Conversion Tags Missing Error Handling
Why It Matters
Conversion tags on click and form-submit triggers are in a race with the browser. The user clicks the button. The form posts. The browser starts navigating. Meanwhile, the conversion tag is opening a connection to googleads.g.doubleclick.net and trying to send the conversion. Whoever finishes first wins.
On a fast desktop with a fast connection, the conversion request takes maybe 50ms. The browser doesn't start navigating for around 200ms after the form submit (network round-trips, redirects, etc.). The conversion almost always makes it. So everything looks fine in QA, on the dev machine, in Preview mode.
On a phone over a flaky 4G connection, the conversion request can take 1500ms. The browser starts navigating at 300ms because the form post completed faster than usual. The conversion request is mid-flight when navigation kills it. The conversion never arrives at Google Ads.
The result is a slow, invisible data loss that scales inversely with device speed. Fast devices report most of their conversions. Slow devices lose a chunk of them. Reported conversion data ends up biased toward fast-device demographics. Smart Bidding learns from biased data and shifts budget toward audiences whose conversions tend to make it through — which isn't the same as audiences who actually convert.
Google gives you a few ways to fix this. Tag Sequencing with a setup tag that waits. An eventCallback parameter that delays the navigation until the tag completes. Or the trigger's built-in "Wait for Tags" option, which is the simplest and works for most cases.
How To Fix It
In GTM, open Triggers. Find every Click or Form Submit trigger that fires conversion tags.
Open each trigger. Tick "Wait for Tags." Set Max Wait Time to 2000ms. That gives the conversion request up to 2 seconds before the navigation forces through.
If a trigger fires Custom HTML conversion tags, add an
eventCallbackparameter that handles the navigation explicitly. This is more reliable than Wait-for-Tags for non-standard tags.Use Tag Sequencing if the conversion tag has setup tags (Conversion Linker, Consent Mode init) that must fire first.
Verify in Preview mode with Network throttling set to Slow 3G (DevTools → Network). Submit the form. Confirm the conversion request shows a 200 response before the navigation completes.
Publish only after every flagged trigger has the configuration visible in Preview.
Example
Trigger: Form Submit - Lead Capture
Wait for Tags: enabled, max wait = 2000ms
Check Validation: enabledThis GTM container has Google Ads conversion tags firing on navigation-triggering events (Click or Form Submit) without configured error handling. Per Google's Tag Manager trigger documentation, the "Wait for Tags" option or an event callback must be configured to prevent browser navigation from killing in-flight conversion requests. Without these safeguards, conversion data is lost on slow connections and slow devices in proportion to the latency of the conversion request, biasing reported data toward fast-device demographics. Fix: enable "Wait for Tags" with a 2000ms max wait on every flagged trigger and verify completion in Preview under throttled network conditions. Source: support.google.com/tagmanager/answer/7679219.
Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.