Full Answer

Shopping agents work in two modes. Browser-based agents — the kind ChatGPT, Perplexity, and Gemini deploy — open a headless browser, navigate your WooCommerce storefront, add items to the cart, and complete checkout exactly as a human would. API-based agents skip the browser entirely and interact with WooCommerce through the MCP (Model Context Protocol) commerce layer, pulling product data and placing orders programmatically. Both modes generate real revenue, but they look nothing alike in your analytics.

The challenge is measurement. Browser-based agents often appear as direct or referral traffic in GA4 because they don't carry standard UTM parameters or referrer headers. API-based agents bypass the browser altogether, so client-side analytics never registers them at all. Seresa's breakdown of the six types of AI visitors your analytics mixes together (https://seresa.io/blog/ai-data-readiness/stop-calling-it-ai-traffic-the-six-types-of-ai-visitors-your-analytics-is-mixing-together) explains why lumping all non-human traffic into one bucket hides your highest-converting channel.

Server-side tracking at the PHP hook level is the only reliable way to separate agent purchases from human conversions, because it fires on the order event itself — no browser required. Without that separation, stores make budget decisions on incomplete attribution.