How to Set Up Google Ads Enhanced Conversions for Lead Generation
Set up Enhanced Conversions for lead generation by defining the lead that should count, capturing an approved source identifier, sending only consented customer data, and connecting the event to the CRM without creating duplicates. Keep the raw lead, qualified stage, opportunity, and won outcome distinct so the campaign can learn from a useful signal without overstating sales results.
Use Google’s Enhanced Conversions best practices, web conversion setup, and offline conversion guidance as the technical references. The steps below assume the lead owner and privacy owner have approved the data path.
1. Write the lead event contract
State exactly what the conversion means: a valid form submission, booked meeting, connected call, quote request, trial request, or another observable milestone. Define the required fields and the system that proves the event happened. Then name the later stages that matter, such as sales acceptance, qualified lead, opportunity, and won account.
Choose the counting unit. A consumer business may count a person; an enterprise business may count a company or opportunity. Decide whether a repeat form from the same account is a new lead, a duplicate, or a new product inquiry. Include rules for spam, test records, existing customers, and merged CRM contacts.
Do this before opening the Google Ads conversion-action screen. Enhanced Conversions improves an approved data signal; it does not decide whether a button click is a lead.
2. Map the lead path and current sources
Inventory every form, landing page, phone system, calendar, tag-manager container, analytics import, CRM connector, and offline upload. Record whether each source creates the lead, enriches it, or only reports it. Identify the current Google tag and any thank-you-page or generic URL triggers.
Select one authoritative lead trigger. A successful form response or server confirmation is usually stronger than a page view. A connected call may require a duration or qualification rule. A booked appointment should say whether a canceled or rescheduled slot still counts.
Find duplicate paths before adding a new tag. A form plugin, analytics import, CRM integration, and custom script can all report the same lead. Keep the source of truth in the event inventory and retire or reclassify unsupported duplicates.
3. Capture an approved source identifier
Work with the CRM owner to choose the identifier that can connect ad interaction, lead record, and later stage. Preserve it through redirects, multi-step forms, validation errors, domain changes, and CRM creation according to the approved data policy. Store it with lead or account ID, product, region, event time, and consent state where permitted.
Test a clean session, returning visitor, mobile form, embedded form, translated form, and a form that fails validation before succeeding. Verify that the source identifier is not overwritten by a later campaign parameter or lost when the form provider redirects to the CRM.
If the lead enters by phone or an offline channel, document the source-matching method separately. Do not force a browser identity into a call record when the business cannot prove that the two belong together.
4. Approve the customer-data fields
Enhanced Conversions should use only the first-party fields approved for the measurement purpose. The privacy owner should decide whether email, phone, or another supported field may be used, where it is collected, how it is normalized, what consent permits it, and when it is removed.
Read Google’s Enhanced Conversions best practices and add the organization’s own retention and access controls. Never send passwords, free-text responses, support notes, confidential account information, or sensitive product details in URLs, event parameters, or debug logs.
Use synthetic data for browser tests or an approved test record with restricted access. A technically valid field is not automatically a field the business is allowed to transmit.
5. Connect consent to the form event
Document the consent state needed for advertising-related measurement and test what happens when it is denied, granted before the form, granted after the landing page, or later withdrawn. Confirm that a server or CRM integration does not bypass the browser’s consent decision.
Run the test across regions, domains, language variants, and embedded forms. A consent banner on the landing page may not control a third-party form or call widget. Store the consent result and event result in the QA record without retaining raw customer values.
If the approved flow permits an event without customer data, keep that event separate from the Enhanced Conversions payload. Measurement should degrade gracefully when a visitor declines consent; the form should not fail because a matching field is unavailable.
6. Implement the web conversion action
Follow Google’s web conversion setup guide and Google tag guidance. Create a conversion action with a business name, counting choice, value rule, conversion window, and primary or secondary role that match the event contract.
Use a dedicated form-success or server-confirmed trigger. Do not rely on a generic page-view rule that can fire for a refresh or a direct visit. Make the lead ID, source identifier, approved customer-data fields, action name, timestamp, value, and consent state available only where the approved path allows them.
Keep raw lead and qualified CRM stage actions distinct. A lead event can fire in the browser; an offline stage should be created by the CRM or approved backend. If both are sent, define which is primary and how the team should read the layered counts.
7. Add CRM stages with a controlled import
When the sales cycle makes later quality important, use the CRM as the source of truth for accepted, qualified, opportunity, or won stages. Follow Google’s offline conversion guidance for the supported import process and start with a small test set.
Verify the identifier, record key, action name, stage time, value, currency, consent handling, and account match. Review accepted, rejected, duplicate, unmatched, and delayed rows. A CRM job that completes successfully can still associate a stage with the wrong account if the mapping is weak.
Do not import every CRM edit as a new acquisition. A qualification transition, reopen, owner change, or note update should follow the documented stage rule. Keep a history when the stage definition changes.
8. Choose a defensible value
For a raw lead, use a fixed proxy or expected value only if the assumptions are written. For a qualified lead or opportunity, use a historical acceptance or win-rate model with product, region, deal size, margin, and sales capacity when those inputs are reliable. Keep currency and date rules explicit.
Do not pass a quoted contract amount as expected revenue if the business usually discounts, loses, or renews differently. Do not call a research request a paid customer. Review the value when qualification policy, pricing, sales coverage, or close rate changes.
9. Test the complete lead journey
Use Tag Assistant with a safe test lead. Verify one event, correct action, approved data handling, source identifier, timestamp, value, consent state, and CRM record. Then follow the record through assignment, qualification, opportunity, and offline import.
Test success, validation failure, duplicate submit, abandoned form, refresh, mobile form, phone lead, calendar reschedule, existing customer, spam filter, CRM merge, missing identifier, consent denial, and delayed stage. Write the expected zero, one, or update result for each case.
Keep a restricted evidence record. The browser diagnostic proves only that a request was attempted; the CRM and downstream reconciliation prove whether the right lead was created and connected.
10. Reconcile before optimizing
Compare web or server lead events, Google Ads conversions, CRM records, accepted and qualified stages, opportunities, and won outcomes by source, product, region, and date. Explain differences from attribution windows, time zones, consent, ad blockers, spam removal, reporting delay, and CRM merges.
Monitor missing source identifiers, duplicate rate, import acceptance, time to qualification, value coverage, and lead-to-opportunity rate. If a form redesign raises leads but lowers acceptance, investigate the definition or experience before using the larger count to justify more budget.
Common setup errors
- Creating the action from a page view rather than a confirmed lead.
- Sending raw form data before consent or into unrestricted logs.
- Losing identifiers on redirects, validation errors, or CRM creation.
- Counting form, analytics, CRM, and call paths independently.
- Treating the raw lead and qualified stage as one conversion.
- Importing every stage edit as a new acquisition.
- Using a value model that sales or finance cannot explain.
- Testing only a successful desktop form.
Fix the event definition and identity path before changing bidding or adding more matching fields.
Lead-generation setup checklist
The setup is ready when the team can show the lead definition, counting rule, source of truth, identifier, approved fields, consent behavior, web trigger, CRM stage mapping, offline test, value model, duplicate rule, test matrix, and reconciliation result. Use the Enhanced Conversions checklist and best Enhanced Conversions for lead generation for companion reviews.
Start with one form and one CRM stage. Expand to other products or regions only after the original path remains explainable through a complete sales cycle.