Inside your brand kit · Traffic Analysis · Live · Local · AI-Aware
The client's own analytics — with the junk removed
Open the page and the traffic is just there — live, free, zero configuration. Where it comes from (AI assistants included, honestly counted), whether it can actually buy (the Local Lens), the pages that leak, and the events that matter. Bank a snapshot monthly with an AI-written verdict, and hand the client a white label report. The movement between snapshots is the story.
The monthly loop
Watch it live — bank it monthly — prove the movement
The live layer is always on and always free. The ritual is the bank: store the window each month and every number gets a partner to move against — the movement between snapshots is the story a client renews for.
IS THE STORY
Dashboards show you today and forget. The bank-and-compare arc is the retainer — every fix returns as movement the client can see.
The Flow Canvas · Watch Visitors Walk the Site
See the site the way visitors move through it
This isn't a chart you look at — it's an interactive canvas you drive. Click any page and it becomes the center: what flows in on the left, where visitors go next on the right, with the real traffic numbers riding every connection.
One page's world at a time
Never the whole spaghetti graph: pick a page and see what flows in from the left — other pages and outside referrers — and where visitors go next on the right, edge thickness by volume.
Click a neighbor, follow the path
Any neighboring page becomes the new center with one click — walk the site link by link, the way a visitor actually travels it.
Zero setup, working day one
Built from Google's own page-to-page records — no tags, no tracking code, no configuration. Every page gets its verdict: a distributor that passes traffic on, or a cul-de-sac where it stops.
The Page Dossier · Search Console × Analytics
Google Analytics for agencies — two dashboards, joined on one card
The question both dashboards make you answer by hand — what's the whole story of this one page? — answered per page, automatically.
The join nobody shows
Analytics knows what visitors did; Search Console knows what they searched. The dossier joins them per page — the report pros assemble by hand across two tabs, automatic.
Every page, whole story
Unfold any page: its traffic and engagement, the exact queries driving it with positions and clicks, its senders, and its internal flow in and out.
It prints, too
The busiest pages carry their dossiers into the white label client report — the chapter that makes a client say nobody's ever shown me my site like this.
AI Assistants · Engine by Engine
AI traffic analytics — which AI assistants sent customers, and what they did
Every engine gets its own row — a floor count, a trend, and the actions its visitors took. AI attribution at the conversion level.
Engine by engine, honestly
ChatGPT, Perplexity, Gemini, Claude — each with its own floor count ('at least N', because AI visits without a referrer hide in Direct), its trend, and its sources.
What those visitors did
The part nobody else shows: the events AI-referred visitors fired — sign-ups, clicks, conversions. 'ChatGPT sent 7 visitors and they signed up' is a sentence backed by data.
The channel of the decade, tracked
AI referrals flow into the channel mix, the client report, and the monthly snapshot — so the month the AI channel takes off, the record already exists.
AI Attribution · How This Is Measured
The stamp rides the whole way
ChatGPT tags every link it hands out. That tag stays on the visitor through your site, through login, and onto the sign-up — if three things are set.
Counted as a floor — AI visits that arrive without the tag land in Direct.
1Record the sign-up in the visitor's browser
A sign-up your server records on its own has no visitor attached. It lands in Unassigned — the count is right, the source is gone.
2Link your domains
If people arrive on www. and sign up on app., link the two in your Google tag so the visit survives the hop.
3Tell Google to ignore your login screen
Add accounts.google.com (or your provider) to unwanted referrals. Otherwise the trip to log in overwrites where they came from.
The traffic, end to end
One read-only Google connection covers Search Pulse and Traffic Pulse together — then every panel below is live, with setup measured in taps, not configuration.
The live layer
Open the page — the traffic is just there
No run button, no configuration: the client's own analytics read live on open, shaped for an agency — the daily pulse line, sessions, people, and engagement, each with its change against the span before. Pick any window; every number carries its dates.
The mix
Channels — with the AI assistants counted
Organic, paid, direct, social, referral — and the channel nobody else shows: visits referred by AI assistants like ChatGPT and Perplexity, carved out honestly and counted as a floor, because AI visits without a referrer hide in Direct. Each channel carries its new-visitor count and its delta.
The local lens
Can this traffic actually buy?
Set the client's service area — tap the observed cities or type one — and one number answers the local advertiser's real question: what share of located sessions came from places that can become customers. Per page too: the blog post with 4,000 sessions and 2% local share gets caught automatically.
The leaks
Pages that waste their traffic
Landing pages taking meaningful traffic but engaging at less than half the site average get flagged LEAK — the fix-first list, computed from the client's own behavior, feeding straight into the creative work the studios already do.
The events
The actions that matter, chosen once
The picker lists every event the property actually recorded — including custom ones — and you tap up to six worth tracking: sign-ups, purchases, calls. Those become atomic cards with deltas and top-channel attribution, and they're the only events the client's report ever shows.
The page dossier
Every page's whole story, one card
Analytics and Search Console joined per page: what lands on it, the searches driving it (queries, positions, clicks), who sends it traffic, and how the site itself feeds it. The report the pros assemble by hand across two dashboards — unfolded per page, automatically.
The flow canvas
Watch visitors walk the site
A full-screen canvas that shows one page's world at a time — what flows in from the left, where visitors go on the right, edge thickness by volume. Click any neighbor to follow the path, page by page. Built from Google's own page-to-page records: zero tracking setup, working on day one.
The intelligence layer
Buckets opened, mysteries diagnosed
Click any channel to see the actual sources inside it. Unassigned traffic gets a diagnosis — each unlabeled pair, its plain-English cause, and the fix. Tagged campaigns read back by name, and the AI channel opens engine by engine: ChatGPT, Perplexity and the rest, each with what its visitors actually did.
The deliverable
Snapshots, verdicts, and the report
Bank the window monthly: the full picture stored permanently with an AI-written executive verdict. The white label analytics report — agency mark, client logo, the pulse line, the mix opened to its sources, AI engine by engine, the page dossier, the local lens, the leaks, how visitors move — prints to PDF, and the recommended-actions page always detaches. A section rail chooses exactly what each client sees.
Run the whole loop from Claude
Read the live traffic, bank the monthly snapshot, and deliver the white label report — the same loop, driven from a conversation.
Read the traffic
“How's Acme's traffic right now — channels, AI referrals, local share, and what changed?”
Bank the monthly snapshot
“Bank Acme's traffic snapshot for the month since the last one.”
Deliver the report
“Generate the Traffic Pulse report for Acme and give me the link to send.”
Same-day numbers are still settling — Google finalizes traffic data after about a day. The page and the report both say so instead of pretending.
A meaningful share of AI-driven visits arrive with no referrer and land in Direct — unclassifiable by anyone. The AI Assistants number reads 'at least N', and means it.
City comes from the network connection and can be missing or wrong; sessions without a city are excluded from local share and the page says how many.
The connection reads the client's analytics and nothing else — nothing is ever written to their account, and disconnecting removes the stored credential entirely.