Full Answer

Google AI Mode generates conversational answers at the top of search results, with product recommendations and citations linking directly to merchant sites. When a user clicks one of those links, Google appends adview_query_id to the destination URL. The parameter carries a token tying the visit to the originating AI Mode query and, when ads appeared alongside the answer, to the specific ad impression. It is Google's way of tracking its own AI-generated referrals — and yours, if you capture it.

The distinction from gclid matters. gclid identifies paid clicks from Google Ads campaigns. adview_query_id identifies clicks from AI Mode answers, which may be organic citations or ad-adjacent placements. Treating them the same — or ignoring adview_query_id entirely — means you cannot separate AI Mode performance from standard organic search. Given that AI-referred visitors convert at significantly higher rates, this is revenue intelligence you are [leaving invisible](https://seresa.io/blog/data-loss/912-million-ad-blockers-are-hiding-a-third-of-your-woocommerce-traffic).

For WooCommerce stores, capturing adview_query_id requires server-side parameter extraction. The parameter arrives in the landing page URL, but GA4's default configuration does not parse or report on it. A server-side tracking layer can read the parameter from the incoming request, store it against the session, and pass it downstream as a custom dimension — giving you a clean channel for [AI Mode attribution](https://www.signalbridgedata.com/blog/server-side-tracking-benchmark-report-2026) that GA4 cannot provide on its own.