A professional business woman leads a meeting with a diverse team, using a digital display.

Google Ads Offline Imports: What Lead-Gen Teams Must Check Now

BySplinternet Marketing

Google’s June 15, 2026 migration changed the upload path for offline conversion imports and enhanced conversions for leads. Google says these uploads moved to the Data Manager API and are blocked in the Google Ads API. For lead-generation advertisers, agencies, CRM integrators, and developers, the immediate task is not simply replacing an endpoint. It is verifying that the data flow still represents the right lead stages, identifiers, consent signals, and customer outcomes.

Google recommends the Data Manager API for current and future offline conversion and enhanced-conversions-for-leads uploads. The migration can affect integrations behind Search, Performance Max, broad-match campaigns, and other campaigns that use imported conversion actions for optimization. It does not, by itself, improve lead quality or fix an unclear CRM lifecycle.

Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.

What changed and where integrations can break

The technical ingestion method uses the events:ingest endpoint and the Data Manager OAuth scope. Google’s request structure supports event timestamps, ad identifiers, hashed user data, consent information, transaction identifiers, and customer-type data.

Audit every system that can send conversion data to Google Ads:

  • CRM, marketing automation, call tracking, middleware, and agency-managed integrations.
  • API endpoints, OAuth scopes, developer credentials, token refresh processes, and legacy access assumptions.
  • CRM field mapping for lead, qualified lead, booked appointment, sale, or other lifecycle stages.
  • GCLID, GBRAID, WBRAID, email, phone, consent, timestamp, currency, value, and unique transaction or event identifiers.
  • Queue handling, retries, rate limits, duplicate prevention, error logging, upload diagnostics, and alerting.
  • Conversion-action settings, including which actions are primary for bidding and which remain secondary for observation.

Use validation-only requests before enabling production traffic. A request that passes transport or schema validation is not proof that Google matched the event, deduplicated it, attributed it to an ad interaction, or made it available for bidding. Reconcile the upload results with Google Ads diagnostics and the original CRM records.

Google recommends continuing to send existing GCLIDs whenever possible, even when enhanced conversions for leads is enabled. Hashed first-party data such as email addresses and phone numbers can provide additional matching signals, but it does not replace accurate CRM records, a clear consent process, or consistent normalization and hashing.

What to do next

  1. Inventory every upload path. Document which systems send events, which conversion actions they target, and whether any workflow still depends on the Google Ads API.
  2. Run representative validation tests. Test a new lead, qualified lead, booked appointment, and closed sale. Confirm timestamps, identifiers, consent fields, event names, values, and transaction IDs.
  3. Preserve available identifiers. Keep GCLIDs and add hashed first-party data, BRAIDs, timestamps, consent signals, and unique event IDs when available.
  4. Reconcile the systems. Compare CRM totals, accepted events, upload diagnostics, duplicate rates, event delays, and Google Ads conversion reporting. Do not compare only by upload date because Google Ads reporting is based on the conversion event and attribution process.
  5. Delay bidding changes until the data is stable. Google recommends waiting through the longer of three conversion cycles or four weeks before switching enhanced conversions for leads to primary and the legacy offline conversion action to secondary.

New-customer measurement needs a separate check. Google documents customer_type for API-based uploads, but the new customer acquisition goal is intended for purchase conversions. A lead-generation team should not assume that labeling a lead as “new” automatically makes it equivalent to a purchase-based new-customer signal. Verify the conversion type, customer history, lookback logic, and treatment of uncertain records before using the data in lifecycle goals.

The practical goal is a dependable path from ad interaction to CRM outcome. Migrate the upload method, test the data model, monitor diagnostics, and confirm several conversion cycles before changing campaign targets or trusting new-customer signals.

Sources

Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.

This article is for informational purposes only and reflects general marketing, technology, website, and small-business guidance. Platform features, policies, search behavior, pricing, and security conditions can change. Verify current requirements with the relevant platform, provider, or professional advisor before acting. Nothing in this article should be treated as legal, tax, financial, cybersecurity, or other professional advice.

Editorial note: Splinternet Marketing articles are researched from cited platform, documentation, regulatory, and industry sources. AI may assist with drafting and review; final content is checked for source support, practical usefulness, and platform/date accuracy before publication.

Related Posts

Splinternet Marketing