June 15, 2026 — 14 days from today — Google Ads blocks all new legacy offline conversion import (OCI) adopters from the API.
After March 2027, the legacy path ends for everyone.
If your pipeline is GCLID-only CSV uploads or legacy UploadClickConversions API calls, it is on a confirmed deprecation timeline.
What's Dying vs. What Replaces It
Retiring:
- Manual and automated CSV/SFTP uploads via the legacy OCI UI
UploadClickConversionsandOfflineUserDataJobServiceAPI calls- The "Uploads" interface under Tools > Conversions in the UI
The replacement: Google Ads Data Manager — a centralized hub for connecting CRMs (Salesforce, HubSpot, Dynamics), file sources (Google Sheets, SFTP, GCS), and data warehouses (BigQuery, Snowflake). Enhanced Conversions for Leads (hashed email or phone) is the required matching standard for all new integrations.
The Hard Timeline
| Date | Event |
|---|---|
| June 1, 2026 | 37-month granular data cap enforced; reporting data before May 2023 gone |
| June 10, 2026 | Google Ads API v20 sunset — API version migration required separately |
| June 15, 2026 | New OCI adopters blocked — hard API enforcement begins |
| April 2026 | Google auto-migrates accounts to unified Enhanced Conversions setting |
| March 2027 | Legacy OCI path ends for all existing users |
Who's Affected
Key findings:
- CSV/SFTP upload users: Any manually-batched GCLID file import is on the retirement path.
- CRM-native integration users: Legacy Salesforce/HubSpot connectors built before the Data Manager era need re-plumbing through the new connector architecture.
- Custom API middleware: Engineering teams using
OfflineUserDataJobServicemust rebuild their ingestion logic against the Data Manager API. - Store sales and visit tracking: These data streams are moving entirely to the Data Manager API — there is no GCLID-only path forward.
The Migration — 5 Steps
1. Audit your current path. Does your pipeline use GCLID-only matching? If there are no hashed email or phone fields in your data feed, you are on the legacy OCI path.
2. Open Data Manager. Navigate to Tools > Data Manager in the Google Ads UI. This is the new front door for all first-party data ingestion.
3. Build your connection. File-based: SFTP, Google Sheets, or GCS. CRM-based: native connectors for Salesforce, HubSpot, or Dynamics. Custom: the Data Manager API for real-time or batch syncing.
4. Map to Enhanced Conversions for Leads schema. You must include hashed email or phone number fields. This is not optional — it is the matching standard. GCLID alone is insufficient for any new integration.
5. Set pipeline to append mode. Data Manager UI-based file uploads are capped at once-per-day syncs. API connections support real-time ingestion. Pick the right connection type for your conversion volume.
| Migration path | Effort | Timeline |
|---|---|---|
| Google Sheets to Data Manager UI | Low | 1–2 days |
| SFTP to Data Manager UI | Low | 2–3 days |
| Salesforce / HubSpot CRM connector | Medium | 3–5 days |
| Custom API middleware rebuild | High | 1–2 weeks |
Root cause: Google is consolidating first-party data ingestion behind a privacy-safe, hashed-signal architecture. GCLID-only matching fails in most privacy-regulated jurisdictions. This is infrastructure policy driven by regulatory pressure — not a product preference.
The deadline is real. Build the bridge before June 15 or lose the ability to onboard new offline conversion data.
Founder CEO/CTO
