AI Max broad expansions reach your site as keyword clicks
Published 2026-11-16
The common belief is that matchtype=e in a landing-page URL means the visitor typed something your
exact match keyword covers. Most tracking templates have carried {matchtype} for years, and most
match-type reports in GA4 or a CRM are built on it.
In an AI Max for Search campaign, that label describes the keyword, not the search. Google documents
{matchtype} as returning a only for AI Max keywordless matches. A click that AI Max won by expanding one
of your keywords arrives with e, p or b, like any keyword click. Google has now added a second
parameter, {search_term_matchtype}, that marks those clicks with a. On 16 November we found it on one
of 16 language versions of Google’s ValueTrack page: US English.
Two parameters, two questions
Both definitions are on Google’s ValueTrack page, one row apart. Every value is in facts above.
| Parameter | What it describes | Values | When it says a |
|---|---|---|---|
{matchtype} | “the keyword that triggered your ad” | e, p, b, a | AI Max keywordless only |
{search_term_matchtype} | “the search term that triggered your ad” | e, p, b, a | AI Max broad expansions and keywordless |
AI Max finds extra searches in two ways. Keywordless matching uses your landing pages and assets, and
no keyword is involved: {keyword} comes back blank and {targetid} carries a kwl- ID. Broad
expansion works through keywords: Google’s reporting page describes it as traffic from “broad match
keywords created by AI Max” from the keywords you added. Those clicks have a keyword, so {matchtype} has
a keyword match type to report, and it is not a.
So the old label was blind to exactly one of AI Max’s two methods. Keywordless clicks were always
visible in the URL. Broad expansions were not, and they landed in the same e, p and b buckets as
the queries your keywords were written for.
Decoding one click
Built from the ValueTrack definitions and the Google Ads API v26 enums, read 16 November. A dash means Google does not state the value.
| How the search matched | {matchtype} | {search_term_matchtype} | {targetid} | API SearchTermMatchSource |
|---|---|---|---|---|
| Your keyword, standard matching | e, p or b | e, p or b | kwd-… | ADVERTISER_PROVIDED_KEYWORD |
| AI Max broad expansion | e, p or b (which one: —) | a | kwd-… (by elimination) | AI_MAX_BROAD_MATCH |
| AI Max keywordless | a | a | kwl-… | AI_MAX_KEYWORDLESS |
Three things follow from the table.
You need two parameters to separate three kinds of traffic. {search_term_matchtype}=a alone tells
you AI Max matched, not how. Add {targetid}: kwl- is keywordless, kwd- is a broad expansion. A
template such as {lpurl}?matchtype={matchtype}&stmt={search_term_matchtype}&tid={targetid} carries all of
it.
The URL is coarser than the API. The API reports six search term match types, including
NEAR_EXACT and NEAR_PHRASE for close variants. The URL parameter has four letters. Google does not say
whether a close variant arrives as e or p, so “exact” in your CRM still includes close variants, as
it always did.
Google gives no date for the change. The page does not say when {search_term_matchtype} started
filling in. Every click recorded before you added it to your template carries only {matchtype}, so your
historical “exact” rows mix keyword matches and AI Max broad expansions, and nothing in the stored URL can
split them now. The Keywords report’s “Total: AI Max expanded matches” row gives you the aggregate in
Google Ads, but not per lead.
One language out of 16
We fetched the same help article in 16 languages on 16 November. Only hl=en lists
{search_term_matchtype}. The British, Australian and Indian English versions do not, and neither do
the French, German, Spanish, Italian, Portuguese, Dutch, Japanese, Korean, Chinese, Polish, Turkish or
Indonesian ones. All 16 already list the kwl keywordless label, so the keywordless half of AI Max has
been documented everywhere for some time.
ValueTrack parameters are not localised, so the parameter should work in any account. But a team that
reads Google’s help in its own language, or a UK team on en-GB, has no page telling it the parameter
exists. We could not test a live click: this is what the documentation says, not a measured result.
What it changes
- Re-read match-type reports built from URLs. Since you switched on AI Max, any GA4, CRM or BI
report that groups conversions by
matchtypehas counted broad expansions as keyword traffic. The “exact” row is the one that misleads most, because it is the one people trust. - Add
{search_term_matchtype}and{targetid}to the tracking template now. Clicks are only labelled from the day the parameter is in the template. Verify it fills in with a test click before you rely on it. - Do not read
aas “keywordless”. In{matchtype}it is; in{search_term_matchtype}it is either method. Name the two fields differently in your reporting so nobody joins them.
This is the same pattern as AI Mode ads, which serve inside your Search totals with no segment to pull them out: AI changes how the click was won, and the report keeps the old label. The URL parameter is only the label. It travels with the click and is a separate thing from the click ID that matches the conversion back to Google.
Once the label is right, one question remains. The conversion that click led to still has to be credited to a click, and “last click” picks a different one depending on which tool you ask.
Sources
- Google Ads Help, ValueTrack parameters page (US English): {matchtype} is 'the match type of the keyword that triggered your ad: "e" for exact, "p" for phrase, "b" for broad, or "a" for AI Max keywordless.'
verified 2026-11-16 - Google Ads Help, ValueTrack parameters page (US English): {search_term_matchtype} is 'the match type of the search term that triggered your ad: "e" for exact, "p" for phrase, "b" for broad, or "a" for AI Max broad expansions and keywordless matches.' The page gives no date for the parameter.
verified 2026-11-16 - Google Ads Help, ValueTrack parameters page: {targetid} is the ID of the keyword (labelled 'kwd'), the ID for AI Max keywordless ('kwl'), a dynamic search ad target ('dsa'), a remarketing list ('aud'), a product partition ('pla') or a hotel group partition ('hpi'). {keyword} returns a blank value when the ad matches without keywords, for example in AI Max for Search campaigns, DSA and Performance Max.
verified 2026-11-16 - Of 16 language versions of Google Ads Help answer 6305348 fetched on 16 November 2026, only the US English version (hl=en) lists {search_term_matchtype}. en-GB, en-AU, en-IN, fr, de, es, it, pt-BR, nl, ja, ko, zh-Hans, pl, tr and id do not. All 16 list the 'kwl' AI Max keywordless label in {targetid}. None shows a 'Tracking AI Max matches' section.
verified 2026-11-16 - Google Ads Help, About reporting in AI Max for Search campaigns: the Keywords report ends with two aggregate rows, 'Total: AI Max expanded matches' (traffic from broad match keywords created by AI Max based on the keywords you added) and 'Total: AI Max landing page matches' (search queries that matched because of your landing pages or assets, outside of your keywords). Filtering the search terms report for match type 'AI Max' may show lower numbers because the filter does not consider 'Other search terms'.
verified 2026-11-16 - Google Ads API v26 reference, SearchTermMatchSource enum: ADVERTISER_PROVIDED_KEYWORD, AI_MAX_BROAD_MATCH (the broad match expansion portion of AI Max), AI_MAX_KEYWORDLESS (the keywordless expansion portion of AI Max), DYNAMIC_SEARCH_ADS and PERFORMANCE_MAX.
verified 2026-11-16 - Google Ads API v26 reference, SearchTermMatchType enum: AI_MAX, BROAD, EXACT, NEAR_EXACT (exact match close variant), NEAR_PHRASE (phrase match close variant) and PHRASE, plus UNKNOWN and UNSPECIFIED.
verified 2026-11-16