Third-party cookie restrictions, browser privacy controls, consent choices, and fragmented customer journeys can make Google Ads conversion reporting less complete than the actual business results.
A visitor may click an ad, return days later, submit a lead form, and eventually become a customer without every step being connected in your advertising reports. You cannot recover every missing conversion, and privacy controls should never be bypassed to improve attribution.
However, a properly configured measurement setup can improve matching, communicate consent choices correctly, and help Google model some conversions when direct measurement is unavailable.
This guide explains how to configure Google Enhanced Conversions in Google Tag Manager (GTM), implement Consent Mode v2, choose between Basic and Advanced Consent Mode, and verify the setup before trusting the resulting conversion data.
Why Conversion Data Goes Missing
1. Distinguish tracking failure from legitimate measurement limitations
Traditional conversion tracking often depends on browser identifiers, advertising cookies, click IDs, and tags that run when a user completes an action. Privacy restrictions and consent decisions can limit the availability of these signals.
Common causes include:
- Cookie restrictions: Browser policies and privacy settings limit some forms of cookie-based tracking.
- Consent denial: Visitors decline advertising or analytics storage, restricting the associated measurement.
- Cross-device journeys: Someone clicks an ad on a phone but converts later on a laptop.
- Broken tracking: Conversion tags fire too early, fail to fire, or fire more than once.
- Inconsistent implementation: Google Ads and GA4 record overlapping events, or consent defaults are applied after other tags have already run.
Start by distinguishing a tracking failure from a legitimate measurement limitation. A missing conversion tag is an implementation problem. A conversion that cannot be directly attributed because the required identifiers are unavailable may be a measurement limitation.
What Google Enhanced Conversions Actually Does
Google Enhanced Conversions supplements existing conversion tracking with first-party customer information, such as an email address or phone number. Google uses this information to improve conversion matching and attribution.
2. Understand the SHA-256 matching process and requirements
When implemented correctly, the process works as follows:
- A customer completes a purchase or submits a lead form.
- Your website or GTM implementation captures eligible first-party customer data.
- The data is normalized and hashed using SHA-256 before being sent to Google.
- Google uses the hashed data to match eligible records with signed-in Google Accounts and relevant ad interactions.
- The matched information helps improve conversion measurement.
For example, a customer clicks a Google Search ad, later completes a purchase, and provides an email address. If the original click identifier is unavailable but the customer data can be lawfully used and matched, Enhanced Conversions may help Google attribute the purchase.
Hashing is not the same as anonymization
SHA-256 is a one-way cryptographic hashing algorithm. The same normalized input produces the same hash, allowing matching without sending the original email address in unhashed form through the Enhanced Conversions process.
However, hashed personal data should not automatically be treated as anonymous or exempt from privacy requirements. A hash can still be used for matching and may remain personal data under applicable laws. Your privacy notice must explain relevant sharing for advertising measurement, and consent must be obtained where required by applicable law.
Configure Enhanced Conversions in Google Tag Manager
3. Enable Enhanced Conversions in Google Ads
Before changing tags, confirm that your conversion event represents a genuine business outcome. In Google Ads:
- Open your conversion settings and select the relevant website conversion action.
- Enable Enhanced Conversions and review the applicable customer-data terms.
- Choose Google Tag Manager as the implementation method.
- Save the settings and note the conversion action used by your GTM tag.
4. Choose How GTM Will Collect Customer Data
| Method | How it works | Best suited for |
|---|---|---|
| CSS Selectors / DOM Elements | Reads a field or value from the rendered page | Data is available in a stable page element after submit |
| Data Layer Variables | Reads structured values pushed by the website | Forms or checkout flows already expose customer data to GTM |
| Developer-provided code | Supplies user data directly through the implementation | Greater control over formatting and event timing |
Prefer Data Layer variables when possible. They are usually less fragile than selectors tied to page layout or CSS classes.
5. Configure Data Layer Variables (Preferred)
A developer can push customer data into the Data Layer after a successful form submission:
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
event: "lead_form_success",
user_data: {
email: formEmail,
phone_number: formPhone
}
});In GTM, create Data Layer Variables for user_data.email and configure the user-provided data variable inside your conversion tag. Ensure data is only pushed after the application confirms a successful submission, and only when required consent conditions are satisfied.
Understanding Google Consent Mode v2
Consent Mode communicates a visitor's consent state to supported Google tags so that their behavior can adjust accordingly. It does not create a consent banner, decide what consent is legally required, or replace your Consent Management Platform (CMP).
6. Understand the Four Key Consent Types
| Consent type | What it controls |
|---|---|
ad_storage |
Advertising-related storage, including relevant cookies |
analytics_storage |
Analytics-related storage, such as cookies used for visit measurement |
ad_user_data |
Consent for sending user data to Google for advertising purposes |
ad_personalization |
Consent for personalized advertising and remarketing |
7. Apply Default Consent States Before Tags Fire
A common default-denied configuration for a site whose policy requires consent before these uses looks like this conceptually:
gtag('consent', 'default', {
ad_storage: 'denied',
analytics_storage: 'denied',
ad_user_data: 'denied',
ad_personalization: 'denied'
});In GTM, use a supported CMP integration or consent-mode template. Ensure that defaults are applied before other tags run (using the Consent Initialization trigger). When a visitor makes a choice, your CMP must update the applicable consent states to granted.
Basic vs. Advanced Consent Mode
8. Choose the Appropriate Consent Mode Implementation
The main difference is what happens before a visitor grants consent.
| Behavior | Basic Consent Mode | Advanced Consent Mode |
|---|---|---|
| Google tags before consent | Blocked until the required interaction or consent | Load with configured default consent states |
| Data sent before consent | No data is sent by blocked Google tags | Consent signals and limited, cookieless measurement pings may be sent |
| Measurement without consent | Relies on available data and general modeling where eligible | May support more detailed, advertiser-specific modeling where eligible |
Basic Consent Mode may be appropriate where your legal or organizational requirements call for Google tags to remain entirely inactive before consent. The trade-off is less information available for conversion modeling.
Advanced Consent Mode is not permission to collect everything before consent. A cookieless ping is still a data transmission, so its use must be reviewed against applicable privacy law and your organization's requirements.
Verify Consent Signals and Conversion Integrity
9. Verify the Default State in Tag Assistant
Do not assume Consent Mode is working just because the CMP banner appears. Open Tag Assistant with a fresh session, select the earliest Consent event in the Summary, and confirm all four parameters show denied initially (unless regional rules dictate otherwise) before relevant tags fire.
10. Verify Visitor Choices Update the Signals
Test each banner outcome (Accept All, Reject All, Custom Preferences). In Tag Assistant, inspect the consent update event and compare the new states (granted) with your action. Also inspect individual tags to ensure they respected the required consent checks.
11. Confirm Enhanced Conversions Respects Consent
Submit a test lead while advertising consent is denied. Confirm that the conversion fires appropriately for your mode (Basic vs Advanced) and that Enhanced Conversions is not sending user data (like email hashes) when ad_user_data is denied.
A Privacy-Compliant Conversion Recovery Workflow
12. Execute the Full Diagnostic and Implementation Pipeline
Use this sequence when auditing an existing Google Ads account:
13. Wait 30 Days to Evaluate Reporting Quality
After publishing, monitor Enhanced Conversions diagnostics and conversion reporting. Google notes that it can take time—often around 30 days—to fully evaluate the impact in reporting and modeling.
Compliance Checklist: What Not to Do
14. Avoid the 8 Critical Compliance Mistakes
ad_user_data is deniedgranted simply to improve reportingNote: The exact legal obligations depend on your jurisdiction. Assess applicable cookie and data-protection requirements with a qualified privacy professional.
Conclusion
Enhanced Conversions and Consent Mode v2 solve different parts of the measurement problem. Enhanced Conversions improves matching with eligible first-party customer data, while Consent Mode communicates user choices and adjusts supported Google tags accordingly.
Together, they can improve measurement quality and support eligible conversion modeling—but only when conversion events are accurate, consent signals are implemented correctly, and personal data is handled lawfully.
When you audit your own Google Ads setup, are you losing conversions because tracking is broken, because consent limits measurement, or because your current attribution setup cannot connect the customer journey?