New integrations
A new custom upload can’t use the Google Ads API route, so the Data Manager API is where it starts.
Your offline conversion upload is on borrowed time
Since 15 June 2026, Google has blocked offline conversion and enhanced conversions for leads uploads through the Google Ads API for new and dormant integrations, and we could find no published end date for those still on legacy access. We move custom uploads to the Data Manager API, which Google calls “the new standard for data integration with Google’s ad products”.
From £2,500 ex VATDo I need to migrate to the Data Manager API?
Dormant integrations
Integrations that sent no uploads in the first half of 2026 weren’t allowlisted for legacy access, so those uploads are blocked too.
Tokens still in use
Tokens active in that window kept legacy access for now. We could find no published end date, which isn’t the same as there being no end.
OAuth with its own scope
The Data Manager API uses OAuth with its own scope instead of the Ads API developer-token setup, so authentication needs rebuilding along with the upload.
Row-level diagnostics
On 4 November 2026 Google announced that the Data Manager API now supports Google Ads call conversions and row-level diagnostics, which makes failed rows far easier to find.
Connectors and third parties
Google also supports routes through Data Manager connectors and third parties such as Zapier and HubSpot. This service is for custom uploads, so check with your provider if you’re on one of those.
What a migration actually involves
What happens to a failed upload?
A failed upload can go unnoticed unless the system handles errors properly, because nothing on screen changes and the conversions simply stop arriving. We log every batch, read back the results and make sure rejected rows reach a person.
- Every batch logged
- Row-level results read back
- Rejected rows reported to a person
Moving the code, keeping the data
We map what your current upload sends into the Data Manager API’s format, replace the developer-token setup with OAuth, then check the same conversions reach the same actions. Your CRM, ERP or database stays as it is.
- Field mapping from your current upload
- OAuth in place of the old setup
- Same conversion actions on the other side
Classic import or enhanced conversions for leads?
Google describes its classic offline conversion import as a legacy feature and recommends upgrading to enhanced conversions for leads. If you’re migrating anyway, it’s a sensible moment to decide which you want and whether call conversions belong in the same pipeline.
- Classic import described as legacy
- Enhanced conversions for leads recommended
- Call conversions now supported
Migration scope
We start by reviewing what your integration sends today and whether its token has legacy access. The quote that follows is fixed, starting from £2,500 ex VAT according to the systems in play.
What’s included
- Review of your current upload and its token status
- Rebuild on the Data Manager API with OAuth
- Error handling, logging and a test against real conversions
What we’ll need from you
- Access to the code or system doing the uploading
- Admin rights on the Google Ads account
- Access to your Google Cloud project, if you have one
Often paired with
Lead quality feedback
Send qualified leads and closed deals from HubSpot, Pipedrive, Salesforce or a custom CRM into Google Ads, so bidding optimises on sales, not form fills.
Tracking Monitoring
Monthly tracking monitoring for Google Ads: automated checks that warn when conversions drop, a tag breaks or your website and CRM stop matching.