Data Measured

artifact #A-008 · sql · current

AI Max migration date fields (GAQL)

The query that dates every Search campaign's flip to AI Max, so you analyse each campaign before and after its own timestamp instead of comparing September to August.

verified_on
2026-09-07
checked against
Google Ads API — Campaign resourceData Measured — Your September search data has a seam (7 Sep 2026)
next re-check
2026-12-01
status
current
time
15 minutes
skill
you can run a GAQL query

What's inside

  • campaign.aca_migration_date_time and campaign.broad_match_migration_date_time (output-only, customer time zone)
  • Filter to Search campaigns, ordered by flip date
  • The analysis rule: per campaign, before/after its own timestamp

Install

  1. Run in the Google Ads API (v25.1+) or Google Ads Scripts' AdsApp.search.
  2. Join the timestamps to your daily campaign report; split each campaign's series at its own date.
  3. Do not compare the account month over month across September 2026.

The file · ai-max-migration-dates.gaql

Download
-- Google Ads Query Language (Google Ads API v25.1+): when did each Search campaign flip to AI Max?
SELECT
  campaign.id,
  campaign.name,
  campaign.status,
  campaign.aca_migration_date_time,
  campaign.broad_match_migration_date_time
FROM campaign
WHERE campaign.advertising_channel_type = 'SEARCH'
  AND campaign.status != 'REMOVED'
ORDER BY campaign.broad_match_migration_date_time DESC
-- Both timestamps are output-only, in the customer's time zone, 'yyyy-MM-dd HH:mm:ss'. Analyse each campaign before/after its own timestamp; do not compare the account across September 2026.

Breaks on

The logged changes that can invalidate this artifact. A new one triggers a re-check.

Stamped 7 Sept 2026 · re-checked quarterly or on change · corrections to team@datameasured.com · ← the library