Full Answer

The instinct to block AI agents comes from a real concern: bots have historically meant scraped content, inflated analytics, and wasted server resources. But shopping agents are a different species entirely. They arrive with purchase intent, carry payment credentials, and complete transactions — they're closer to high-intent referral traffic than to crawlers.

Adobe's Q1 2026 Digital Economy Index tracked AI-referred sessions across major retail sites and found conversion rates 42% above organic and average order values 37% higher. That gap is widening as agents get better at matching products to buyer intent. A blanket robots.txt block or WAF rule that catches shopping agents alongside training crawlers quietly shuts off a growing revenue channel without the store owner realising what they've lost.

The practical approach is segmentation, not exclusion. Server-side tracking lets you tag agent sessions at the request level — before the data reaches GA4 or your ad platforms — so agent-driven revenue shows up as its own line item rather than polluting your human-visitor metrics. You get clean attribution for both cohorts without losing either. The three categories that matter are training crawlers (block them — they take content without sending traffic), search bots (allow them — they drive referral visits), and shopping agents (allow them — they drive purchases). For a breakdown of how these visitor types differ, see Crawler, Search Bot, or Shopping Agent: The Three Species of AI Traffic.