Show every client the AI traffic their analytics can’t see
You manage a book of client sites, and every one of them is asking whether AI is sending them anything, while their analytics buckets it all as “Direct.” Lume gives you one project per client: who’s really crawling their content (verified vs. spoofed), whether AI answers send humans back, and where crawlers hit 403s that drop pages from those answers. It won’t rank a client or get them cited. It proves whether the work you did landed, server-side and unsampled.
Sound familiar?
- Half my clients are asking whether AI is sending them traffic, and their analytics just shrugs and buckets it all as “Direct.”
- A client’s crawlers could be getting 403s on the pages we just optimized, and I’d have no way to see it until the AI answers quietly dried up.
- I did the GEO work. Now the client wants proof it landed, and I don’t have a number that shows AI actually started showing up.
- Every client site is one more dashboard to log into, and not one of them tells me who’s really crawling the content.
What Lume does for you
Every client’s AI traffic, in one place
One project per client site, each matched against the live catalog: 56 cataloged bots, crawlers, and AI agents across 36 operators. See verified bots, AI crawlers, and AI-referred humans across your whole book of business, server-side and unsampled, not the JavaScript-only, sampled picture their analytics gives them.
The report clients can’t get anywhere else
Who’s really crawling their content, verified vs. spoofed (verification runs for 7 major operators); whether AI answers are sending humans back across 15 assistants; and where crawlers hit 403s and 429s that quietly drop those pages from AI answers. Concrete, defensible, ready for the monthly review.
Prove the work landed
After a GEO or technical-SEO engagement, show the before-and-after: whether crawlers can now reach the pages, and whether AI referrals actually started arriving: crawl, citation, referral. Honest framing: Lume measures the outcome; it doesn’t do the ranking.
Low-cost, always-on, exports into their stack
Cheap per-site instrumentation that runs alongside the analytics each client already has and exports back into it, so every number lands in the dashboards they already read, with a next step attached, not one more login they’ll ignore.
Fits every client’s stack
One ingest token per client site and you’re live. Report traffic from WordPress, the CDN, or the edge: low-cost, always-on instrumentation that runs alongside the analytics they already have and exports back into it.
Agency FAQ
Is this a GEO / rank / share-of-voice tool?
No. Lume measures the real traffic on your client’s own server: which agents are hitting the site, whether they’re authentic or spoofed, and whether AI answers send humans back. It won’t rank a page or get it cited; pair it with your GEO tool and use Lume to prove the outcome.
How do multiple client sites work?
A project per client site. Instrument each one and read them side by side. Client data stays separate while you see the whole book of business in one place.
Can I show this to clients or put it in my reports?
Export the data (CSV, and back into the analytics and warehouse your client already uses) so the numbers land in the dashboards and reports they already read. Lume hands you the data; how you present it to the client is yours.
How long does it take to set up per client?
Minutes. Start from the client’s edge or CDN logs, or drop in a dependency-free SDK: zero client JS, zero added latency, and no rebuild of their site.
Will clients trust the numbers?
They rest on verified identity: Web Bot Auth (RFC 9421, Ed25519), forward-confirmed reverse DNS, and published IP ranges for 7 major operators. Lume never stores a full client IP either: it’s truncated to a network prefix before anything is persisted.
Give every client the AI-traffic report they can’t get anywhere else.
Free plan, one ingest token per site. Instrument your first client and see what’s really crawling their content.
Start for free →