Tag Count Mismatch
The count of Google Ads conversion tags in your GTM container is more than 50 percent different from the count of enabled Google Ads conversion actions, with a gap of at least two. That suggests either duplicate tags counting the same action, missing tags for actions that have no corresponding tag, or a desync between what GTM is firing and what Google Ads is expecting.
Why It Matters
In a healthy account, the number of Google Ads conversion tags in GTM should roughly match the number of enabled conversion actions in Google Ads. One tag per action, one action per business event. Small differences are expected (a tag that fires multiple actions, or an offline import action that has no GTM tag), but a large gap usually means something is off. When GTM has more tags than Ads has actions, the typical cause is duplicate tags. Two tags pointing at the same Conversion ID and label, both firing on the same trigger, both counting the same business event. The duplicate inflates reported conversion volume and biases Smart Bidding. When Ads has more actions than GTM has tags, the typical cause is enabled actions with no tag wiring (which produces ghost conversions: enabled, expected to fire, never receives volume). Either the team built actions in Google Ads ahead of the site implementation and never finished the wiring, or tags were removed during a cleanup without disabling the matching actions. The finding is warning-level because the count gap by itself is diagnostic, not directly broken. Pair this finding with `duplicate-conversions`, `ads-conversion-missing-gtm-tag`, or `gtm-tag-not-in-ads` to identify the underlying root cause.
How To Fix It
- Open the AdLint details and review the GTM tag count vs Google Ads enabled action count.
- If GTM has the larger count, check for duplicate tags. Two tags with the same `send_to` value firing on the same trigger should be consolidated to one.
- If Google Ads has the larger count, list the enabled actions and confirm each has a matching GTM tag (or a legitimate non-GTM source like an offline import). Build the missing tags or disable the orphaned actions.
- Verify the resulting counts in GTM and Google Ads are within roughly 20 percent of each other.
- Re-run AdLint after the next publish and the next reporting cycle.
Example
GTM: 12 Google Ads conversion tags
Google Ads: 5 enabled conversion actions
Likely cause: 7 duplicate tags accumulated from copy-paste during multiple rollouts.This account has a wide gap between the count of Google Ads conversion tags in GTM and the count of enabled conversion actions in Google Ads. Per Google's conversion-tracking documentation, the two surfaces should roughly match (one tag per action, one action per business event); a 50-percent gap with at least two tags difference typically indicates duplicate tags (causing inflated conversion volume), orphaned enabled actions (causing ghost conversions), or a desync between deployment and configuration. The finding is diagnostic and pairs with other cross-source findings to identify the specific root cause. Fix: consolidate duplicate tags, build matching tags for orphaned actions or disable the actions, and verify counts converge within roughly 20 percent after the next publish. Source: support.google.com/google-ads/answer/1722022.
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