Conversion Callback Implementation
One or more Google Ads conversion tags in your GTM container fire on a form submit or link click trigger, then let the page redirect immediately. There's no `eventCallback`, no `event_callback`, and no tag sequencing. The browser tears down the request before the hit reaches Google. Your Google Ads conversion action records nothing for those users, and Smart Bidding never learns from them.
Why It Matters
A Google Ads conversion tag is an outbound HTTPS request. It needs roughly 200 to 800 milliseconds to leave the browser. On a confirmation pageview that lifetime is fine. On a form submit or an outbound link click, the browser starts navigating before the tag finishes, kills in-flight requests, and the conversion is lost. The fix is a callback or a sequence. With `eventCallback`, the form submit trigger waits for the tag to confirm the hit went out before letting navigation proceed. With tag sequencing (setupTag and cleanupTag in GTM), the conversion tag fires first, the navigation fires second, and the order is guaranteed. The loss rate is uneven, and that's what makes the bug hard to spot. Fast desktop browsers on good connections often complete the request in time. Mobile on a slow connection misses most of them. Reported conversion volume looks fine in aggregate, but it's biased toward users on faster networks and faster devices — exactly the audience Smart Bidding is now told to chase.
How To Fix It
- Open every Google Ads conversion tag firing on a `formSubmit` or `linkClick` trigger.
- Either set the trigger to "Wait for Tags" and enable Check Validation, or add tag sequencing so the conversion tag fires as a setup tag before the navigation.
- For custom HTML conversion implementations, add `eventCallback` to the gtag config so the page only continues after the hit confirms.
- In Preview mode, run the form submit on a throttled mobile profile and confirm the conversion request completes before the redirect.
- Republish and verify reported conversion volume on those actions rises on mobile within one reporting cycle.
Example
Trigger: Form Submit
Wait for Tags: enabled
Max wait: 2000 ms
Or: setupTag = AW Conversion, navigation fires afterGoogle Ads conversion tags in this GTM container fire on form submit or link click triggers without `eventCallback`, `event_callback`, or GTM tag sequencing configured. Per the Google Tag Manager trigger documentation, conversion tags that fire on navigation events require either a wait-for-tags configuration or explicit sequencing, otherwise the browser tears down the outbound request before it reaches Google Ads. The result is uneven conversion loss skewed toward slower devices and mobile connections, which biases the Smart Bidding signal toward the users least representative of your full customer base. Fix: enable Wait for Tags on the trigger, or add a setup tag sequence so the conversion fires before navigation, then verify on a throttled mobile profile in Preview. Source: support.google.com/tagmanager/answer/7679219.
Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.
References
Audit your own files for this check
AdLint runs this check (and 177 others) against your GTM, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Twitter/X, and Snapchat exports. Everything stays in your browser. No uploads, no accounts.
Run a free audit