Identical Conversion Volumes
Two or more of your Google Ads conversion actions report the exact same conversion count. Identical counts on independent actions are statistically unlikely. The usual cause is two tags wired to the same event, or one event being imported twice (once from the site tag, once from GA4 or an offline upload).
Why It Matters
Each Google Ads conversion action should represent a distinct user outcome. When two enabled actions land on the same integer (say, 247 and 247) across hundreds of sessions, the actions are almost certainly being fed by the same underlying trigger. Common patterns: a Purchase tag that was forked into Purchase and Purchase_New during a migration but never decommissioned, a GA4 imported conversion that mirrors a site-tag conversion, or two GTM tags listening to the same dataLayer push. The downstream damage is subtle. Conversion totals on the account double. Smart Bidding sees twice the volume it should and bids more aggressively. Reported ROAS halves because spend is real but value is duplicated only on the count side, not the value side. Finance reconciliation breaks. The conversion column in Ads Manager and the order count in the commerce backend stop matching.
How To Fix It
- Open Tools and Settings, Measurement, Conversions in Google Ads.
- Filter to the actions with matching counts and inspect Source for each (Website, Google Analytics 4, Import, Firebase).
- If two share the same source, open the GTM container or site tag and find every tag that sends conv id and label for either action.
- Keep one canonical action per business outcome, mark the duplicate as Secondary or set it to Removed (not just disabled).
- Walk one real conversion end to end in Tag Assistant to confirm only one network call hits per outcome.
Example
Purchase - Website: 247 conversions
Purchase (GA4 import): 247 conversions
Same event, two paths.Two or more enabled Google Ads conversion actions on this account report identical conversion counts over the reporting period. Per Google Ads conversion tracking documentation, each conversion action is intended to represent a distinct user outcome, and identical counts across independent actions strongly indicate the same underlying event being counted through two paths (for example, a website tag and a Google Analytics 4 import wired to the same purchase, or two GTM tags listening to the same dataLayer event). The result is inflated total conversions, Smart Bidding optimizing against duplicated volume, and reported ROAS that diverges from backend revenue because spend is real while count is double. Fix: identify the duplicated source in the Conversions list, keep one canonical action per outcome, set the duplicate to Removed or Secondary, and verify in Tag Assistant that only one conversion request fires per real user outcome. 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