AI agents are buying from your store. Your analytics can't see it.
ChatGPT, Perplexity, and shopping agents don't run JavaScript — so the revenue they drive lands in GA4 as “Direct.” Klemvo joins server-side signals to your order data and files AI-driven revenue where it belongs: in the dashboards you already use.
of global online orders were AI-influenced last holiday season — $262B.
Salesforce, holiday 2025of AI-origin traffic lands as “Direct” in GA4 by default. Invisible.
Loamly, 446k-visit dataset, Feb 2026annual growth in agent-executed purchases — the trackable rails are compounding.
eMarketer, Dec 2025A human session leaves 40+ signals. An agent leaves six.
Your measurement stack was built for browsers: pixels, tags, cookies. Agents fetch, parse, and disconnect — the tags never fire. The result is a structural blind spot no channel grouping can fix.
Tags never fire
GA4 and Meta Pixel depend on JavaScript executing in a browser. Agent traffic bypasses the entire client-side stack at the transport layer.
Revenue files as “Direct”
A store doing $50M GMV has no way to know if AI-driven orders are 1% or 15% of it — so budgets, catalogs, and bids ignore their fastest-growing channel.
The channel converts
AI-referred visitors convert up to 42% better than other traffic. The least visible channel is also one of the best-performing ones.
Detect. Join. Restore.
No tags, no code on your critical path — Klemvo works from the server side, where agent traffic is actually visible.
Spot the agents
Agent checkouts via protocol session IDs (ACP, UCP, AP2). Click-throughs from ChatGPT, Perplexity & Copilot via referrer and journey signals — including the ones GA4 misfiles today.
Match traffic to orders
Server-side signals joined to your order webhooks, confidence-labeled — deterministic where protocols allow it, honest estimates where they don't. Never a black box.
Fix your dashboards
Recovered attribution pushed natively into GA4, Meta CAPI, and Google Ads offline conversions — so your reports and your ad algorithms finally see the truth.
Then comes the question the data unlocks: why do agents fetch your products but not recommend them? Klemvo's readiness reports find the missing structured data, blocked endpoints, and feed gaps costing you AI sales.
Two-click on Shopify. Full-depth on your own stack.
App install, no engineers
Orders via webhooks, journeys via the API, catalog checks against what Shopify broadcasts to AI channels. Attribution restored to GA4 and your ad platforms — beyond what the admin shows you.
Middleware or log stream
If you own your infrastructure, Klemvo sees everything: which agent visited, which products it fetched, and how that crawl became a purchase — the full join.
One free tool. One subscription. One partnership.
Three products, one ladder — each one earns the next.
AI Revenue Audit
90 days of your history, analyzed once. You get one number nobody else can show you: how much of your revenue was AI-driven and misfiled as “Direct.”
Start here →Attribution
Recovery into GA4, Meta, and Google Ads — plus the growth loop: catalog monitoring, breakage alerts, and proof of which fixes became AI orders.
Learn more →Diagnosis & Optimization
Why agents skip your products — and fixing it: schema gaps, endpoint blocks, feed losses, and catalog optimization for AI channels. For brands where AI revenue is worth real money.
Learn more →The honest answers, up front.
What exactly do you need access to?
An order webhook and log or customer-journey access — read-only, off your critical path. On Shopify that's an app install; on your own stack, a log stream or middleware. No tags on your storefront, no code changes, nothing that can slow down or break your store.
Is our customer data safe?
Access is read-only, identifiers are hashed, and each store's data stays its own — we never pool or sell customer-level data. What we learn across stores is about agents (which bots, which patterns), never about your customers.
Shopify already labels AI orders in my admin. Isn't that enough?
That label stops at the admin wall. Your budget decisions live in GA4, Meta Ads Manager, and Google Ads — which still file that revenue as “Direct,” so your ROAS math and bidding algorithms train on wrong data every day. We fix the record where the money decisions happen, and cover the click-through revenue Shopify's label misses entirely.
How do you handle matches you can't be sure about?
Every number is confidence-labeled. Agent checkouts with protocol IDs are deterministic; tagged click-throughs are near-certain; anything uncertain is shown as a clearly-marked estimate — never blended into the verified figure. If we can't prove it, we say so.