Google Ads guide

How to Fix Google Ads Enhanced Conversions

Fix Google Ads enhanced conversions by identifying where the event is lost or misclassified: the conversion action, the browser or server trigger, the consent state, the customer-data field, the identifier, or Google Ads diagnostics. Do not add another tag as a first response. An extra sender can turn a missing-data problem into a duplicate-conversion problem and make the account harder to debug.

Enhanced conversions improve an existing measurement path with hashed first-party data. Google’s enhanced conversions guide and API documentation are the authoritative references, but the fastest repair usually starts with one controlled conversion and a trace back to the source system. Record the symptom, test the smallest possible change, and compare the result by identifier rather than trusting a single reported total.

Classify the failure before changing code

Write down what you actually see. “Enhanced conversions are not working” can mean no conversion action fires, the action fires but sends no eligible field, Google Ads reports limited diagnostics, the count is higher than the order or CRM system, or the conversion appears but is the wrong business event. Each symptom has a different fix.

Check the action’s primary or secondary status, counting rule, value, currency, conversion window, and selected implementation method. Compare the action with the surrounding conversion tracking settings before touching enhanced data. If the account is optimizing toward a duplicate form submit or page view, better matching will not repair the bidding goal.

Fix missing or limited enhanced-conversion data

Start with a controlled test that completes the real conversion journey. Confirm that the intended conversion action fires once, then use the tag or container preview to see whether the enhanced-data mapping is evaluated at that same event. A page-load trigger can run successfully while the purchase or lead event never happens, and a form trigger can run before the customer data is available.

If the event fires but no enhanced signal is eligible, check the selected method in Google Ads against the method actually sending data. A configuration that expects Google Tag Manager may not process an API payload chosen as the account’s method, and a server adjustment cannot compensate for a browser tag that points to a different conversion action. Google’s API guidance also requires a normal conversion-tracking foundation before enhanced data is sent through the API.

Check field availability at the moment of conversion. An email variable may be empty because the form cleared after submission; a checkout may keep the value only in a server response; a phone field may be optional or formatted unexpectedly. Follow the normalization and hashing rules for the method, and inspect only safe test evidence. Never copy a raw email address or phone number into a ticket to prove that the field existed.

Fix duplicate conversion counts

When Google Ads reports more conversions than the source system, trace one order or lead through every possible sender:

  1. Check whether a direct Google tag and a Google Tag Manager tag both fire.
  2. Check whether a confirmation page fires again after refresh or a payment retry.
  3. Check whether a server callback retries without preserving the original transaction or event identifier.
  4. Check whether a CRM qualification import is being treated as a new primary conversion instead of an adjustment or later-stage action.
  5. Check whether a form start, button click, and successful submission share a goal that the campaign counts as one business result.

For ecommerce, use the stable order or transaction ID through the browser and server path. For leads, decide whether the initial form event or later qualified stage is primary, and make the relationship explicit. Enhanced conversions should supplement the original action; they should not be a second independent conversion definition.

Fix consent-related failures

Test three states: consent granted, consent denied, and no decision yet. Verify that the enhanced-data signal follows the site’s consent rules in each state. If a consent management platform updates asynchronously, make sure the tag does not fire before the state is available. If an action can complete before a customer makes a decision, document what the site is allowed to measure and which fields are withheld.

Google recommends a strong consent framework for enhanced conversions in the EEA and UK. Read the official best-practices guidance alongside your own privacy and legal requirements. Hashing does not turn unconsented collection into permitted collection, and a successful tag preview does not prove that the policy path is correct.

Fix the wrong conversion action or goal

Sometimes the code is working but the account is optimizing toward the wrong event. Compare the conversion action’s name, source, category, primary status, counting method, value, and owner with the business definition. A purchase tag that fires on checkout start, or a lead action that fires for an unqualified form, should be fixed at the event-definition layer.

For longer sales cycles, keep a dependable online event while the CRM pipeline is being integrated, then import a qualified stage when its identity and timing are reliable. Do not make a low-quality event primary simply because it provides more volume. Better matching can increase the visibility of a bad goal just as efficiently as a good one.

Fix API and data-pipeline errors

For API or Data Manager implementations, check the conversion action ID, event time, click identifier, currency, value, first-party-data formatting, hash algorithm, and deduplication identifier. Read the response from the sending service and store a safe error code and request ID, not raw customer data. Confirm that the upload occurs within the documented attribution window and that the account has accepted the relevant data terms.

If offline lead stages are delayed, distinguish a real processing delay from a failed upload. Compare the source queue, accepted records, rejected records, and Google Ads conversion status. Re-sending without idempotency can create a second event; deleting the queue without preserving the failure reason makes the next repair harder.

Check the repair without creating a new problem

After a change, run one controlled test and compare the browser or server log, the Google Ads diagnostic, and the source-system record. Keep the test separate from a simultaneous bid-strategy, consent-banner, checkout, or landing-page release. Annotate the change date and wait through normal conversion lag before deciding whether reporting improved.

Use a short repair record:

  • Symptom and affected conversion action.
  • Sender and implementation method before and after the fix.
  • Consent state used in testing.
  • Identifier used to prove one event rather than two.
  • Source-system record and Google Ads diagnostic result.
  • Owner and date for the next reconciliation.

If the account is still unclear, return to the enhanced conversions setup guide and the existing conversion tracking checklist instead of adding more instrumentation. adz.so can inspect supported account settings through its audit workflow, but it does not repair tags, consent, or CRM pipelines for you.

Research note: reviewed against Google Ads Help enhanced-conversion best practices, account-level guidance, and API documentation on 2026-08-03. Check the current account diagnostics and policies before changing production code.