Brand kit/Traffic Pulse

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.

MOVEMENT
IS THE STORY
Watchthe live layer · free
Bankthe monthly snapshot
Actfix the leaks · aim local
Comparesnapshot vs snapshot

Dashboards show you today and forget. The bank-and-compare arc is the retainer — every fix returns as movement the client can see.

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.

Live on openFree, alwaysWindow-over-window

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.

AI Assistants channelAn honest floorNew visitors per channel

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.

Local sharePer-page local %Type or tap cities

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.

LEAK flagsEngagement vs site averageFix-first list

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.

Pick from what existsUp to sixPer-channel attribution

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 report — agency mark, client logo, the pulse line, the mix, the local lens, the leaks, the events — prints to PDF, and the recommended-actions page always detaches.

Monthly ritualAI verdictDetachable actions

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.

Works inClaude.ai (web)Claude CoworkClaude Code— no API key needed.

Read the traffic

Ask Claude to

“How's Acme's traffic right now — channels, AI referrals, local share, and what changed?”

Bank the monthly snapshot

Ask Claude to

“Bank Acme's traffic snapshot for the month since the last one.”

Deliver the report

Ask Claude to

“Generate the Traffic Pulse report for Acme and give me the link to send.”

Fresh data is provisional

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.

The AI channel is a floor

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.

Geography is an estimate

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.

Read-only, always

The connection reads the client's analytics and nothing else — nothing is ever written to their account, and disconnecting removes the stored credential entirely.