CROSS·Cross-Source·critical

Conversion ID and Label Matching

One or more Google Ads conversion tags in your GTM container may be sending a conversion ID or label that does not match the intended Google Ads conversion action. The conversion ID and label are the only signals Google uses to route a hit to an action: if either is wrong, the tag fires successfully and the conversion lands in the wrong action or vanishes entirely.

CL
By Christopher LandaverdeCreator of AdLint · ad-tech tracking specialistUpdated

Why It Matters

The conversion ID and label determine which Google Ads action receives the hit. If either value is wrong, the tag can fire successfully while credit lands in the wrong action or nowhere useful. This creates ghost conversions, orphaned actions, and bidding signals attached to the wrong goal.

How To Fix It

Open the Google Ads conversion action and copy the AW conversion ID and conversion label directly into the GTM tag. Avoid variable labels unless you have a controlled lookup table and tests for every output. Preview a test conversion and confirm the fired request contains the expected send_to value.

Example

Configuration
Expected send_to: AW-123456789/AbCdEfGhIjk
GTM tag sends: AW-123456789/{{Conversion Label}}
For Your Client Report

This GTM container contains Google Ads Conversion Tracking tags whose conversion ID or label may not align with the intended Google Ads conversion action. Per Google Tag Manager documentation, the conversion ID (AW-NNNNNNNNN) and conversion label uniquely route a tag hit to a specific conversion action; an incorrect ID, an incorrect label, or a dynamic variable label that resolves unexpectedly will fire the tag successfully while crediting the wrong action or no action at all. The downstream symptoms are ghost conversions on the intended action, mystery volume on an unrelated action, and Smart Bidding optimising on the wrong goal. Fix: copy the conversion ID and label directly from the Google Ads Conversion action into each GTM tag, avoid variable labels unless backed by a tested lookup table, and verify in Tag Assistant Preview that the fired request contains the expected send_to value. Source: support.google.com/tagmanager/answer/6105160.

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