Your CFO just asked why AI-generated ad copy is showing up in board reports without any audit trail. Your RevOps lead wants to know which Demand Gen channels are actually driving conversions. And your security team is flagging OAuth token management as a Q3 priority. Google's v24.2 release, shipped June 24, addresses all three concerns in a single minor update.
This is the sixth monthly release since Google shifted to a faster cadence in January 2026. For marketing leaders managing programmatic ad operations, the new fields translate directly into tighter governance, cleaner attribution, and fewer surprises in your next pipeline review.
Local Services Meets Performance Max
The most operationally significant addition is the integration of Local Services Ads into Performance Max campaigns. According to Google's release notes, v24.2 introduces AssetGroup.google_local_services_info and Campaign.PmaxCampaignSettings.local_services_enabled fields that let you identify and manage Local Services inventory programmatically.
For B2B companies with field sales or service components, this matters. You can now pull Local Services conversion data (calls, messages, bookings) into the same reporting infrastructure as your other PMax campaigns. The new ConversionOrigin.LOCAL_SERVICES_ADS enum means your attribution models can finally distinguish between a lead that came from a local services ad versus one that came from a standard search placement.
The practical implication: if you're running PMax for lead generation and have any local presence, you can now build a single dashboard that shows CAC by channel without manual data stitching. That's one less reconciliation step before your monthly pipeline review.
Maps Joins the Demand Gen Channel Mix
Google Maps is now a selectable channel for Demand Gen ad groups. The channel controls documentation shows that selected_channels.maps can be toggled independently, giving you granular control over where your visual ads appear.
This arrives alongside Google's broader consolidation of Display into Demand Gen. The migration tool launched in June 2026, and the company reports that advertisers adding Google Display Network to their Demand Gen campaigns see a 9.5% increase in ROI on average.
For marketing executives, the channel expansion creates both opportunity and complexity. You can now reach users in Browse, Directions, and Place Details modes on Maps, but you'll need to update your reporting queries to capture the new dimension. If your team is still running legacy Display campaigns, the migration deadline is coming: remaining campaigns will be automatically moved to Demand Gen by 2027.
Smart Campaign Creation Is Dead
The v24.2 release includes a new error code that signals the end of an era: SmartCampaignErrorEnum.CREATION_FAILED now returns when attempting to create new Smart Campaigns via the API. As Search Engine Land reported, this effectively sunsets Smart Campaign creation for programmatic workflows.
Existing Smart Campaigns continue to run, but the writing is on the wall. Google is consolidating around AI Max and Performance Max as the primary automated campaign types. If your agency or internal team has scripts that spin up Smart Campaigns for new clients or product launches, those scripts need to be rewritten before your next campaign cycle.
Experiment Types for Cross-Campaign Testing
Two new experiment types landed in v24.2: COMPARE_CAMPAIGNS and PMAX_TEXT_CUSTOMIZATION_FINAL_URL_EXPANSION. The first enables campaign mix experiments that compare multiple campaigns of the same or different types in a single test. The second lets you run controlled experiments on Performance Max text customization and final URL expansion settings.
This is the kind of infrastructure that makes incrementality testing practical at scale. Instead of running sequential A/B tests across campaign types, you can now design experiments that answer questions like: "Does adding a PMax campaign to our existing Search portfolio actually lift total conversions, or just cannibalize existing volume?"
For teams that have been struggling to prove incremental value to finance, these experiment types provide the holdout and control structures you need. The minimum detectable effect calculations still require careful design, but the API now supports the test architecture.
Landing Page Text Generation for Demand Gen Video
The AssetAutomationType.GENERATE_LANDING_PAGE_TEXT enum value is new in v24.2, and it's opted in by default for DemandGenVideoResponsiveAd instances. Google's AI will now generate text information from your landing page to display in the engagement panel for video ads.
This is where AI transparency becomes a governance question. The generated text appears automatically unless you explicitly opt out. For brands with strict messaging guidelines or regulated industries, this default behavior needs to be addressed in your campaign setup process. Your legal and compliance teams should know that AI-generated copy is now appearing in ad units by default.
The good news: the v23.1 release earlier this year introduced Campaign.text_guidelines with up to 25 term exclusions and 40 messaging restrictions. If you haven't implemented those controls yet, the landing page text generation feature makes it more urgent.
Version Sunset Timeline
According to Google's deprecation schedule, v24.2 will sunset in May 2027. The monthly release cadence means you'll see v25 in July, v25.1 in August, and v25.2 in September. Major versions now have a 12-month lifespan; minor versions get 10 months.
For teams that pinned API versions annually, this cadence requires a process change. CI/CD pipelines that don't update within four weeks will miss new metrics and fields that your stakeholders expect in dashboards. The practical recommendation: schedule quarterly version reviews at minimum, with a standing ticket to evaluate each monthly release for features that affect your reporting or governance requirements.
The Two-Week Pilot
If you're running Performance Max or Demand Gen campaigns, here's a concrete next step: audit your current API version and identify which v24.2 fields affect your reporting.
- Pull your current channel-level reporting for Demand Gen and confirm whether Maps inventory is appearing (it may be opted in by default)
- Check whether any campaigns are using the new Local Services PMax settings
- Review your text guidelines configuration to ensure AI-generated landing page text aligns with brand standards
- Verify that your experiment infrastructure can support the new COMPARE_CAMPAIGNS type
The v24.2 release is a minor version with no breaking changes, which means you can upgrade without code modifications. The risk is low; the visibility gain is immediate. Finance will appreciate the cleaner attribution. Security will appreciate the audit trail. And you'll have the data you need for your next board prep.
