.png)
Today in Google Ads news for June 13, 2026: Google's Consent Mode becomes the sole data gate for advertising data collection when the June 15 deadline hits this Sunday, affecting every advertiser running Google Ads with consent management. The same date brings an offline conversion import cutoff for new API adopters. Meanwhile, updated Terms of Service formalize Google's AI automation authority ahead of July 1, Performance Max asset experiments expand, API v20 is already dead, and YouTube channels are being auto-linked to Ads accounts. Here is everything you need to know.
Starting June 15, 2026, the ad_storage parameter in Consent Mode becomes the single control point for what advertising data flows into your Google Ads account. Google Analytics can no longer override Google Ads data collection settings, eliminating the previous dual-gate system where both Consent Mode and Google Signals settings determined data flow.
The practical impact: brands that previously had Google Signals turned off in Analytics as a secondary privacy control may now see more Ads-linked data than expected whenever users grant consent through their consent banner. There is no dashboard fix available after the switch takes effect.
As reported by Search Engine Land, teams must audit their consent banners and Consent Mode implementation before Sunday. If your consent management platform is not properly configured to set ad_storage to denied by default in applicable jurisdictions, you could be collecting data you did not intend to collect. This is a compliance issue, not just a measurement one.
The same June 15 date brings a second breaking change. The Google Ads API will no longer accept new adopters of offline conversion imports or enhanced conversions for leads. Developer tokens that have not sent relevant requests between January and June 2026 will receive errors.
Google is migrating these workflows to the Data Manager API. Existing users retain temporary legacy access while they transition, but the direction is clear: the Data Manager API is now the primary path for offline conversion data.
Agencies and martech platforms building new offline conversion workflows need to integrate the Data Manager API immediately. If you are an existing user who has been putting off migration, the window of legacy access is shrinking. We covered this change in more detail in yesterday's roundup.
Google updated its Google Ads Terms of Service effective July 1, 2026, explicitly authorizing Google to use advertiser-provided inputs across AI-powered and automated tools. The updated language covers formatting, selecting, or generating targets, ads, or destinations on the advertiser's behalf.
As reported by Search Engine Land, the changes apply only to Google Ads accounts, not Workspace or Cloud. No action is required from advertisers. However, the update cements Google's legal footing to expand automation across campaigns. Advertisers remain responsible for resulting campaign outputs.
The practical takeaway: Google is signaling that automated ad creation, targeting adjustments, and destination selection will become more aggressive. If you are not actively monitoring what Google's automation produces in your account, now is the time to start. For context on why manual oversight of automation matters, see our piece on why manual Google Ads management is failing accounts in 2026.
Google expanded Performance Max asset experiments on June 8, 2026, giving advertisers structured A/B creative testing inside a single PMax campaign for the first time. This replaces guesswork with actual comparative data.
The constraints are worth noting: only one experiment can run per campaign at a time, and asset groups are locked once a test begins. API and Manager Account (MCC) support for multi-account experiment management is planned, which will be a significant unlock for agencies managing campaigns at scale.
As reported by Digital Applied, this is a meaningful step toward transparency in PMax. For deeper context on how the rollout started, see our June 11 roundup.
Google Ads API v20 was retired on June 10, 2026. All requests to v20 now fail. If your automated workflows for reporting, bidding, or campaign management have not been migrated, they are already broken.
As reported by Search Engine Land, migrating to v24.x is the current recommended path. Teams that delayed migration may be experiencing data gaps and operational disruption right now. Any scripts, third-party integrations, or internal tools still referencing v20 endpoints need immediate attention.
YouTube auto-linking is live. Starting June 10, Google Ads accounts not already linked to a YouTube channel are being automatically connected. Advertisers who previously opted out of YouTube linking should review account settings to confirm the auto-link aligns with their data strategy.
37-month granular data retention is now enforced. As of June 2026, granular hourly, daily, and weekly reporting data older than 37 months is at risk of permanent loss. Monthly and yearly aggregates remain available for 11 years, but if you rely on granular historical data for budget modeling or audits, export to BigQuery now.
Richer home listing ads in Search. Google is rolling out expanded property listing ads with more detail for real estate advertisers. If you run ads in the property space, review eligibility and creative requirements. Our real estate lead quality case study covers how structuring around buyer intent makes the difference in this vertical.
July 1 ToS deadline approaching. The Terms of Service change discussed above takes effect in 18 days. While no action is required, advertisers should understand the expanded scope of Google's automation authority before it kicks in.
Weeks like this are exactly why managing Google Ads in-house or through a traditional agency creates risk. Consent Mode migration, API version sunsetting, offline conversion import cutoffs, Terms of Service changes: each one requires awareness, technical execution, and speed. A single missed deadline can break data flows or leave you out of compliance.
groas handles this by design. The proprietary engine, trained on over $500 billion in profitable ad spend, incorporates platform changes as they roll out. In DFY, a dedicated strategist manages every migration and compliance shift end to end, so you never scramble. In DWY, the strategist flags what matters and works alongside your team to implement. In DIY, agencies get engine updates automatically.
Month-to-month, no lock-ins, $0 onboarding. Whether you want full management (apply for DFY), strategic support alongside your team (get started with DWY), or the engine powering your agency's execution (start your 7-day free trial for DIY), groas stays current so your campaigns do not fall behind.
This Sunday's June 15 deadline is the story of the week. Consent Mode becomes the sole data gate, and offline conversion imports get locked out for new API adopters. If you have not audited your consent setup and API integrations yet, today and tomorrow are your last working days to do it. The Terms of Service update on July 1 adds another layer of urgency to understanding how Google's automation authority is expanding. We will be back tomorrow with the latest. See you then.
Google Ads Consent Mode is the framework that controls how advertising data is collected based on user consent signals. Starting June 15, 2026, the ad_storage parameter becomes the sole gate for Google Ads data collection, replacing the previous dual-gate system that also relied on Google Signals settings in Analytics. This matters because brands that previously had Google Signals turned off may now see more advertising data flowing into their Ads accounts whenever users grant consent. There is no dashboard toggle to reverse this after the switch takes effect. Advertisers must audit their consent banner implementations and Consent Mode configurations before the deadline.
If you are a new adopter trying to set up offline conversion imports or enhanced conversions for leads through the Google Ads API for the first time, yes. Starting June 15, developer tokens that have not sent relevant requests between January and June 2026 will receive errors. Google is migrating these workflows to the Data Manager API. Existing users retain temporary legacy access while they transition. Agencies and martech platforms building fresh offline conversion pipelines should begin integrating the Data Manager API immediately to avoid disruption.
Google updated the Google Ads Terms of Service effective July 1, 2026, to explicitly authorize Google to use advertiser-provided inputs across AI-powered and automated tools. This includes formatting, selecting, or generating targets, ads, or destinations on the advertiser's behalf. No action is required from advertisers, but the update formalizes Google's legal authority to expand automation. Advertisers remain responsible for the outputs of these automated decisions, which makes monitoring campaign performance and creative outputs more important than ever. groas accounts benefit here because a senior strategist monitors every automated output continuously.
Performance Max asset experiments, expanded on June 8, 2026, allow advertisers to run structured A/B creative tests within a single PMax campaign. You can compare different asset variations with actual performance data instead of relying on PMax's opaque reporting. Key constraints include a limit of one experiment per campaign at a time and locked asset groups once a test begins. API and MCC support for managing experiments across multiple accounts is planned. This feature is a meaningful step toward transparency in Performance Max optimization.
Google Ads API v20 was officially retired on June 10, 2026. All requests to v20 now fail. If your automated workflows for reporting, bidding, or campaign management have not been migrated, they are already broken. You may be experiencing data gaps and operational disruption right now. The recommended migration path is to update to v24.x. Any scripts, third-party integrations, or internal tools still referencing v20 endpoints need immediate attention.
groas adapts to platform changes like Consent Mode updates, API migrations, and Terms of Service shifts before they impact your campaigns. The proprietary engine, trained on over $500 billion in profitable ad spend, incorporates new platform requirements as they roll out. In DFY, a dedicated strategist handles every migration and compliance adjustment end to end. In DWY, the strategist flags required changes and works alongside your team. In DIY, agencies get engine updates automatically. Month-to-month contracts with no lock-ins mean you always have access to current-state execution without managing migrations yourself.
