Full Answer

The adview_query_id parameter works as a session-level attribution stamp. When a user triggers an AI Mode response in Google Search, the platform embeds this identifier in the session alongside an adview_type value (type 4 for AI Mode impressions). Together, these parameters create a traceable chain from the original query through to any conversion event on the destination site — the same attribution model Google uses for traditional paid search, applied to an AI-generated answer surface.

What makes this significant is the scale Discovered Labs documented. Their network traffic analysis found adview_query_id active across 547+ ad delivery flows, complete with placeholder timing for ad units that have not yet gone live. The infrastructure is not experimental — it mirrors the mature measurement stack behind Search and Shopping campaigns.

For WooCommerce store owners running conversion tracking, the practical implication is straightforward: conversions arriving through AI Mode already carry attribution data, but most analytics setups are not configured to capture it. Client-side tracking loses these parameters to ad blockers and Safari ITP before they reach GA4 or Google Ads. Server-side tracking captures the full URL on first contact, preserving the adview_query_id for accurate attribution. Without it, AI Mode conversions show up as unattributed direct traffic — a growing blind spot as AI Mode usage scales (see: adview_query_id — Google's AI Mode Attribution Stamp).