How to set up Google Ads enhanced conversions

1. Check the conversion action, data, and access

Choose a website conversion action for the online outcome you want to measure. Copy its Conversion ID, such as AW-123456789, and Conversion Label from the tag setup details. A customer account ID is different. If your current conversion is imported from Google Analytics, do not assume that its identifier can be used as a Google Ads website tag destination.

In Google Ads Goals settings, review the enhanced-conversions setting and customer data terms. Google now uses a unified setting for web and leads, so older instructions showing two separate switches may not match your account. Confirm that the action you are using is covered.

Know where customer information is available when the conversion fires. Plan to send an email or the complete supported name-and-address fields for the web setup, with other fields added when appropriate. Make sure your consent manager is configured before the measurement tag runs.

• Access to the correct Google Ads account and website
• An existing Google tag or a plan for its installation
• The website action's Conversion ID and Label
• Available customer fields on the actual conversion path
• Consent and customer data terms checked
• Counting, value defaults, and bidding settings reviewed

2. Configure the exact Simple CAPI website event

Choose Lead for the intended form and save its exact public URL and a unique form selector. Choose Schedule for the successful booking confirmation page. Put the script on that page, not the calendar-start page. A cross-domain embedded form may need installation inside the form's own page; the outer page cannot automatically read it.

Enter the Conversion ID and Label, country, source label, and default currency. There is no manual amount to invent. Simple CAPI reads an actual conversion amount from supported form fields or explicitly marked booking data. The default currency is only a fallback when an amount exists; without a valid amount, both value and currency are omitted.

The standard setup uses the Google browser tag. Optional server credentials are not required for that path. If the page already has Google tags, check that the same conversion is not also triggered by another script or tag-manager rule.

• One saved website action
• One exact public page
• One unique Lead form or Schedule confirmation page
• Customer data available at the trigger
• Actual value only when supplied by the conversion
• One installation per event

3. Test the live page, then review Google diagnostics

Open Google Tag Assistant, connect to the published page, and complete an advertiser-controlled test form or booking. Inspect the conversion destination, the enhanced-conversion fields, and consent state. Test the accepted and denied consent paths without sending customer data you are not authorized to use.

Also test an unrelated form, a failed submission, and a confirmation-page reload. Simple CAPI's Lead listener observes a browser form submission; that alone does not prove an asynchronous form was accepted by the website. Its Schedule listener observes the confirmation page and has five-minute session reload protection. Verify that these triggers match how your site actually completes the action.

In Google Ads, open Goals, then Summary and the conversion action's Details and Diagnostics. Review the data-quality alerts as Google processes traffic. A successful browser test is useful evidence, but it does not guarantee an immediate reportable conversion, a match to a customer, or credit to an ad.

• Correct Conversion ID and Label
• One intended event for the successful action
• No event from an unrelated form
• Available enhanced-conversion fields and correct consent
• Expected amount or no amount, rather than an invented value
• Google Ads diagnostics checked after traffic is processed

4. Fix the problem shown by the test

Start with the failed stage. If no conversion request fires, inspect the page and trigger. If a request fires without useful matching fields, inspect where the data is read. If Google receives the request but reports an issue, follow that action's diagnostic alert instead of adding another copy of the tag.

• No event: check the saved URL, unique form selector, published script, and any paid-traffic-only setting
• Missing customer fields: check whether the form clears them before tracking, runs in another domain's iframe, or has no usable email or address
• Wrong fields: correct formatting and verify the fields belong to the current lead, especially on a booking confirmation page
• Denied consent: verify the consent flow; do not force permission just to make matching fields appear
• Duplicate totals: inspect other tags and separate website or upload actions used for bidding
• Browser-only status: no server upload is configured; this is not proof that the browser tag succeeded
• API rejection: review the returned error, action type, account access, and historical upload eligibility

5. Treat offline lead imports as a separate setup

If you want to measure a later qualified lead or closed sale, connect the system that records that outcome to a supported Google import. Use the corresponding offline conversion action, outcome time, and matching customer identifiers. Simple CAPI's website script does not read future changes in your sales system.

Simple CAPI's optional server path uses uploadClickConversions with a separate UPLOAD_CLICKS action. Google restricts this method to existing eligible integrations under its June 15, 2026 access change. New offline integrations should use Google's Data Manager API, which Simple CAPI does not currently implement. Check eligibility before entering advanced connection details.

A saved-configuration check does not test Google credentials or deliver a conversion. Before relying on any upload, verify an advertiser-controlled event in Google Ads and review how the website and uploaded actions affect bidding. Their shared transaction ID does not deduplicate different actions.