Google Ads Adds a Way to Tell When an "Exact Match" Click Was Really AI Max
In short: Google Ads has a new ValueTrack parameter, {search_term_matchtype}, that records in a click's URL whether the search term matched through AI Max broad-match expansion ("a") or a standard exact, phrase or broad match ("e", "p", "b"). The existing {matchtype} parameter only reports the keyword's own match type, so an AI Max expansion fired on an exact keyword still shows as "e" there — it never flagged that AI Max was actually involved. This new parameter is the only way to see that from the URL itself, which matters because more campaigns are being pushed onto AI Max through 2026 and 2027.
- A new ValueTrack parameter, {search_term_matchtype}, returns "e", "p" or "b" for standard exact/phrase/broad matches, and "a" for AI Max broad expansions and keywordless matches.
- Your existing {matchtype} parameter still just reports the keyword's own match type — it does not change when AI Max expands a search, so a click can show as "exact" there while actually being an AI Max expansion.
- To isolate AI Max traffic: filter for clicks where {search_term_matchtype} = "a". To isolate standard keyword traffic: filter for clicks where it is not "a".
- Add it alongside {matchtype}, {targetid} and {keyword} in your tracking template so analytics, CRM and call-tracking systems outside Google Ads can see it too — not just the Google Ads UI.
- This matters more every quarter: AI Max upgrades for campaigns with automatically created assets and campaign-level broad match started 1 September 2026, and Dynamic Search Ads campaigns move to AI Max automatically from February 2027 (no new DSA campaigns can be created after January 2027).
- The parameter is reporting-only. It does not change how AI Max matches queries, bids, or costs — it just tells you, after the fact, how much of your "exact match" traffic wasn't really exact match.
What's actually new
Google Ads has quietly added a new ValueTrack parameter: {search_term_matchtype}. It records, in the destination URL of every click, how the search term that triggered the ad actually matched — not how the keyword you bid on is set up.
It returns one of four values:
- e — exact match
- p — phrase match
- b — broad match
- a — the search came through AI Max broad-match expansion, or a keywordless match
Here's the part that makes this worth adding: the parameter you already have, {matchtype}, only reports the keyword's match type. If AI Max expands an exact-match keyword to cover a related search, {matchtype} still shows "e" — it has no idea AI Max was involved. {search_term_matchtype} is the only field that tells you that.
What this affects
This applies to AI Max for Search campaigns. It is not listed in Performance Max's compatibility table for either parameter. The timing matters beyond this one feature: campaigns using automatically created assets and campaign-level broad match began upgrading to AI Max from 1 September 2026, Dynamic Search Ads campaigns move to AI Max automatically from February 2027, and new DSA campaigns can no longer be created after January 2027. In other words, more of your "exact match" traffic is going to quietly include AI Max expansions over the next year, whether you're watching for it or not.
How to add it
Add it to your tracking template alongside the parameters you're probably already using:
{lpurl}?keyword={keyword}&matchtype={matchtype}&search_term_matchtype={search_term_matchtype}
Then, to tell the two kinds of "exact match" traffic apart:
- Isolate AI Max expansions: filter for clicks where
{matchtype}is e, p or b and{search_term_matchtype}is "a". - Isolate standard keyword traffic: filter for clicks where
{matchtype}is e, p or b and{search_term_matchtype}is not "a". - Check the expansion source: when
{matchtype}= "a", look at{targetid}. The IDkwl-3500001marks Google's own default automated expansion; a URL-rule-sourced expansion carries a differentkwl-ID.
Because this is a URL parameter rather than something locked inside the Google Ads UI, it flows into whatever you're already using to track clicks — GA4, your CRM, call tracking — not just Google Ads' own reports.
What's unclear so far
A few loose ends worth knowing about before you lean on this too hard: Google's help page doesn't date the change, and as of 15 November the English version listed the parameter itself without yet showing the "Tracking AI Max matches" section that explains it. The help documentation and the filter logic also aren't fully consistent with each other. And it's not yet confirmed whether the Google Ads API or Google Ads Editor exposes an equivalent field — so for now, this looks like a UI/URL-level reporting addition rather than something you can pull via API.
None of this changes bids, costs, or how AI Max actually matches queries. It just finally lets you see, after the click, how much of your "exact match" column wasn't exact match at all.
Want a second pair of eyes on how much of your account's reported "exact match" traffic is actually AI Max? Request a free account review.
Get new marketing updates in your inbox.
We email you when we publish something worth your time. No spam, unsubscribe anytime.
Sources
Facts in this article come from the sources above, checked on 17 November 2026. Platform features roll out in phases, so check your own account before acting. We update this page when official details change.
