Enhanced Conversions for Leads

Enhanced conversions for leads is Google's upgrade to offline conversion import for businesses that turn website forms into sales later. The visitor clicks your ad, lands on your site, and fills out a form. Your Google tag hashes the user-provided data, such as an email address, and sends it to Google. You also store the lead in your CRM. When that lead becomes a customer, you import the same hashed data with the outcome, plus the GCLID (Google's click ID) where you have it, and Google connects the sale to the original ad click. The GCLID is the click ID Google adds to your landing page address when auto-tagging is on. Capturing it in a hidden form field is still worth doing, because Google recommends including it whenever you can, alongside the hashed details.

Setup has two steps in Google's documentation. First, configure the Google tag, either directly or through Google Tag Manager, to capture hashed user-provided data from the form. Second, automate the offline import using the same hashed data, through Google Ads Data Manager, since uploads through the Google Ads API are blocked from June 15, 2026. Google matches your hashed data against the hashed lead data your site collected and against signed-in Google accounts that engaged with the ad. That matching also supports reporting for engaged-view and cross-device conversions, which a click ID alone cannot reach. Because the feature relies on your own hashed data, it also helps when the lead later calls or visits on another device. A click ID lives in one browser, while an email address follows the person across devices.

Timing and platform changes matter here. Uploads that include personal data have a 63-day limit after the associated last click, shorter than the 90 days for GCLID-only imports. Google also says that from April 2026 enhanced conversions for web and for leads are merged into one setting. Starting June 15, 2026, offline conversion import and enhanced conversions for leads uploads move to the Data Manager API and are blocked in the Google Ads API. Legacy file formats need to be upgraded. Treat the Data Manager route as the default for new work. Older tutorials describe uploading through the Google Ads API or spreadsheets, and Google says those routes are changing, so confirm which method your account supports before building anything.

Most failures come from the data, not the settings. Google says common problems are missing or incorrectly formatted data and faulty tag implementation. If the email you upload does not match what the tag hashed at form submission, there is no match. Sending different fields at upload than at capture, or capturing the field on one page and the form submit on another, has the same effect. Another error is waiting for the final closed deal when the sales cycle is longer than 63 days, so no upload ever lands inside the window. Be careful about which email you hash. If the form collects a work email and the CRM later stores a personal one, the hash will not match. Pick one field that uniquely identifies the lead and keep it stable from capture to upload.

To use it well, define the lead stages you can report reliably, such as qualified lead and closed deal, and upload them as separate conversions with values. Google recommends the diagnostics report and an implementation checklist after launch. This week, check that your form field names match what the tag collects, verify the same email format reaches your CRM, and run a small test upload. Only then start bidding on the imported conversions, since Smart Bidding learns from whatever you upload. Start with a secondary conversion action for the first few weeks so you can compare counts without changing bidding, then promote it to primary once the numbers look right.