How to Set Up Google Ads Enhanced Conversions

To set up Google Ads enhanced conversions correctly, first make sure a normal conversion action records the real business outcome, then choose the implementation path that owns the tag or API connection, configure eligible first-party data with the site’s consent rules, and validate both the original and enhanced signals. Enhanced conversions are an addition to conversion measurement, not a replacement for a conversion tag or a way to make a weak event useful.

The exact labels in Google Ads can vary as Google consolidates enhanced conversions for web and leads. The durable sequence is the same: define the action, prepare the data, configure one method, test deduplication, and watch diagnostics. Google’s Enhanced Conversions Best Practices documentation is the reference for implementation details; this guide is a release checklist for an advertiser or developer carrying out the setup.

Before you turn anything on

Write down the conversion action you intend to improve. A purchase, completed application, qualified consultation request, or paid subscription is a stronger candidate than a page view or a form-start event. Confirm its primary or secondary role, counting setting, value and currency behavior, and the system that owns the conversion record. If the action is not already reliable, start with the Google Ads conversion tracking settings review instead of adding another layer.

You also need a source of first-party data at or around the conversion. For web conversions that may be an email address, phone number, name, or address entered by the customer. For a lead workflow, the later CRM record may contain the information needed for an enhanced conversion for leads. Do not assume that an Analytics import supports every enhanced-conversion path; check the current Google instructions for the source you actually use.

Finally, identify the person responsible for the tag, the person responsible for consent, and the person who will compare Google Ads with the source system. Setup is not complete when a checkbox is green if no one can explain what data was sent or whether one order became two conversions.

Step 1: Open the right conversion settings

In Google Ads, open the Goals or Conversions area and locate the conversion action or the account-level enhanced-conversion setting shown for your account. Google’s current account-level guidance explains that the available method and behavior can depend on existing web, lead, tag, or API configurations. Do not select a new method simply because it is the first item in the menu. Match the setting to the system that already records the conversion.

Review the existing action before opting in. Check whether enhanced conversions were already enabled at the action level, whether the action was explicitly opted out, and whether another tag is sending the same data. Save a screenshot of the starting state without exposing customer information, and record the date and editor in the change log.

Step 2: Choose the implementation method

Google tag

Use the Google tag path when the site already places a Google tag directly on the pages and the team can update the conversion event. Map the relevant first-party fields at the successful conversion event, not on every page view. For an order, wait for the confirmed order state and pass the transaction ID, value, and currency through the same dependable event.

Google Tag Manager

Use Google Tag Manager when it owns the site’s advertising tags and approvals. Keep the enhanced-conversion configuration with the conversion tag that fires the original action. Document the trigger, variables, normalization behavior, and consent requirement. Preview the container on a test property or controlled journey before publishing, and make sure a direct site tag is not also firing.

Google Ads API or Data Manager path

Use an API-oriented method when a server or data pipeline owns the conversion record, especially for lead stages that happen after the web form. Google’s API documentation requires a regular conversion-tracking foundation and describes sending formatted, hashed first-party data with the conversion connection. Keep the conversion action identifier, click identifier, event time, and deduplication identifier in the system that sends the adjustment. The API should be the documented owner, not a second experiment running beside the browser tag.

Step 3: Configure customer data and consent

Choose the smallest set of first-party fields needed for matching and implement Google’s normalization and hashing rules for the chosen method. Never send raw email addresses or phone numbers through a URL parameter or place them in a shared log. Test whether a field is empty, malformed, shared by several people, or collected at a stage where the user has not given the necessary permission.

Consent must be evaluated before the enhanced-data signal is sent. If your site uses a consent management platform, verify the handoff between its granted or denied state and the tag trigger. Test a visitor who accepts, a visitor who rejects, and a visitor who has not answered. For the EEA and UK, Google recommends a strong consent framework as part of the enhanced-conversions setup; the official best-practices guide should be read alongside your legal and privacy requirements.

Do not treat hashing as consent. Hashing protects the value’s transmission and matching workflow; it does not make collection lawful, correct, or expected by the customer. Record the consent state used by each test and delete raw test data from any temporary system after verification.

Step 4: Prevent duplicate conversions

For ecommerce, refresh the confirmation page, use the browser’s back button, retry a payment, and replay a server callback. The same order should retain one stable transaction ID. For leads, submit the form once and trace the later CRM event. Decide whether the browser event is the initial conversion and the CRM event is an adjustment, or whether the CRM event is the only primary action. Never let both independently become two primary conversions for one opportunity.

If you use the API, send the enhancement within the current documented window and preserve the identifier that ties it to the original conversion. If the implementation cannot explain how an event is matched or deduplicated, stop the launch and fix the data contract before interpreting performance changes.

Step 5: Test the finished setup

Run one controlled conversion through the real journey. Use the tag or container preview to verify the intended trigger, then inspect Google Ads diagnostics for the action. Compare the Google Ads record with the order system, CRM, or other source of truth by date, action name, value, and identifier. A tag firing proves only that code executed; it does not prove that the conversion was attributed or that enhanced data was eligible for matching.

Keep the change isolated from a bid-strategy change for at least one review cycle. If you alter the tag, consent tool, conversion action, and campaign goal on the same day, a later increase or decrease cannot be assigned to one cause.

Troubleshoot common setup failures

If enhanced conversions show no activity, check the selected conversion action, the event trigger, the consent state, field availability, and the method chosen in the account. If activity appears higher than expected, investigate duplicate browser and server events, purchase retries, and whether a form-start action is included in the same reporting column. If diagnostics are limited, use a controlled test and compare source-system evidence rather than guessing from a single day of reported conversions.

Google’s interface is changing as web and lead enhanced conversions move toward more unified settings in 2026, so an older tutorial may show a different menu. Follow the account’s current help link and preserve the underlying data contract when the labels change.

adz.so can inspect supported Google Ads settings through its audit workflow, but it does not install tags, configure your consent platform, or replace your CRM data pipeline. After the implementation is live, review the conversion tracking setup guide and the enhanced conversion settings article for the surrounding decisions.

Research note: reviewed against Google Ads Help enhanced-conversion setup, account-level, and API guidance on 2026-08-03. Confirm the current account UI and data-policy requirements before publishing a production change.