Common Google Ads Enhanced Conversions Mistakes

The most common Google Ads enhanced conversions mistakes are measurement-design errors: enabling the feature on a weak action, sending the same conversion from two owners, ignoring consent, exposing raw customer data during testing, or judging a release before conversion lag has passed. Fix the conversion definition and the data path before trying to increase match coverage.

Enhanced conversions use hashed first-party data to supplement an existing conversion signal. Google’s best-practices guide explains the purpose and implementation requirements. The practical test for every setup is simple: does this event represent a result the business wants more of, did it fire once with an allowed data path, and can the source system reconcile it with Google Ads?

Mistake 1: Turning on enhanced conversions before fixing the action

An enhanced signal does not change a page view into a purchase or an unqualified form into a sales opportunity. If the conversion action fires on a button click, checkout start, or duplicate form submission, enhanced matching can make the wrong event more visible. Review the action’s primary or secondary status, counting rule, value, currency, and business owner first.

Use a completed purchase, qualified application, paid subscription, or another defensible result when the account should optimize toward business outcomes. Keep useful funnel events secondary when they are diagnostic only. The Google Ads conversion tracking settings article provides the surrounding decision framework.

Mistake 2: Running two undocumented implementation owners

A direct Google tag, a Google Tag Manager container, and a server-side API can all be valid technologies. The mistake is letting two of them send the same action without an explicit relationship. A browser purchase plus a server callback can become two conversions if the transaction ID is not preserved. A Tag Manager trigger can duplicate a direct tag after a site migration.

Choose the owner that matches the existing architecture. If the browser event is the original conversion and the server event is a later adjustment, document that relationship and the identifier that connects them. If the API owns the conversion, do not leave an old tag firing as a second primary action. Google’s API guidance describes the need for a regular conversion foundation and correctly formatted data; it is not a reason to add an untracked sender.

Mistake 3: Treating hashing as permission

Hashing can protect a value in the matching process, but it does not decide whether the site was allowed to collect it. Do not send an email, phone number, name, or address before the relevant consent state is available. Test granted, denied, and unanswered states, and make sure a consent-management platform’s state reaches the tag before the conversion trigger.

For the EEA and UK, Google recommends a strong consent framework for enhanced conversions. Review the official guide with the site’s legal and privacy owners. Never place raw customer data in a URL, screenshot, console log, or shared debugging ticket. A secure-looking technical implementation can still be an unacceptable data-collection process.

Mistake 4: Sending every available field

More fields do not automatically mean better matching. An optional phone number may be stale, a placeholder email may be shared by multiple employees, and a name may not be available at the conversion event. Send the smallest reliable set allowed by the selected method. Normalize and hash it according to Google’s instructions, then remove raw test values from temporary systems.

Field quality also depends on the business event. An email captured on a free download may be valid first-party data but irrelevant if the campaign should optimize toward paid subscriptions. A good field attached to a weak action is still a weak bidding signal.

Mistake 5: Ignoring duplicate and retry paths

Test refreshes, back navigation, payment retries, webhook retries, cross-domain redirects, and mobile checkout. For ecommerce, carry one stable transaction ID through the confirmation and server paths. For leads, assign the initial form, qualified stage, booked meeting, and sale distinct roles. Do not count a CRM qualification as a new primary conversion when it is an adjustment to the original lead.

Compare identifiers, not just totals. A daily total that is twice as large may be an obvious duplication, but smaller duplication can be hidden by conversion lag or timezone boundaries. Keep an idempotency rule in the server or CRM pipeline so reprocessing a message does not create a new business event.

Mistake 6: Confusing a tag preview with a successful conversion

A preview tool can show that JavaScript ran, but it does not prove the event was sent with the expected action, passed the consent condition, was accepted by Google Ads, matched the correct account, or contributed to bidding. Use a full acceptance test: source-system record, tag or API evidence, Google Ads diagnostic, and final reconciliation.

If diagnostics are delayed, do not keep republishing the same change. Save the test timestamp, action, identifier, and safe error information. Wait through the normal processing window and compare the result before changing another layer.

Mistake 7: Changing measurement and bidding at the same time

Turning on enhanced conversions, changing primary actions, switching bid strategies, and redesigning a checkout in one release destroys the experiment’s explanation. If performance moves, no one can tell whether measurement coverage, auction decisions, user behavior, or duplicate data caused it.

Release the measurement change first. Confirm the action, data path, consent, deduplication, and source-system reconciliation. Only then decide whether the campaign’s bidding goal should change. Mark the launch date and allow for the account’s conversion lag before judging performance.

Mistake 8: Copying an obsolete interface path

Google is changing the presentation of enhanced conversions for web and leads as settings become more unified during 2026. A tutorial may show conversion action menus or method labels that are not present in a particular account. Follow the current help link in the account and preserve the underlying questions: which action, which owner, which consent state, which identifier, and which source-system result?

A safer correction workflow

When a mistake is found, freeze unrelated changes and write a small repair note:

1. Name the affected conversion action and the observed symptom.
2. Trace one controlled event from the source system to every possible sender.
3. Remove or disable only the duplicate or incorrect path after confirming the intended owner.
4. Retest consent, field availability, transaction or event IDs, and diagnostics.
5. Compare the first complete conversion cycle with the source-system report.

Use the enhanced conversions setup guide for implementation steps and the enhanced conversions checklist for sign-off evidence. adz.so can inspect supported account settings through its audit workflow, but it does not implement tags, consent systems, or CRM imports.

Research note: reviewed against Google Ads Help enhanced-conversion best practices, account-level guidance, and API documentation on 2026-08-03. Verify current UI labels and data-policy requirements before a production correction.