Event Brief

What changed on June 15, 2026

Google moved offline conversion imports out of the Google Ads API. If your CRM integration or upload script stopped working, this page explains what happened and where to go.

The change

Blocked: Offline conversion imports (UploadClickConversions) and enhanced conversions for leads through the Google Ads API.
Replacement: The Data Manager API — POST https://datamanager.googleapis.com/v1/events:ingest — with a new JSON request shape, RFC 3339 timestamps, and no developer token requirement.
Grace path: Developer tokens that sent offline conversion requests between January and June 2026 could be allowlisted for temporary legacy access; new integrations cannot.

Who is affected

Workflow	Affected?	What to do
CRM / backend calls the Google Ads API to upload conversions	Yes — broken	Migrate to the Data Manager API. See the migration guide.
Zapier / connector tools built on the Google Ads API path	Yes (until the vendor migrates)	Check your vendor's status; meanwhile convert exports with the converter and upload manually.
Manual CSV upload in the Google Ads UI	No — but the entry point changed	The old file import is marked "legacy"; imports now run through Data Manager in Google Ads.
Enhanced conversions for leads via the Google Ads API	Yes — broken	Same migration, plus SHA-256 hashing requirements for user data.

What's actually different in the new format

Timestamps: legacy Google Ads format → RFC 3339 (cheatsheet)
Conversion action: per-row name → request-level numeric ID
Click IDs: top-level fields → nested ad_identifiers object
Money: plain currency values (micros are gone)
Processing: synchronous per-row results → asynchronous with a request_id
Full details: field mapping table

Fastest path to a working upload

Drop your existing conversion CSV into the converter. It validates every row and outputs both a Data Manager API JSON payload and a clean import CSV — entirely in your browser, so conversion data never leaves your machine.