Exact match, with an asterisk

Pull up the match type report your team trusts most. Not the one inside Google Ads, the one in your CRM or BI tool, the one that says exact match leads close at twice the rate of broad and therefore exact keywords deserve the budget. For most accounts that report is built on a single URL parameter, {matchtype}, that has been riding on every click for years.

Since AI Max for Search arrived, that label has been telling a half truth. When AI Max expands one of your keywords to catch a search you did not write for, the click still lands on your site wearing your keyword’s match type. An exact keyword’s expansion arrives as “e”. Your exact row has been quietly absorbing traffic that an AI system chose, and nothing in the stored URL could tell you which rows.

Last week the missing label turned up in Google’s documentation. A new ValueTrack parameter, {search_term_matchtype}, returns “a” when AI Max won the click, including the expansions the old parameter hid. It is free, it takes a few minutes to add, and it only labels clicks from the day you add it. With Black Friday on November 27, that last part is the whole story.

This is a docs-based review. I read Google’s three ValueTrack help pages, the AI Max reporting help page and the Google Ads API reference, and the coverage from PPC News Feed, Search Engine Land, The Keywordless, PPC Land and Trackingdesk. I have not fired a test click through a live account, so everything below is what the documentation says, not what I measured.

What it is

ValueTrack parameters are placeholders. You write them into a tracking template, a final URL or a custom parameter, and at the moment of the click Google swaps each one for a real value: the campaign, the device, the keyword. Whatever reads the landing page URL afterwards, your analytics, a hidden form field, a call tracking script, can store that value against the visit and carry it into the lead record. This is how match type ends up in a CRM at all.

AI Max for Search is Google’s AI layer on Search campaigns: it matches search terms beyond your keywords, rewrites ad text and can swap the landing page. It finds the extra searches two ways. Keywordless matching works from your landing pages and assets with no keyword involved. Broad expansion works through your keywords; Google’s AI Max reporting page describes that traffic as coming from “broad match keywords created by AI Max” based on the ones you added. Since September, Google has been upgrading campaigns that used the campaign level broad match setting or automatically created assets onto AI Max, so plenty of advertisers run it without ever having chosen it in a planning meeting.

What changed last week

The main ValueTrack table now carries two rows that look almost identical. {matchtype} is “the match type of the keyword that triggered your ad,” with “a” reserved for AI Max keywordless. The new {search_term_matchtype} is “the match type of the search term that triggered your ad,” and its “a” covers “AI Max broad expansions and keywordless matches.”

One question is about your keyword, the other is about the search. In plain keyword matching they agree. With AI Max on, they split exactly where you need them to.

Google’s About ValueTrack parameters page now has a section called Tracking AI Max matches that lays out four traffic classes. A standard keyword match returns your keyword’s type in both parameters and a keyword ID in {targetid}. An AI Max broad expansion returns your keyword’s type in {matchtype}, a keyword ID, your keyword’s text, and “a” only in the new parameter. Keywordless expansions return “a” in both, an empty keyword and a “kwl” ID, with kwl-3500001 marking Google’s default automated expansion. Keywordless URL rules return “a” in both and an ID tied to your own URL rule. The How you can use ValueTrack page adds a worked example and a template that carries keyword, both match types and target ID.

PPC News Feed reported it on November 11, credited to Hana Kobzová, and Search Engine Land and The Keywordless followed the same day. None of Google’s pages gives a date for the change, and nobody has found a Google announcement.

Cut paper collage of two nearly identical blue paper keys hanging side by side, one with a small extra red notch that a silhouetted hand examines through a round lens.

What works

The split is clean. Filter for clicks where {matchtype} is e, p or b and {search_term_matchtype} is “a”, and you have AI Max expansion traffic. Same {matchtype} values without the “a”, and you have keyword traffic you wrote for. Add {targetid} and the keywordless clicks separate into Google’s default expansion and your URL rules. Four traffic classes, three parameters, one template. Google documents both filters in plain words, which is more than it usually does.

The label travels. Google Ads already reports AI Max in aggregate: the Keywords report ends with a “Total: AI Max expanded matches” row, and the search terms report has an AI Max match type. Those numbers stay inside Google Ads. A URL parameter goes wherever the click goes, into the form fill, the opportunity, the closed won deal, the refund. That is the layer where you find out whether expanded traffic actually turns into revenue, and it is the layer Google does not grade for you.

It finally lets you size the problem in your own data. How much of your “exact” traffic is really AI Max? PPC Land’s coverage of an analysis by Mike Ryan of Smarter Ecommerce put the share of exact match impressions served through AI Max expansions at nearly 29% by July 2026, across 383 million EMEA ecommerce Search impressions. That is one study of one vertical, and impressions are not leads. Your number could be far lower or higher. Until now you could not compute it per lead at all.

And it costs nothing to try. It does not touch bidding or matching, as Search Engine Land points out, so adding it cannot change how a campaign spends.

What breaks or is unclear

History is gone. Clicks are labelled from the day the parameter sits in your template. Every lead you collected before that carries only the old {matchtype}, and no stored URL can be split after the fact. If you have been arguing about whether AI Max helped since your September upgrade, the URL data will not settle it. The fresh data starts whenever you add it.

Most of the documentation does not show it. On November 16 I checked the main ValueTrack page in British English, French and German, and the About page in British English: none listed the new parameter. Trackingdesk checked 16 language versions of the main page the same day and found it only on US English. ValueTrack names are not localised, so the parameter should work in any account, but a London agency reading the en-GB help center has no page telling it this exists. PPC Land also noted that the main page’s own template example still shows only {matchtype}; the AI Max section lives on the About page.

The URL is coarser than the API. The Google Ads API’s SearchTermMatchType enum includes 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. The asterisk got smaller, not gone.

One letter, two meanings. In {matchtype}, “a” means keywordless. In {search_term_matchtype}, “a” means either method. If someone on your data team joins those two fields or labels them both “match type,” you will build a report that is confidently wrong in a new way.

Performance Max is not covered. Neither parameter appears in the help page’s Performance Max compatibility table. This is a Search campaign tool.

Your template can break your landing pages. Google warns on the same page that AI Max’s final URL expansion can serve 404s if your tracking template is not compatible, and recommends {lpurl} at the start. If your template was built years ago by an agency that has since left, editing it in Black Friday week deserves a test before it goes live.

It labels, it does not judge. Knowing a lead came through an expansion does not tell you whether AI Max created that lead or just relabelled a search your broad keyword would have caught anyway. That needs a holdout or an experiment, not a parameter. Search Engine Land makes the same point.

Cut paper collage of a long trail of footprints across cream paper where a kneeling silhouetted figure has started placing small red markers, leaving the earlier footprints behind them unmarked.

Who it is for

Anyone running AI Max for Search who judges keywords outside Google Ads. That means lead gen and B2B teams whose real conversion is a qualified opportunity in a CRM, ecommerce teams reconciling Search against margin in a BI tool, and agencies whose client reports come from analytics rather than the Ads interface. If you were upgraded to AI Max in September and your exact match keywords got more expensive or less efficient in your own reporting, this is the first tool that lets you see why at the lead level.

It matters less if you only read performance inside Google Ads, where the aggregate AI Max rows already exist, or if you have no AI Max campaigns at all.

Pricing and limits

The parameter is free; it is a tracking feature, and you pay for clicks as usual. The limits are the ones above: Search campaigns only, no Performance Max, four values with close variants undefined, no history, documentation visible only on US English pages as of November 16, and no announced date. Neither Google nor the coverage says whether Google Ads Editor exposes an equivalent field. Treat it as live but quietly shipped, and verify with your own test click rather than trusting the help page.

What to do this week

Add it today, next to the old one. Put {search_term_matchtype} and {targetid} alongside {matchtype} in the tracking template of your largest AI Max campaign, as separate parameters with distinct names. Do not replace {matchtype}; reports already built on it should keep working. Keep {lpurl} at the start.

Test one click before you trust it. Use Google’s landing page test or click your own ad, and confirm the value lands in the URL, survives any redirects and reaches the analytics or form field you expect. Check one expanded landing page too, so the template change does not introduce a 404 right before your heaviest traffic of the year.

Pipe it into the lead record. If your forms capture keyword and match type into hidden fields, add one more field for search term match type. A parameter that only lives in analytics sessions will not reach the CRM, and the CRM is where this pays off.

Rename the fields in your reporting. Call one “keyword match type” and the other “search match type.” Write down that “a” means different things in each. It takes five minutes and saves a quarter of bad decisions.

Mark the date. Note the day you added the parameter in your reporting notes. Every comparison of expanded versus keyword traffic starts there; anything earlier is mixed.

Plan the read for December, not now. Holiday traffic will give you the biggest sample you will get all year. In the second week of December, compare cost per qualified lead or margin for expansion clicks against keyword clicks on the same keywords. If the expansions hold up, keep them. If they are padding your exact row with weaker traffic, you will finally have the per lead evidence to tighten AI Max or move budget, instead of a hunch and a screenshot.

Tell whoever owns your templates. If an agency or developer manages tracking, send them the About ValueTrack page this week, and mention that the British English version does not show it yet.

AI Max was always going to change how your clicks were won. What it did not do, until last week, was admit it in the one place your downstream reports could see. Google added the label quietly and without a date. Add it before Black Friday, or your best traffic of the year arrives with the old half truth attached.