serkankaya.
Türkçe sürüm
Let’s work together ↗

Enhanced Conversions for Leads Setup: A GTM and CRM Guide

What are enhanced conversions for leads and how do you set them up? Hashed email capture in GTM, CRM uploads, Data Manager and privacy steps in one guide.

Enhanced conversions for leads is a measurement feature that tells Google Ads, through hashed customer data, whether a lead that came in through a form later became a sale. When the form is submitted, the tag hashes details such as the email address and sends them to Google. When the lead converts, the same data is uploaded from the CRM and Google ties the conversion to the right ad click.

In this post I explain how the feature works, how it differs from classic offline import, and how to set it up with Google Tag Manager. Then I cover the CRM upload methods, the 2026 changes, privacy notes and my pre-launch checklist.

How do enhanced conversions for leads work?

Short answer

How do enhanced conversions for leads work?

A user clicks an ad and fills in a form on your site. The Google tag hashes details such as the email address and sends them to Google. The lead is stored in your CRM, and when it converts, the same hashed data is uploaded to Google Ads with the GCLID. Google matches it with the tag data and signed-in Google Accounts and attributes the conversion to the campaign.

Google describes the feature as an upgraded version of offline conversion import.[1] Classic import relies only on the click identifier, the GCLID. Enhanced conversions for leads also uses user-provided data on top of that identifier.

User-provided data is the email, phone number or address a person types into a form. It does not reach Google as plain text; it is hashed with SHA-256 first. SHA-256 is a hash function that turns text into an irreversible 64-character digest.

Ad click Form and hashed email Sale in the CRM Google Ads matching
The tag sends hashed data at form time; the CRM uploads the same data at sale time, and Google joins the two ends.

According to Google, when you use server-side Google Tag Manager or the Google tag gateway, user data is encrypted before Google receives it.[1] For now this encryption applies only to Google Ads tags. Google says it performs the matching inside a confidential computing environment.[1] I covered the general logic of a server-side setup in my server-side tracking guide and the setup itself in my server-side GTM setup post.

How is it different from classic offline import?

Classic offline import links a sale to an ad click only through the GCLID, while enhanced conversions for leads adds a second matching path through a hashed email and phone number. The difference is whether the conversion is lost when the click identifier is lost.

In practice the GCLID can disappear in many places. The form may fail to fill the hidden field, the CRM integration may not pass the field on, or the user may return on another device. In those cases the hashed email becomes a backup key for matching.

Classic offline import

  • Matching relies on the GCLID alone
  • If the GCLID is lost in the form or CRM, the conversion does not match
  • No extra tag is needed on the site
  • A hidden form field is required to store the GCLID

Enhanced conversions for leads

  • Uses hashed email and phone alongside the GCLID
  • Matching is still attempted with user data when the GCLID is missing
  • Needs a tag that collects hashed data on the form
  • The tag also collects the GCLID automatically
Based on Google's enhanced conversions for leads documentation.

Google recommends that you keep sending the GCLID regardless of the implementation method.[2] If you do not collect user-provided data with a tag, the GCLID becomes required.[2] So the two methods are not alternatives; enhanced conversions for leads is a layer on top of offline import.

What do you need before you start?

Before setting up enhanced conversions for leads, you should know which URLs host your lead forms, whether each form has a unique customer field, and whether auto-tagging is on in Google Ads. Google also requires you to accept the customer data terms.[2]

Google recommends the email address as the matching key. Its reasoning: an email is unique and rarely gets reformatted in a CRM.[2] If you use a phone number, it must include the country code; the tag strips symbols and dashes on its own.[2] Collecting both is recommended to improve match rates.

The point people often skip is the sales process itself. If your CRM does not clearly define “qualified lead” and “sale” stages, there is no meaningful conversion to upload. A qualified lead is a prospect whose need, budget and timing the sales team considers a good fit. Google also recommends that lead generation advertisers use the qualified or converted lead goals for offline measurement.[2]

How do you set up enhanced conversions for leads with GTM?

To set up enhanced conversions for leads with Google Tag Manager, you turn the feature on in Google Ads and accept the customer data terms, add a Conversion Linker tag, and create a “Google Ads User-Provided Data Event” tag that fires on form submission. Then you test the setup in preview mode and publish the container.[2]

  1. Turn on the feature and accept the terms

    In Google Ads, open conversion settings from the Goals menu and turn on enhanced conversions for leads. Read the customer data terms and accept them on behalf of your company. If conversions are tracked in a manager account, the terms must be accepted from that account.

  2. Add a Conversion Linker tag

    Set up a Conversion Linker tag that fires on every page a user may land on after an ad click. This tag writes the click information from the URL into a first-party cookie.

  3. Choose the data source

    Create a User-Provided Data variable and pick its type: automatic, manual or code. Automatic collection cannot capture phone numbers; if you need the phone, choose manual or code.

  4. Attach the tag to form submission

    Create a new Google Ads User-Provided Data Event tag, enter your Google Ads ID in the Conversion ID field and select the variable. Use the moment the form is successfully submitted as the trigger.

  5. Test and publish

    In GTM preview mode, submit the form with a real test record and confirm the tag fires with user data. Then publish the container and watch the diagnostics report.

Google’s documentation lists three collection methods.[2] Automatic collection finds user data in the site code on its own and needs no special skills. Manual configuration points to the field with a CSS selector or JavaScript variable and requires HTML and CSS knowledge. Code configuration adds a snippet that sends consistently formatted data, and Google calls it the best choice for accuracy.[2]

I usually go with code configuration. Pushing the email and phone to the dataLayer when the form is successfully submitted is far more robust than a CSS selector. When the site design changes, the selector breaks; the dataLayer event does not. If you do use a selector, give the field a fixed HTML ID, as Google suggests.[2]

// Must run AFTER the form has been saved successfully on the server
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
  event: 'lead_form_submit',
  user_data: {
    email: '[email protected]',     // email from the form
    phone_number: '+905551112233'    // with country code, in E.164 format
  }
});

In GTM you create a custom event trigger for this event and data layer variables for user_data.email and user_data.phone_number. You then open the User-Provided Data variable as the “manual” type and map those variables to the matching fields. If you use the Google tag directly on the page, you can build the same logic with gtag.js.[3]

How do you upload conversions from the CRM to Google Ads?

When a lead moves to a sale or a qualified stage, the same customer data collected on the form is uploaded to Google Ads together with the conversion name and time. You can use Google Ads Data Manager connectors, file uploads or the Data Manager API for this.[2]

According to Google, an upload should contain at least the GCLID (required if you do not use a tag), at least one piece of user data (email, phone or address), the conversion name, the conversion time and the conversion goal.[2] Recommended fields are the order ID, conversion value, currency and the consent field. Google notes that leaving the consent field empty may result in conversions that cannot be attributed.[2]

FieldStatusNote
Email and/or phoneRequired (at least one)Normalized and hashed with SHA-256
GCLID, GBRAID, WBRAIDRecommendedGCLID is required without a tag
Conversion name and timeRequiredTime is written with a time zone
Order IDRecommendedPrevents duplicate uploads
Value and currencyRecommendedTRY code for Turkish lira
Consent (ad_user_data)RecommendedGRANTED or DENIED

This table is based on the field list in the Google Ads Help Center and the Google Ads API documentation.[2][4] How far back Data Manager reads depends on the connector. According to Google, Google Cloud Storage, Amazon S3, HTTP, SFTP and Google Sheets sources read conversions from the last 90 days on every run.[2] For Salesforce and HubSpot, the first successful run takes the last 14 days, and later runs pass on only the changes.[2]

How should data be normalized before hashing?

Normalizing means bringing data into one standard format before hashing it. A hash function produces a completely different result even if a single letter differs. That is why “[email protected] ” on the form and “[email protected]” in the CRM will never match unless both are normalized.

According to the Google Ads API documentation, emails are trimmed, lowercased and hashed with SHA-256 in hexadecimal format.[4] For gmail.com and googlemail.com addresses, dots before the @ sign and suffixes starting with + are also removed.[4] Phone numbers are written in E.164 format, starting with +90 for Turkey and without spaces, and then hashed.[4]

import { createHash } from 'node:crypto';

const sha256 = (v) => createHash('sha256').update(v).digest('hex');

function normalizeEmail(raw) {
  let [user, domain] = raw.trim().toLowerCase().split('@');
  if (domain === 'gmail.com' || domain === 'googlemail.com') {
    user = user.split('+')[0].replace(/\./g, '');
  }
  return `${user}@${domain}`;
}

// Simple example for a Turkish number: 0555 111 22 33 -> +905551112233
function normalizeTrPhone(raw) {
  const digits = raw.replace(/\D/g, '').replace(/^0/, '');
  return digits.startsWith('90') ? `+${digits}` : `+90${digits}`;
}

const hashedEmail = sha256(normalizeEmail(' [email protected] '));
const hashedPhone = sha256(normalizeTrPhone('0555 111 22 33'));

Two more details matter when you upload through the API. Google says a conversion can carry up to five user identifiers.[4] If you send a GBRAID or WBRAID without a GCLID, the user data field is ignored.[4] You should also leave the custom variables field empty on conversions that contain user data.[4]

What changed in enhanced conversions for leads in 2026?

Two major changes happened in 2026: Google combined enhanced conversions for web and for leads into a single setting in April 2026, and from June 15, 2026 it moved offline conversion and enhanced conversions for leads uploads to the Data Manager API.[1]

With the unified setting, Google Ads accepts user-provided data from website tags, Data Manager and API connections at the same time.[1] According to Google, you no longer need to choose between implementation methods, and all users have been migrated to this setting.[1] So you may not find the “which method should I use” choice that some help pages still show.

The API change affects developers directly. According to the Google Ads API documentation, after June 15, 2026, UploadClickConversions requests fail for access that sent no upload requests during a specific period.[4] Google recommends the Data Manager API for new integrations.[4] The Data Manager API is an API for sending first-party conversion and audience data to Google’s advertising products through a single integration.[5]

I explained how the consent signal is managed on the web side in my Consent Mode v2 post. For the same user, the consent status in the web tag and the consent field in the CRM upload should never contradict each other.

How do you test the setup, and which mistakes are common?

An enhanced conversions for leads setup is verified with the enhanced conversions diagnostics report in Google Ads.[1] The report shows whether the tag is sending user data and flags implementation issues. Google also publishes a separate implementation checklist.[1]

These are the mistakes I see most often in the field:

  • The trigger fires at the wrong moment. The tag fires when the button is clicked, but the form fails validation. The result is wrong or empty data.
  • The email on the form differs from the CRM. The sales team corrects the email in the CRM or types a different address. Storing the original form email in a separate field solves this.
  • Phone numbers are saved without a country code. The “0555…” format is common in Turkey. If that number is hashed without converting it to E.164, it will not match.
  • The GCLID is never stored. Even though the tag collects the GCLID, Google recommends that you keep importing existing GCLIDs.[2]
  • The same sale is uploaded twice. Without an order ID, repeated uploads cannot be told apart.
Enhanced conversions for leads pre-launch check0/9

Which businesses is it worth it for?

Enhanced conversions for leads makes sense for businesses where the sale happens off the site after a form and is tracked in a CRM. Health tourism, education, real estate, B2B software and financial services fit this model. For e-commerce with direct purchases on the site, enhanced conversions for web is usually enough.

In health tourism the flow usually runs from lead to consultation, deposit and procedure. Which of these stages goes to Google Ads is a business decision. Making form submission the main goal grows volume but does not guarantee quality. Sending a deeper stage, such as consultation or deposit, shows bidding the real value. In my health tourism marketing work, I treat this decision as the first item of the measurement plan.

Conclusion

Enhanced conversions for leads builds the missing link between the form and the sale with a hashed email and phone number. The technical part of the setup is a few GTM tags and an upload flow. The real work is defining CRM stages, normalizing data correctly and carrying the consent status consistently from start to finish.

To get started, first check whether your CRM stores the form email, phone and GCLID in separate fields. If you want to see how measurement and bidding strategy fit together, take a look at my performance marketing page.

Key terms

Enhanced conversions for leads
Enhanced conversions for leads is a Google Ads measurement feature that strengthens offline conversion import with hashed customer data such as email and phone. Data collected on the form is matched with the same data uploaded from the CRM when the lead becomes a sale.
User-provided data
User-provided data is first-party information such as an email address, phone number or postal address that a person enters into a form themselves. In enhanced conversions this data is hashed with SHA-256 before it is sent to Google and matched against signed-in Google Accounts.
SHA-256
SHA-256 is a cryptographic hash function that turns any text into an irreversible 64-character hexadecimal digest. Google Ads requires email addresses and phone numbers to be normalized and then hashed with SHA-256 for enhanced conversions.
Qualified lead
A qualified lead is a prospect whose need, budget and timing the sales team considers a good fit, and who is likely to become a customer. In Google Ads it can be chosen as an offline conversion goal and gives bidding a more meaningful signal than a form submission.

Frequently asked questions

What are enhanced conversions for leads?

Enhanced conversions for leads is an upgraded version of offline conversion import that adds hashed customer data such as email and phone. When a form is submitted, the tag sends hashed data to Google. When the lead becomes a sale, the same data is uploaded from the CRM and Google matches the conversion to the right ad click.

Do I still need the GCLID with enhanced conversions for leads?

Google recommends that you keep sending the GCLID regardless of your implementation method. If you do not collect user-provided data with a tag, the GCLID is required. And if you upload through the API with a GBRAID or WBRAID but no GCLID, the hashed user data is ignored.

What is the difference between enhanced conversions for web and for leads?

Enhanced conversions for web strengthens conversions that complete on the site, such as purchases, with hashed data. Enhanced conversions for leads measures sales that happen off the site after a form, for example over the phone or at a clinic. As of April 2026, Google has combined both features into a single setting.

Which data should I send with enhanced conversions for leads?

Google recommends the email address, because it is unique and rarely gets reformatted in a CRM. Sending a phone number with its country code alongside the email increases the chance of a match. The upload should also include the conversion name, time, GCLID, order ID, value and consent field.

Are enhanced conversions for leads KVKK compliant?

The feature hashes data with SHA-256 before sending it, but hashing alone does not make you compliant with KVKK, Turkey's data protection law. The form needs a privacy notice and, where required, explicit consent, and the consent status must be reflected in the upload's consent field. Ask a data protection specialist for a legal assessment.

Sources

  1. Google Ads Yardım: About enhanced conversions for leads
  2. Google Ads Yardım: Configure Google Tag Manager for enhanced conversions for leads
  3. Google Ads Yardım: Configure the Google tag for enhanced conversions for leads
  4. Google Ads API: Manage offline conversions
  5. Google for Developers: Data Manager API