Google Ads Enhanced Conversions Unification (June 2026): What Advertisers Must Migrate Before the Deadline

Google Ads Enhanced Conversions Unification: The June 2026 Migration That Most Advertisers Are Sleeping On

In April 2026, Google quietly published an update to its enhanced conversions documentation that flew under most advertisers' radar. Starting June 2026, Google Ads will merge "Enhanced Conversions for Web" and "Enhanced Conversions for Leads" into a single unified feature. The method-selection screen will disappear. The settings UI will collapse. And the path Google now actively recommends for new implementations — Enhanced Conversions for Leads via the Data Manager API — comes with a tighter, less-forgiving upload window than what most lead-gen advertisers are used to.

If you are still using standard offline conversion imports with GCLID — the original method most lead-gen advertisers, B2B SaaS companies, and CRM-driven funnels were built around — you have a window of roughly six weeks to either migrate or accept that your Smart Bidding signal will degrade.

This is, candidly, not a marketing claim. It is what the official Google Ads documentation now states. At TagSpecialist, we have already started migration audits for clients on the older offline-import flow, and the gap between what teams think they're doing and what Google now expects has been larger than we anticipated.

This post walks through what is actually changing, why it matters for your reported conversions and your Smart Bidding ROAS, and the exact technical steps to migrate before the June cutover.

What's Actually Changing in June 2026

Three concrete shifts are landing:

1. The method selection screen disappears. Today, when you set up Enhanced Conversions, you choose either "Web" or "Leads" as the source. Starting June 2026, that choice goes away. The Google Ads UI shows a single unified Enhanced Conversions toggle. Advertisers will configure data sources — website tags, Data Manager, or API — without explicitly selecting a "method".
2. Multiple data sources become concurrent, not exclusive. Starting April 2026 (already live), Google Ads accepts user-provided data from website tags, the Data Manager API, and direct API connections simultaneously rather than forcing you to pick one. This is good news — it means redundancy works. Send the same hashed email from your website tag and your CRM offline upload, and Google will deduplicate.
3. The Data Manager API is now the official upgrade path. Google's own developer documentation now states it does not recommend new offline conversion workflows using the legacy Google Ads API. Soft-deprecation, not formal — but the writing is on the wall. New work should target the Data Manager API.

The takeaway: the unification itself is mostly a UI cleanup. The real story is what Google is strongly steering you toward — and the implementation differences between the old way (GCLID-based offline imports) and the new way (Enhanced Conversions for Leads with hashed PII) are not trivial.

The Problem: What Standard Offline Conversion Imports Get Wrong in 2026

Here is the architecture that most lead-gen and B2B advertisers built between 2019 and 2024:

Form Submission → CRM (HubSpot / Salesforce / Pipedrive)
                          │
                          ▼
                 Wait for SQL / MQL / closed-won
                          │
                          ▼
              Daily/weekly CSV export with GCLID + value
                          │
                          ▼
         Google Ads → Conversions → Upload → Smart Bidding

This worked well for years. It still works today. But it has three structural weaknesses that did not matter much in 2022 and matter a lot in 2026:

Weakness 1: The 90-Day Upload Window Already Misses Long Sales Cycles

Standard GCLID-based offline conversion imports have a hard limit: conversions uploaded more than 90 days after the original ad click will not be imported. For most B2C and short-cycle B2B advertisers, this is fine. For longer-cycle SaaS, education, healthcare, financial services, and enterprise sales — where the deal closes 4-9 months after the first click — a meaningful share of revenue is silently dropped from the bidding signal.

Weakness 2: GCLID Itself Is Less Reliable in 2026

GCLID is captured at the moment of ad click and stored on the destination URL. If a user clears cookies, copies the link without the GCLID, switches devices before submitting the form, or hits the form via a referral that strips query parameters, the GCLID is gone — and the conversion can never be tied back to the original click. With ITP now capping cookie lifetime at seven days on Safari, and Firefox enforcing similar limits, the GCLID-on-page approach has degraded materially over the last 24 months.

Weakness 3: The New Replacement Has a 63-Day Window

Here is the part that catches teams off-guard. When you migrate from GCLID-based offline imports to Enhanced Conversions for Leads, you gain match accuracy through hashed first-party data (email, phone) — but the upload window drops from 90 days to 63 days. This is per Google's published guidelines:

Method	Upload Window	Match Mechanism
Standard offline conversions (GCLID)	90 days	Click-time GCLID
Enhanced Conversions for Leads	63 days	Hashed email/phone + GCLID

If your team is on a weekly batch upload cadence, you have just lost roughly a third of your tolerance window. Daily syncs are no longer optional. Anything slower than a 24-hour upload cadence will start losing late conversions to the 63-day cliff.

The Impact: Why This Migration Is About Smart Bidding ROAS, Not Just Compliance

A common misconception we hear in TagSpecialist audits: "Enhanced Conversions is a privacy feature; it doesn't change my bidding."

That is incorrect. Enhanced Conversions feed directly into Smart Bidding. The richer the conversion signal — and the higher the match rate between your offline conversions and Google's identity graph — the more accurately Google can model the lookalikes, optimize bids, and find similar high-intent users.

Three measurable effects:

1. Match rate improvement. Hashed email + phone match rates on Google's graph typically run 5-15 percentage points higher than GCLID-only matching. That improved match rate flows directly into Smart Bidding optimization quality. Google has cited meaningful conversion lift on the upgrade across multiple advertiser case studies, though the exact lift varies materially by industry and sales motion.
2. Smart Bidding signal density. Advertisers running tCPA or Maximize Conversions strategies need a steady cadence of high-confidence conversions. When match rate improves, Smart Bidding learns faster and stabilizes optimization at lower CPAs. Conversely, if you let your conversion signal drift to zero in June 2026 because you didn't migrate in time, your bidding strategies will revert to broader, less-targeted optimization.
3. Cross-device closure. GCLID-only matching breaks when the lead clicks on mobile and converts on desktop (or vice versa) without crossing a device-bridging touchpoint. Hashed email matches across devices natively, recovering attribution that GCLID-only flows simply cannot see.

For an enterprise advertiser running $50K/month on Google Ads Lead Gen, the difference between properly migrated Enhanced Conversions for Leads (with daily sync) and a stale GCLID-only flow that limps through June 2026 is, in TagSpecialist's experience, 15-25% of attributable closed-won revenue showing up in the bidding signal. The bidding strategy adjusts, and over 60-90 days, CPA falls and conversion volume rises.

The Solution: A Step-by-Step Migration to Enhanced Conversions for Leads

Here is the migration path TagSpecialist runs for clients on the legacy GCLID-import flow. The pattern is the same whether your CRM is HubSpot, Salesforce, Pipedrive, or a custom Postgres-backed pipeline.

Step 1: Capture Email at Form Submit on Every Lead-Gen Page

The new flow requires a hashed email (and ideally phone, name, address) attached to every conversion. That means: every form on your site must capture and emit email reliably, even if the user submits with auto-fill or a third-party form builder.

Two implementation choices, depending on stack:

Option A — Pure GTM (recommended for most)

window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
  event: 'lead_submit',
  user_data: {
    email_address: document.querySelector('#email').value.trim().toLowerCase(),
    phone_number: document.querySelector('#phone').value.replace(/\D/g, ''),
    address: {
      first_name: document.querySelector('#first_name').value.trim().toLowerCase(),
      last_name:  document.querySelector('#last_name').value.trim().toLowerCase(),
      country:    'us',
      postal_code: document.querySelector('#zip').value.trim()
    }
  }
});

Then enable Enhanced Conversions on your Lead conversion action in Google Ads. The Google tag will hash the values automatically and send them with the conversion.

Option B — Server-side enrichment via sGTM

If you are already running a server container on Cloud Run or Stape (which we recommend for any setup spending $10K+/month on Google Ads), the cleaner pattern is to capture the email server-side, hash it server-side, and pass it via the Measurement Protocol with the conversion. This avoids ad blockers stripping the lead event entirely. We cover this in Server-Side Tagging Best Practices 2026.

Step 2: Stand Up Daily CRM-to-Google-Ads Sync via Data Manager API

For closed-loop conversion uploads (the moment a lead becomes SQL or closed-won), the replacement for the legacy "upload CSV in the UI" flow is the Data Manager API. Three operational requirements:

1. Daily cadence, not weekly. With the 63-day window, weekly batches will drop late conversions silently. Schedule a Cloud Scheduler / Cloud Function / Airflow DAG to sync every 24 hours.
2. Send hashed email + GCLID together. Sending both improves match rate beyond what either signal achieves alone. Always include both when you have them.
3. Send the conversion timestamp at lead-creation, not closure. This is a subtle but critical point. The conversion's conversion_date_time should be the moment the lead converted (form submit), not the moment the deal closed. The 63-day window is measured from ad click to conversion timestamp, not from upload.

Skeleton of a Data Manager API offline upload (Python):

from google.ads.googleads.client import GoogleAdsClient
import hashlib

def hash_normalized(value: str) -> str:
    return hashlib.sha256(value.strip().lower().encode("utf-8")).hexdigest()

def upload_lead_conversion(client, customer_id, conversion_action_id, lead):
    conversion_upload_service = client.get_service("ConversionUploadService")

    user_identifiers = []
    if lead.email:
        identifier = client.get_type("UserIdentifier")
        identifier.hashed_email = hash_normalized(lead.email)
        user_identifiers.append(identifier)
    if lead.phone:
        identifier = client.get_type("UserIdentifier")
        identifier.hashed_phone_number = hash_normalized(lead.phone)
        user_identifiers.append(identifier)

    click_conversion = client.get_type("ClickConversion")
    click_conversion.conversion_action = client.get_service(
        "ConversionActionService"
    ).conversion_action_path(customer_id, conversion_action_id)
    click_conversion.conversion_date_time = lead.submit_time_iso  # NOT close time
    click_conversion.conversion_value = lead.deal_value or 0.0
    click_conversion.currency_code = "USD"
    if lead.gclid:
        click_conversion.gclid = lead.gclid
    click_conversion.user_identifiers.extend(user_identifiers)

    request = client.get_type("UploadClickConversionsRequest")
    request.customer_id = customer_id
    request.conversions.append(click_conversion)
    request.partial_failure = True

    response = conversion_upload_service.upload_click_conversions(request=request)
    return response

Schedule this against your CRM's "lead became SQL" or "deal moved to closed-won" stages, with a daily window covering the previous 24 hours plus a 7-day backfill buffer.

Step 3: Validate Match Rate in Google Ads, Not Just Upload Success

A successful upload (HTTP 200) does not mean a successful match. After 24-48 hours, navigate to Google Ads → Tools → Conversions → [your conversion action] → Diagnostics → Enhanced conversions. You'll see two numbers that matter:

• Coverage: percentage of conversions that include user-provided data. Should be 95%+ once your form-capture is solid.
• Match rate: percentage of those conversions that Google was able to match to a user. Should run 60-80% for B2C lead gen, 40-60% for B2B (lower because business emails match Google identity graphs less reliably).

If coverage is below 90%, your form data capture has gaps. If match rate is below 40%, your hashing or normalization is broken — the most common culprit is forgetting to lowercase before hashing, or leaving whitespace in phone numbers.

Step 4: Run Both Methods in Parallel for 30 Days, Then Cut Over

Google's April 2026 update explicitly supports concurrent data sources — you can run your legacy GCLID-based offline import and your new Enhanced Conversions for Leads pipeline simultaneously without double-counting. Google deduplicates by gclid + conversion_action + conversion_date_time.

A 30-day overlap window is the safe pattern:

• Days 1-30: both methods active; compare reported conversions side by side.
• Day 30: confirm new method matches or exceeds old method's volume.
• Day 31: turn off the legacy upload pipeline; keep new method as sole source.

This avoids the worst migration outcome — flipping the switch on the new method, hitting an unforeseen integration bug, and watching Smart Bidding optimization degrade for two weeks before you notice.

Common Migration Pitfalls We See in TagSpecialist Audits

Of the migration audits TagSpecialist has run on the legacy GCLID flow this year, the same handful of mistakes recur:

1. CRM lead-creation timestamp vs. close timestamp confusion. Teams send conversion_date_time as the deal-close time, then their 63-day window starts ticking from a date 90 days after the actual ad click. Conversions silently get rejected. Always use the lead-creation time.
2. Inconsistent email normalization between the website tag and the CRM upload. If the website tag lowercases and trims, but the CRM upload leaves capitalized email addresses, hashes don't match across the two paths and Google sees them as different users. Standardize the normalization function across all entry points.
3. Skipping phone hashing. Phone is the second-most-impactful match identifier after email, especially in industries with weak email match rates (B2B, healthcare, financial services). Most teams skip it because their CRM doesn't have clean phone data — but even capturing it on the form-submit side and hashing the available subset moves match rate by 3-7 points.
4. Weekly batch cadence after the 63-day cliff. A 7-day batch on a 63-day window leaves a 56-day buffer — which is fine until a sales cycle stretches 60+ days, at which point conversions fall off the cliff and never appear in Smart Bidding signal. Daily is the only safe cadence under the new flow.
5. Forgetting to enable Enhanced Conversions on the conversion action itself. Sending hashed user data via the Data Manager API does nothing if the conversion action in Google Ads is not configured to accept it. Check Conversions → [action] → Settings → Enhanced conversions: ON.

How TagSpecialist Can Help

If your sales-funnel infrastructure was built before mid-2024, there is a strong chance your Google Ads conversion signal is about to lose meaningful fidelity. TagSpecialist has run this exact migration for B2B SaaS, agency, fintech, and education clients — and the playbook is identical regardless of your CRM.

A typical TagSpecialist Enhanced Conversions for Leads migration includes:

• CRM audit and field mapping — confirming email, phone, name, address, and GCLID are reliably captured at lead-creation, not deal-closure.
• Server-side hashing pipeline — Cloud Run / Cloud Function service that normalizes and hashes PII, with audit logging to satisfy GDPR data-handling requirements.
• Data Manager API integration — daily sync from your CRM to Google Ads with backfill, retry, and partial-failure handling.
• Match rate validation and tuning — ensuring coverage hits 95%+ and match rate hits the upper end of your industry's typical range.
• 30-day parallel-run validation — running legacy and new methods concurrently to confirm no signal loss before cutover.

The migration takes 2-3 weeks for most clients — well within the window before June 2026, but not if you wait until late May to start.

If you are running Google Ads Lead Gen at $10K+/month and have not yet planned your Enhanced Conversions for Leads migration, book a 15-minute audit call and we'll walk through your current setup and what the migration looks like for your stack — no sales pressure, just engineering scoping. For ongoing tracking infrastructure, see our Google Tag Manager Specialist services and Server-Side Tagging Specialist services.

The June 2026 unification is, in the end, not a catastrophe — it is a forcing function. The advertisers who migrate cleanly will see their Smart Bidding signal sharpen and CPAs improve. The advertisers who let it slip will quietly underperform their better-prepared competitors for the rest of the year. The work is not exotic, and the deadline is real. Now is when you do it.