> ## Documentation Index
> Fetch the complete documentation index at: https://docs.erdo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Ads Enhanced Conversions

> Match landing-page leads and conversion uploads using email and phone identifiers.

Erdo's shared landing-page kit supports Enhanced Conversions for leads when a
page has a Google Ads lead conversion configured. After a successful submission,
the kit supplies the submitted email and phone to the Google tag immediately
before the lead conversion. Google hashes those identifiers for matching.

Email is trimmed and lowercased. Phone numbers use international E.164 format,
including the country code, such as `+13055550100`. Blank or invalid values are
omitted. The form's country selector supplies an international phone number.

For two-step forms, the contact submission on Step 1 sends the conversion once.
Completing Step 2 enriches the lead without sending another conversion. Modal
opens and phone taps send no lead identifiers. The kit clears the Google tag's
user data after the lead conversion so later interactions do not inherit it.

## Consent still applies

EU, UK, EEA and Swiss pages keep advertising consent denied until the visitor
accepts through the consent banner. Google's `ad_user_data` consent setting
controls use of the identifiers; Enhanced Conversions does not bypass it.

Contact details are not added to GA4 event parameters. Follow-up pages do not
send lead details from personalized links to Google tags.

## Conversion uploads

Qualified-lead uploads can include the source lead's optional `email` and `phone`
alongside the existing click identifier and conversion details. Erdo normalizes
and SHA-256 hashes these values before sending them to Google's Data Manager
API. The request uses hex-encoded `emailAddress` and `phoneNumber` identifiers;
raw contact details are not sent in the upload. Blank or invalid identifiers
are omitted, and existing click matching and transaction IDs remain unchanged.

Your Google Ads conversion settings and consent configuration must also support
Enhanced Conversions. Sending an event is not proof that Google matched a lead
or attributed a conversion; review the conversion action's diagnostics in
Google Ads. Historical uploads are not automatically resent by this change.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.