Google Ads · Trade show lead → deal · Conversion tracking
How to track trade show lead to closed deal for Google Ads
A badge scan at a booth has no click identifier and never will, but the pre-show campaign that booked the meeting does — and those are two very different leads recorded identically. 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 closed deal in your CRM — no cookie survives the gap between pre-show campaign click and deal closed.
✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.
Written guarantee
95%+ conversion accuracy on Google Ads · Trade show lead → deal
Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.
Built on — and certified for — the platforms that matter
Stape
Pro Partner
Meta
Tech Provider
Tag Manager
TikTok
Events API
Microsoft
UET Partner
CAPI Partner
CAPI Partner
Built on the same partner stack used by enterprise DTC brands.
Where this funnel usually breaks
Every show lead imported with one source
It is the fastest way to load the list and it destroys the only distinction that matters — whether the campaign produced the lead or the booth did.
The whole show's pipeline credited to media
Booth cost, travel and staffing produced most of it. Attributing the lot to a pre-show campaign makes that campaign look extraordinary.
Scanned leads never marked unattributable
They then sit in the pipeline as ordinary leads and quietly inflate every source-level report they touch.
Specific to Google Ads × Trade show lead → deal
Google Ads before a trade show: credit only pre-booked meetings
For trade show pipeline on Google Ads, capture gclid, gbraid or wbraid on the pre-show meeting booking page and store it on the contact before the show. Import the booked meeting as a conversion action, and upload closed deals through offline conversion import only for those contacts and only within 90 days of the click.
Google's role before a show is mostly search. Attendees look up the show's exhibitor list, your booth number or your brand plus the show name, and a search ad that offers a meeting slot catches them at that moment. Those clicks produce the only attributable leads in the funnel, so the booking page has to write the click ID to the contact at registration, not after the show list is imported.
Timing works against closed deals. A meeting booked three weeks before the show and a deal that closes four months after it puts the deal outside Google's 90-day import window. Make the meeting held at the show the primary conversion action, with a value based on your meeting-to-deal rate, and upload closed deals as a secondary action only when they land inside the window.
The import list is where it breaks. When the badge-scan file and the pre-booked list are merged and uploaded in one go, scanned contacts have no gclid and should simply fail to match. The danger is Enhanced Conversions for Leads, which can match a scanned contact by hashed email if that person once clicked an ad. Upload only contacts flagged as pre-booked.
Architecture
The exact event sequence
Five stages. The break is at stage four: pre-booked meetings and floor scans get imported into the CRM in one batch, and after that no one can tell them apart. The identifier has to survive all of them.
Step 1
Pre-show campaign click
The only stage in this funnel with an identifier. Capture it and store it on the contact immediately.
Step 2
Meeting booked at the show
Attributable, because it came from the campaign.
Step 3
Badge scanned at the booth
Not attributable. Someone walked past and was interested. That is a real lead and it is not a campaign result.
Step 4
Post-show follow-up
Where both types converge and become indistinguishable if nobody separated them at intake.
Step 5
Deal closed
Months later, at a value that has to be traced back to which of the two origins produced it.
Diagnostic sequence
What's specific to Google Ads
The funnel logic above is the same wherever you advertise. These are the parts that change because it's Google Ads.
- 1
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.
- 2
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.
- 3
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.
- 4
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.
- 5
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.
Source-of-truth validation
How to prove the chain works
One real journey, followed all the way, then a reconciliation. Neither on its own is enough.
- A live Google Ads ad clicked, and the identifier confirmed present on the landing URL.
- The same identifier confirmed on the closed deal in your CRM after a full real journey through every step.
- Deal closed confirmed arriving at Google Ads, verified by the match rate on the upload, not the success message.
- Your crm, with the lead source split into pre-booked and scanned reconciled against Google Ads per record over a fully closed window.
- The same reconciliation repeated 30 days later.
Straight talk
When this doesn't apply to you
Worth checking before you build anything, because two of these are common and both mean the work isn't worth doing.
- If you run no pre-show digital campaign, every lead from the event is a booth lead and none of it is attributable. Say so.
- 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 deal closed regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward pre-booked meetings held at the show instead and use the later data for budget decisions rather than for bidding.
- If almost none of your closed deals carry a click identifier today, that's the whole project. Fix capture first — the import is the easy half and no tooling rescues a record with nothing to reference.
What working looks like
Deal closed attributed to the click
Server-sideWeeks later if necessary, because the identifier lives on the closed deal in your CRM rather than in a cookie.
Google Ads bidding fed the real outcome
8+ EMQVia offline conversion import, so it optimizes toward closed deals from pre-booked meetings rather than toward badge scans.
A reconciliation that closes
DedupedYour crm, with the lead source split into pre-booked and scanned matched per record against what Google Ads reports, over a fully closed window.
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 closed deal in your CRM
Write the identifier onto the contact at the pre-show registration, weeks before the show. There is no second chance once the event starts.
Send deal closed from the record
Your CRM on the closed deal, but only for contacts whose pre-show campaign identifier was stored before the event. 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. Lost deals reverse.
Want this built for Google Ads · Trade show lead → deal? One fixed price, $400–$1,800, no monthly fee. Live in 2–4 business days, 95%+ accuracy in writing. See packages
Book a free 30-min callGot questions?
The honestanswers.
No buzzwords, no upsell. If we don’t know, we say so.
01Should I upload badge-scanned leads to Google Ads as conversions?
No. Only contacts who booked through the pre-show campaign belong in the upload; scanned leads were produced by the booth, not by the click.
02Can geo-targeted Google Ads around a trade show venue be attributed?
Clicks that lead to a booked meeting can. Ads seen during the show that send someone to walk past the booth produce scans, which are not attributable.
03Why isn't meeting booked at the show enough to optimize on?
Because badge scans measure footfall past your booth, which is a function of your stand position and the show's attendance, not of anything you bought.
04How does the identifier survive to deal closed?
It doesn't, as a cookie — the gap is too long. It has to be written onto the closed deal in your CRM at the point of pre-show campaign click, where it lives as a field rather than as browser storage.
05What does Google Ads need to accept the conversion?
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.
06How long does this take to build?
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.
07Can I do this myself?
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 a lead list imported in one batch after the show, which fails silently at every stage.
Still have questions?Book a 30-min call— bring them all.
RELATED GUIDES
Related funnels, and the checks that close this one
- 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 · CybersecurityGoogle Ads conversion tracking for cybersecurity companies
- Google Ads · IT services / MSPGoogle Ads conversion tracking for IT services providers and MSPs
- Universe → Google AdsConnecting Universe to Google Ads
- Tixr → Google AdsConnecting Tixr to Google Ads
- Google Ads · Demo request → opportunityHow to track demo request to opportunity for Google Ads
Get trade show lead to closed deal tracked properly on Google Ads
Book a free 30-minute call. We measure your actual identifier coverage on your own account, live, and you leave with a written plan — including the option that you don't need us.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
You might also need
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400


