How to track demo request to opportunity for Google Ads
A demo request is a form fill, and a large share of them are students, competitors and people who will never buy. What separates a good channel from a cheap one is the rate at which requests become qualified opportunities — and that's invisible to bidding unless the qualification outcome is sent back. On Google Ads the specifics that matter are the click identifier (gclid, gbraid and wbraid), the import mechanism (Google's offline conversion import), and conversion actions deduplicate on their own counting setting rather than an event ID, so the setting matters more here than the payload. The chain only works end to end if the identifier is captured on landing and stored on the lead and opportunity records in your CRM — no cookie survives the gap between ad click and qualification sent back.
Free30 minutesNo obligation
Specific to Google Ads × Demo request → opportunity
Google Ads demo-to-opportunity: qualified pipeline as primary action
Upload the qualified opportunity to Google Ads as an offline conversion when the CRM stage changes, matched on the gclid, gbraid or wbraid stored on the lead, or on hashed email through Enhanced Conversions for Leads. Value it by expected deal size, make it the primary action, and keep the demo form as secondary.
Google is usually the strongest demo channel for B2B software because the request follows a search, and qualification typically happens within days or a few weeks, well inside the 90-day import window even when the close is not. Make the qualified-opportunity action primary and leave the form fill as secondary once qualified volume is steady. Value each opportunity by segment, such as expected deal size times win rate, so an enterprise opportunity is not worth the same as a single-seat one.
Enhanced Conversions for Leads is worth turning on alongside the gclid. It matches the uploaded opportunity on the hashed work email captured by the demo form, which recovers requests where the click identifier was dropped by a multi-step form. If your CRM is Salesforce, Google also has a native connection that imports by stage; check whether its stage mapping matches your written qualification definition before relying on it.
Two Google-specific distortions show up as soon as opportunities flow back. Brand campaigns claim opportunities from people who were coming anyway, so keep brand in its own campaign and don't let its qualified count justify non-brand budget. Competitor-keyword campaigns fill the calendar with competitors' staff and analysts doing research; the opportunity rate exposes them within a month.
Google Ads · Demo request → opportunity · what breaks
Where this funnel usually breaks — Google Ads · Demo request → opportunity
- 01
Qualification never defined
So quality disputes between marketing and sales are two opinions with no referee, and nothing can be sent back.
- 02
Requested and attended treated as one
A demo nobody showed up to isn't a signal worth paying for.
- 03
The identifier lost at lead conversion
Same failure as every CRM funnel: the field is on Lead, the Opportunity has nothing, and nothing errors.
Google Ads · Demo request → opportunity · the fix
What working looks like — Google Ads · Demo request → opportunity
Qualification sent back attributed to the click
Weeks later if necessary, because the identifier lives on the lead and opportunity records in your CRM rather than in a cookie.
Google Ads bidding fed the real outcome
Via offline conversion import, so it optimizes toward qualified pipeline rather than toward demo form fills.
A reconciliation that closes
Your crm's qualified opportunity records matched per record against what Google Ads reports, over a fully closed window.
Google Ads · Demo request → opportunity · architecture
The exact event sequence — Google Ads · Demo request → opportunity
The interesting drop-off is between stages two and four, and its size differs enough by channel to reorder your entire budget.
- 1
Ad click
Identifier captured on landing and written to the lead on submission.
- 2
Demo requested
The form event. High volume, low meaning, useful only as learning volume.
- 3
Demo attended
A real filter. A meaningful share of requested demos never happen.
- 4
Qualified as an opportunity
Your sales team's own definition, agreed in writing before anything is measured against it.
- 5
Qualification sent back
Uploaded as the conversion, so bidding chases pipeline rather than form fills.
Google Ads · Demo request → opportunity · diagnose
What's specific to Google Ads
- 01
Click identifier: gclid, gbraid and wbraid
Three parameters, not one. gclid is the long-standing identifier; gbraid and wbraid arrive on iOS traffic where privacy constraints prevent the usual one. Capture code that names only gclid loses a growing share, silently, and the loss is invisible until you audit how many records carry an identifier.
- 02
Import mechanism: offline conversion import
Uploaded against the click identifier, either through the Google Ads API or as a file. The upload is the easy part; what limits it is how many of your records carry an identifier at all. Verify the current column format against Google's own template — it has changed before.
- 03
Deduplication
There's no shared event ID mechanism like Meta's. What matters instead is the counting setting on each conversion action — 'one' for lead-type conversions so a repeat submitter doesn't count three times, 'every' for ecommerce where a second purchase is a second sale. This is the single most common misconfiguration we find in Google Ads accounts.
- 04
Window and timing
Google's offline import window is 90 days from the click. Anything older can't be matched, and rows outside it fail as unmatched without much explanation. Measure your median click-to-outcome time against that before designing anything.
- 05
The Google Ads gotcha
A conversion action that stops receiving hits is flagged as inactive 30 days later — by which point a month of budget has already run against a missing signal. Check the last-received date on every action monthly; it takes two minutes and it's the cheapest monitoring available.
Google Ads · Demo request → opportunity · prove
How to prove the chain works — Google Ads · Demo request → opportunity
Source of truth
your CRM's qualified opportunity records
- The same identifier confirmed on the lead and opportunity records in your CRM after a full real journey through every step.
- Qualification sent back confirmed arriving at Google Ads, verified by the match rate on the upload, not the success message.
- Your crm's qualified opportunity records reconciled against Google Ads per record over a fully closed window.
Google Ads · Demo request → opportunity · free audit
What we check in the free audit
- Click identifier: gclid, gbraid and wbraid
- Import mechanism: offline conversion import
- Deduplication
- Window and timing
- The Google Ads gotcha
Checked against
your CRM's qualified opportunity records
Free30 minutesNo obligation
Google Ads · Demo request → opportunity · when not to buy
When this doesn't apply to you — Google Ads · Demo request → opportunity
- If your demos are booked and run entirely by a sales team from outbound lists, this funnel isn't measuring your ad spend and there's nothing here worth building.
- If you're running Performance Max exclusively and haven't separated your conversion actions, the import will work and the reporting won't tell you much. Worth sorting the account structure first.
- If your cycle from click to qualification sent back regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward demo attended instead and use the later data for budget decisions rather than for bidding.
- If almost none of your CRM records carry a click identifier today, that's the whole project.
Google Ads · Demo request → opportunity · what we deliver
The implementation, on Google Ads
Capture gclid, gbraid and wbraid on landing
Auto-tagging appends the identifier. Confirm it's enabled in every account — it gets switched off for cleaner analytics URLs more often than you'd expect, and that single setting removes conversion attribution, Enhanced Conversions and offline import in one go.
Persist it to the lead and opportunity records in your CRM
Capture on landing, carry through every step of the form, write to the Lead, and map through lead conversion onto the Opportunity.
Send qualification sent back from the record
The upload fires when the CRM stage changes to qualified, referencing the identifier stored on the record. Dispatched to Google Ads through Google's offline conversion import.
Deduplicate and reverse
Conversion actions deduplicate on their own counting setting rather than an event id, so the setting matters more here than the payload. An opportunity disqualified after the fact should be adjusted, particularly where you're uploading at the qualification stage.
FAQ
Google Ads · Demo request → opportunity questions, answered
Yes, at the qualified stage, through offline import or Enhanced Conversions for Leads, keyed to the gclid or hashed email on the lead. Make it primary and leave the form fill secondary once qualified volume is steady.
It does until you tell it otherwise. Sending qualified opportunities back is what exposes competitor-term campaigns that fill the calendar with researchers and vendors.
Because the request-to-qualified rate is where channels differ most in B2B. Optimizing on requests buys the cheapest forms, and the cheapest forms are usually the least qualified.
It doesn't, as a cookie — the gap is too long. It has to be written onto the lead and opportunity records in your CRM at the point of ad click, where it lives as a field rather than as browser storage.
A click identifier inside the 90-day window, a conversion action name that matches one configured in the account, a conversion timestamp for when the outcome happened, and a value. Read the match rate after uploading — a file can upload perfectly and match nothing.
Two to four days for the implementation, plus a closed reconciliation window before we'd call it verified. Capture and persistence are the fiddly parts; the import itself is usually an afternoon.
Yes, and the reference pages on this site cover the mechanics. The part that's genuinely tedious rather than clever is keeping gclid, gbraid and wbraid alive through multi-step forms and multi-step demo forms and CRM lead conversion, which fails silently at every stage.
More on Google Ads · Demo request → opportunity
- Meta · Demo request → opportunityHow to track demo request to opportunity for Meta Ads
- TikTok · Demo request → opportunityHow to track demo request to opportunity for TikTok Ads
- Microsoft · Demo request → opportunityHow to track demo request to opportunity for Microsoft Ads
RELATED GUIDES
Funnels next to demo request to opportunity, and the checks that close it
- Google Ads · Franchise enquiry → agreementHow to track franchise enquiry to signed agreement for Google Ads
- Google Ads · Comparison page → demoHow to track comparison page visit to demo request for Google Ads
- Google Ads × CRM DealsHow to reconcile Google Ads against your CRM's closed-won deals
- Google Ads · PEO and HRGoogle Ads conversion tracking for PEO and outsourced HR providers
- Google Ads · Freight and logisticsGoogle Ads conversion tracking for freight and logistics companies
- monday → Google AdsConnecting monday CRM to Google Ads
- SugarCRM → Google AdsConnecting SugarCRM to Google Ads
- Google Ads · Trade show lead → dealHow to track trade show lead to closed deal for Google Ads
Free · 30 min
Get demo request to opportunity tracked properly on Google Ads
Free30 minutesNo obligation
