Understanding the Shift in Google Ads Data Management
The digital advertising landscape is currently undergoing a massive structural shift. As privacy regulations tighten and the reliance on third-party cookies diminishes, Google is re-engineering how it handles advertiser data. The latest development in this evolution is the transition of offline conversion imports. Google has officially announced that it is moving offline conversion imports out of the Google Ads API and into the Data Manager API.
For developers, martech providers, and high-level advertisers, this represents more than just a simple technical update. It is a fundamental change in how lead data and offline sales are reported and processed within the Google ecosystem. Starting June 15th, Google will begin phasing out the ability to use the Google Ads API for these specific tasks, signaling a clear push toward a more centralized, automated data ingestion infrastructure.
The Technical Deadline: June 15 and Beyond
Google has set a clear timeline for this transition. Beginning June 15th, developers using the UploadClickConversions request within the Google Ads API will find that this functionality is being deprecated for specific accounts. Specifically, accounts that have not utilized this functionality within the last 180 days will be the first to lose access. This “use it or lose it” approach suggests that Google is targeting inactive or legacy integrations first to streamline the migration process.
The scope of this change includes both standard offline conversion imports and enhanced conversions for leads. While other Google Ads API operations—such as campaign management, keyword research, and reporting—will continue to function normally, the specific workflow for injecting offline lead data is moving to a new home. This means that any platform or custom-built internal tool that relies on syncing CRM data with Google Ads must be audited immediately.
What is the Data Manager API?
To understand why this move is happening, one must look at the Data Manager API. Google describes this as a unified ingestion system. In the past, advertisers had to use different APIs and manual upload methods for different types of data. Customer Match lists lived in one area, while offline conversion imports lived in another. The Data Manager API is designed to consolidate these workflows into a single, high-performance gateway.
The Data Manager API isn’t just a replacement; it’s an upgrade. Google claims it offers a superior developer experience and includes additional functionality that was simply not possible within the legacy Google Ads API framework. By moving conversion data into this centralized system, Google can more effectively apply its AI and machine learning models to the data, providing advertisers with faster processing times and more accurate attribution models.
Why Offline Conversion Tracking is Critical
Offline conversion tracking (OCT) is the backbone of measurement for businesses that don’t complete their sales cycle online. For industries like B2B SaaS, automotive, real estate, and professional services, a “conversion” isn’t a click or a form fill—it’s a signed contract or a physical purchase. Without OCT, these businesses are essentially flying blind.
When a user clicks an ad and fills out a lead form, the digital journey often ends there. The actual sale might happen weeks or months later via a phone call or an in-person meeting. By importing that offline sale data back into Google Ads, advertisers can tell the algorithm which specific keywords, ads, and audiences actually resulted in revenue, rather than just “cheap leads.”
If this data flow is interrupted because an integration wasn’t migrated to the Data Manager API, the consequences are immediate. Reporting will show a drop in ROI, attribution models will break, and most importantly, automated bidding strategies like Target CPA (tCPA) or Target ROAS (tROAS) will lose the signals they need to optimize effectively. In short, your ads will become less efficient and more expensive.
The Push Toward AI-Driven Infrastructure
This migration is a tactical move in Google’s broader strategy to move toward a “Privacy-First” and “AI-First” ecosystem. As the industry moves away from precise individual tracking, Google is relying more heavily on modeled conversions and first-party data. The Data Manager API is built to handle the complexities of modern data privacy, ensuring that data is ingested securely and used in a way that complies with evolving global standards.
By centralizing data ingestion, Google can better facilitate “Enhanced Conversions.” This feature uses hashed first-party data (like email addresses or phone numbers) to match conversions even when cookies are unavailable. Moving these features into a dedicated Data Manager API allows Google to iterate on these privacy-centric technologies without being slowed down by the legacy architecture of the general Ads API.
Impact on Martech Providers and Developers
For martech providers—such as CRMs, call tracking software, and marketing automation platforms—this change requires immediate engineering attention. Many of these platforms have built-in integrations that automatically send conversion data to Google Ads. If these providers do not update their backend logic to support the Data Manager API by the June 15th deadline, their users will see a sudden “dark period” in their conversion data.
Developers will need to rebuild import processes, update authentication protocols, and thoroughly test the new ingestion workflows. While the Data Manager API is designed to be more efficient, any migration of this scale involves a learning curve. Teams will need to familiarize themselves with the new endpoints and data schemas required by the updated system.
Steps for a Successful Migration
If your organization or your clients rely on offline conversion imports, you should follow a structured migration path to ensure zero data loss. Waiting until the June 15th deadline is not an option for businesses that rely on real-time data for bidding optimization.
1. Audit Current API Usage
The first step is to identify exactly which accounts and workflows are using the UploadClickConversions request. Use the Google Ads API usage reports to determine the volume and frequency of these requests. If you have accounts that haven’t sent data in over 180 days, be aware that they will be the first to lose access, but even active accounts should prepare for the eventual full transition.
2. Review Data Manager API Documentation
Google’s developer documentation provides the technical specifications for the Data Manager API. It is essential to review the requirements for “Enhanced Conversions for Leads” specifically, as this is a primary focus of the new API. Understand the hashing requirements for first-party data to ensure compliance with Google’s security protocols.
3. Develop and Test New Ingestion Workflows
Before switching over entirely, build a parallel testing environment. Use the Data Manager API to send a subset of data and verify that it is appearing correctly in the Google Ads UI. Compare the data from the new API against the legacy API to ensure there are no discrepancies in attribution or volume.
4. Monitor Automated Bidding Performance
Once the migration is live, keep a close eye on your Smart Bidding campaigns. Any change in data ingestion can cause a temporary “learning phase” for the algorithm. Monitoring performance for 14–21 days after the migration will help you identify if the bidding strategy is reacting correctly to the new data stream.
The Bigger Picture: Consolidation and Automation
We are seeing a trend where Google is simplifying its interface for advertisers while making the backend more robust for data scientists and developers. The introduction of the “Data Manager” tab in the Google Ads UI was the first step; moving the API is the logical second step. This consolidation allows for better integration with Google Cloud and BigQuery, making it easier for large enterprise advertisers to move massive datasets into the Google Ads engine with minimal latency.
In this new era, the advertisers who win will be those who have the cleanest, most reliable first-party data pipelines. By moving offline conversions to a specialized API, Google is signaling that data quality and data security are now the primary levers for campaign success. It is no longer just about who has the best ad copy, but who has the best data infrastructure feeding the AI.
Conclusion: Stay Ahead of the June 15th Deadline
The transition from the Google Ads API to the Data Manager API for offline conversion imports is a mandatory step for any forward-thinking digital marketer or developer. While the June 15th deadline primarily affects accounts with 180 days of inactivity, the writing is on the wall: the legacy method is being phased out for everyone.
By acting now, you can ensure that your conversion tracking remains uninterrupted, your attribution models stay accurate, and your automated bidding strategies continue to have the high-quality data they need to perform. This move toward a unified, AI-driven data ingestion system is a significant milestone in the history of Google Ads, and staying ahead of the curve is essential for maintaining a competitive edge in the modern advertising landscape.