Fireshift / Guides

Google Ads transaction ID for lead forms: 875 sites

By the Fireshift team · Updated 2026-11-08

What does a transaction ID do for a lead?

Google Ads counts two conversions with the same transaction ID on the same conversion action once (Google Ads Help). Google built it for orders, but a lead form has the same problem: a reloaded thank-you page, a trigger that fires twice, or GTM next to an old gtag snippet. Each of those counts one lead as two.

Counting "One" per click helps, but only per action and only for the same ad click (counting options). The ID is the fix that holds when the same person comes back from a second click.

How many sites send one?

We read every Google Ads conversion tag (GTM tag type "Google Ads Conversion Tracking") in the public containers of the 886 sites. 875 had one or more, 5,925 tags in all. A tag sends an ID when its Transaction ID field is filled.

Most IDs come from a dataLayer variable. The most common name is ecommerce.transaction_id (116 tags), the GA4 ecommerce field. That is the right source for a purchase. On a lead tag it is often empty, because nothing pushes an order for a form.

Our 5 Nov count on a smaller set of 193 B2B SaaS sites was 13.0% with an ID on any tag (duplicate conversions guide). The bigger base gives 15.5%.

What goes wrong with a fixed ID?

Three sites typed a fixed value into the Transaction ID field: 1, 2 or 1001. One of them sends ID 1 with every booked meeting. Google Ads keeps the first conversion with that ID on that action and drops the rest as duplicates. A fixed ID is worse than no ID.

How do I check mine?

1. In GTM, open each Google Ads Conversion Tracking tag and look at the Transaction ID field. Empty means no ID. A typed number means a fixed ID.
2. Open DevTools, Network, filter on your AW- number. Submit the form once with a test address.
3. Open the conversion request and look for oid=. No oid means no ID. The same oid on two test submits means the ID is fixed or stale.
4. Reload the thank-you page. A second request with a new oid counts a second lead.
5. In Google Ads, check which actions are primary. Only primary actions steer bidding (Google Ads Help).

How do I add one in GTM?

• Push the ID with the success event. Most form tools return a submission ID after the form is accepted. Push it with your success event, for example dataLayer.push({event: 'form_success', lead_id: '…'}).
• Read it with a Data Layer Variable and put that variable in the tag's Transaction ID field. In gtag, it is the transaction_id parameter of the conversion event (Google Ads Help).
• No submission ID? Make one in the browser once per submit and keep it in the session, so a reload sends the same value.
• Never use an email, a phone number or a name. Google does not allow personal data in the transaction ID.
• Fire on the confirmed form, not the click. An ID does not fix a tag on the wrong trigger (click conversions, HubSpot forms).

What can't we see from outside?

• Primary or secondary, and the count setting. Both live in the Ads account.
• Whether the variable is filled. We see the field name, not the value at run time.
• Inline gtag calls, server-side tags and offline imports. An ID can be sent outside a public GTM container. 11 of the 886 sites had no readable Ads tag.
• The sample: our 1,727-site study, built from lists, not random. It leans B2B SaaS.

Published 8 Nov 2026. Data: docs/research/txn-id-2026-11-08.json (tools/research/txn_scan.py, txn_analyze.py); base = the 886 study sites with Google Ads conversions (study scanned 5 Nov 2026, containers read 8 Nov). Lead tag = a tag whose trigger event does not name a purchase, order, checkout, payment or transaction. Recheck: tools/research/txn_recheck.py. Method.

FAQ

Can I use the lead's email as the Google Ads transaction ID?

No. Google does not allow personal data in the transaction ID. Use the form's submission ID, or a random ID made once per submit.

Does the free Fireshift scan check transaction IDs?

It reads every Google Ads conversion tag in your public GTM container. It can see whether the Transaction ID field is set and whether it is a fixed value. It can't see the value at run time, or whether an action is primary or secondary.