Google has announced that it will begin phasing out offline conversion imports through the Google Ads API for certain developers starting June 15. The change marks a significant shift in how advertisers and marketing technology providers will need to handle conversion data that originates outside of the traditional web browsing experience.
What the June 15 Deadline Means for Developers and Advertisers
According to notifications sent to developers, offline conversion imports using the UploadClickConversions request will cease to function after June 15 for any account that has not utilized this specific functionality within the preceding 180 days. This directive specifically targets offline conversion imports and enhanced conversions for leads, leaving all other standard Google Ads API operations unaffected. The move is not a blanket shutdown but a targeted deprecation aimed at accounts that have been inactive in this particular area, although it clearly signals a broader strategic transition.
Understanding the Scope of the Change: What Is Being Deprecated
The core functionality being phased out is the UploadClickConversions method within the Google Ads API. This method has been a primary mechanism for advertisers to send conversion data from offline events—such as phone calls, in-store purchases, or form submissions that are processed after a digital interaction—back into Google Ads. Enhanced conversions for leads, a feature that uses hashed first-party data to improve the measurement of lead-based conversions, is also included in this deprecation. It is crucial for developers to understand that this is not a change to the entire Google Ads API; all other API operations for campaign management, reporting, and online conversion tracking will continue to function normally. The restriction is narrowly applied to the specific pipeline for offline data ingestion via the legacy method.
The Mandatory Migration Path: Transitioning to the Data Manager API
Google has designated the Data Manager API as the replacement for these deprecated workflows. The company describes the Data Manager API as a unified ingestion system designed to centralize how advertiser data is sent into Google Ads. This newer API already supports Customer Match uploads and, with this transition, will become the primary conduit for conversion imports as well. Google has indicated that the Data Manager API offers a better developer experience, including improved error handling, more granular control over data ingestion, and additional functionality that was not available in the old UploadClickConversions workflow. For developers, this migration is not optional for continued operation of these specific features. It will require a deliberate process of updating existing integrations, rebuilding import processes, and thoroughly testing new ingestion workflows to ensure data flows correctly before the June deadline.
Why This Matters: The Critical Role of Offline Conversion Data
Offline conversion imports are a cornerstone of modern performance marketing, particularly for businesses with long sales cycles or complex customer journeys. They allow advertisers to connect digital ad exposure to outcomes that occur in the physical world or through non-digital channels, such as a phone call to a dealership, a scheduled appointment, an in-store purchase, or a closed deal from a sales team. When this data stops flowing into Google Ads, the consequences are immediate and significant. Reporting becomes incomplete, making it impossible to accurately assess the full return on ad spend. Attribution models lose crucial touchpoints, skewing the understanding of which campaigns are truly driving results. Perhaps most critically, automated bidding strategies, which rely on high-quality conversion data to optimize for goals like target CPA or ROAS, will degrade in performance. Without a steady stream of offline conversion signals, these algorithms operate with a partial view of reality, leading to suboptimal bidding decisions and potentially wasted budget.
A Strategic Shift: Google’s Broader Push Toward Centralized, AI-Driven Infrastructure
This deprecation is not an isolated technical update but a clear signal of Google’s broader strategic direction. The move is part of a concerted effort to consolidate the numerous advertiser data tools into fewer, more centralized systems. The Data Manager API is the embodiment of this strategy, acting as a single, unified point of ingestion for multiple types of advertiser data, from customer lists for targeting to conversion signals for measurement. This consolidation is closely tied to Google’s increasing reliance on automation and AI-driven campaign products. By funneling all offline conversion data through a single, modern API, Google gains more consistent, higher-quality inputs for its machine learning models. This infrastructure is also designed to be more privacy-centric, aligning with the industry-wide shift toward first-party data. The transition away from a direct, code-based upload method to a more managed, centralized system reflects an effort to build a robust data pipeline that can handle evolving privacy regulations and signal loss, such as the deprecation of third-party cookies.
Navigating the Migration: Practical Steps for Developers and Martech Providers
For organizations affected by this change, the migration requires a structured approach. The first step is an audit of existing integrations to identify all workflows that rely on UploadClickConversions. This includes not only direct integrations but also any third-party platforms or internal tools that feed offline conversion data into Google Ads. Once identified, the development team must become familiar with the Data Manager API documentation, paying close attention to the new authentication, data schema, and error handling requirements. The rebuild process will likely involve rewriting data ingestion logic, adjusting how data is formatted and batched, and implementing new retry and validation mechanisms. After the new integration is built, a rigorous testing phase is essential. This should include testing with sample data, running parallel uploads alongside the old system, and closely monitoring the Google Ads interface to ensure that conversions are being recorded correctly and that automated bidding performance remains stable. Google has provided documentation and migration guides to assist with this process, and it is recommended that developers start the migration well in advance of the June 15 deadline to avoid any last-minute disruptions.
Broader Industry Implications: The Convergence of Automation, Privacy, and Data Management
This update is a tangible example of the converging trends reshaping the digital advertising landscape. The push toward automation means that platforms like Google are demanding cleaner, more consistent, and more structured data feeds. The growing emphasis on privacy means that data handling must be more secure and transparent, often requiring hashing or other anonymization techniques. This deprecation effectively forces advertisers and technology vendors to modernize their data infrastructure. It raises the technical bar for participation, favoring those with dedicated engineering resources and penalizing those who rely on outdated, ad-hoc integration methods. For the martech ecosystem, this change may accelerate the consolidation of service providers, as smaller platforms that cannot quickly adapt to new API requirements may find themselves at a competitive disadvantage. For advertisers, it underscores the need for a sophisticated data strategy, one that treats offline conversion data with the same rigor as online data and that builds flexibility into the tech stack to accommodate platform migrations.
What Remains Unchanged and What to Expect Next
It is important to note that the Google Ads API is not being phased out. All other operations, including campaign management, keyword planning, ad group creation, and online conversion tracking via the standard web-based tag, will remain fully functional. The change is exclusively focused on the route through which offline conversion data is uploaded. Looking ahead, developers should expect continued investment from Google in the Data Manager API. It is likely to become the central hub for more data-related features over time, potentially expanding to include other types of offline measurements or data integration points. The immediate takeaway is clear: any business that relies on importing offline conversions into Google Ads must prioritize migrating these workflows to the Data Manager API before June 15. Failure to do so will result in a disruption of critical conversion data, impacting campaign performance, reporting accuracy, and the effectiveness of automated bidding strategies. This deprecation, first spotted by PPC specialist Arpan Banerjee in a LinkedIn post, serves as a definitive timeline for an important technological transition in the paid media landscape.
