Skip to main content
This page compares the Google Ads capabilities represented in the Interchange adapter with what Interchange currently makes available to buyers. It answers a practical question: what can I do through Interchange today, and what would still require another path?
Last reviewed 2026-08-28. This is Interchange’s description of its own adapter, based on the implementation and the linked provider documentation. Google Ads has not reviewed or endorsed this page. Availability can still vary by account permissions, market, and provider access.

​
At a glance

​
How to read availability

  • 🟢 Available — Offered through Interchange now, subject to your ad account’s permissions and eligibility with the provider.
  • 🟡 Partial — Some of the workflow is available; the Comments column explains the boundary.
  • 🔵 Testing — Interchange is validating the workflow before offering it broadly.
  • ⚪ Planned — Not offered through Interchange yet. The provider may still support it directly; Comments explains why and links a roadmap reference.

​
Roadmap

The adapter roadmap is tracked in AI-1951 (a plain-text reference — Interchange’s internal issue tracker is not public). This roadmap tracks Google Ads product completeness, staging readiness, and live readiness. Every row that is not currently available shows that reference or a more specific one in its References column, so customers and partners can quote a stable identifier when asking about a capability.

​
Connection, accounts, and identity

Google Ads connects to Interchange through an OAuth grant. Connecting a Manager account (MCC) account gives Interchange access to each Customer account (10-digit ID) it can reach — you then map each one to your advertisers. The mapped account decides which Google Ads tenant a buy runs on: a media buy for an unmapped advertiser fails closed with account_mapping_required rather than silently using another account. Connection, account-discovery, and revocation behavior is the same across ad platforms — see Platform accounts and advertiser mapping for the full model and the Google Ads section of the connecting guide for Google Ads-specific permissions.

​
Campaign products

​
Creative formats

These rows describe Interchange availability, not a claim that the ad platform itself prohibits an unavailable format.

​
What the adapter can do

​
Placement choices

Interchange does not expose a separate Google Ads placement selector.

​
Targeting

​
Reporting

Interchange reports Google Ads delivery day by day (there is no hourly delivery breakdown), aggregated nightly from adapter-reported delivery, in the advertiser’s home currency using the booked or historical exchange rate — any cross-currency rollup is always labeled an estimate and is never used for billing. See Reporting overview for the full model. Interchange does not currently publish an attribution-finality window for Google Ads; the table below lists every metric the adapter surfaces today.

​
Webhooks and async lifecycle

Google Ads does not push status, delivery, or reporting events into Interchange — every campaign product declares supports_webhooks: false.
  • Status. Interchange does not currently poll Google Ads in the background for creative or media-buy status changes; status reflects what the adapter returned on your last call.
  • Delivery. Interchange has not yet made on-demand delivery fetching generally available for Google Ads — see Get Media Buy Delivery in “What the adapter can do” above. The /reporting/metrics endpoints never call the adapter either way — they read from a separately-populated store (see Reporting below), so a reporting request does not itself refresh provider delivery.
This is separate from Interchange’s own buyer webhook subscriptions — an unrelated account-level event feed (currently discovery.revision only), documented in Buyer webhooks.

​
Market and account availability

Interchange does not promise that every feature is enabled for every account or market. Availability is checked against your selected ad account rather than a global market list on this page.

​
Important limitations

  • Interchange implementation/testing. Interchange reviewed 33 Google Ads creation flows. Search Traffic and a bounded Search Conversions workflow are implemented in the adapter; the remaining reviewed flows are blocked or unavailable.
  • Interchange implementation/testing. Search Traffic and Search Conversions are still being tested before general availability. Search Conversions currently supports only website or phone-call actions in complete enabled-primary category/origin groups; other sources and arbitrary action subsets are not offered.
  • Interchange implementation/testing. Product discovery and campaign budget writes use the selected advertiser customer’s ISO 4217 currency. Foreign, manager, or invalid-currency customer snapshots; stale products priced in another currency; non-representable budget amounts; and inline or catalog-resolved offering allocations that do not reconcile exactly to their package budget fail before a Google write. Bid values use account-currency major units and may carry up to six decimal places because Google stores them as integer micros. On non-USD accounts, live forecasts keep the selected account currency while USD-authored advisory floors become zero instead of assuming an exchange rate.
  • both Interchange’s implementation and the ad platform’s API or account eligibility. Search Conversions requires one event goal naming exact enabled primary website or phone-call conversion actions, explicit country or region targeting, and access to Google’s effective conversion customer. Campaign creation stays paused while Interchange reads back the exact campaign goal and effective action set.
  • Interchange implementation/testing. Creative assignment and publication are separate: campaign creation records creative IDs and applies canonical keyword targeting, while a later creative-sync call publishes the responsive search ad. Campaign creation does not return a Google-native creative preview.
  • both Interchange’s implementation and the ad platform’s API or account eligibility. A separately synchronized Performance Max creative can return Google’s expiring external UI preview only when one saved asset-group assignment and exact customer, campaign, asset-group, response, URL, and expiry readback agree. Google provides no placement selector or dimensions for this preview; ambiguous, transient, or fallback requests fail closed.
  • the ad platform’s API or your account’s eligibility. Google Ads account permissions, conversion resources, audiences, and market eligibility can further narrow availability.

​
Technical mapping

Engineering-level detail — raw provider objectives, billing enums, optimization codes, and object-field mappings. Not required reading to understand what Interchange can do with Google Ads; see the tables above for that.

​
Provider documentation