A playbook in action · Live · Local · AI-aware
The client’s own analytics — read the way you’d read it
Four playbooks, one monthly rhythm. One read-only Google consent covers this and Search Pulse. The live read is free and always current — the channel mix with AI assistants carved onto their own line, the share of located traffic that sits in the client’s service area, and the pages quietly losing attention. Bank the month when you want it on the record, then forward the white-label report.
New here? Connecting Claude takes about a minuteThe rhythm, in four moves
The live read never charges. Banking a snapshot is 150 tokens, confirmed first.
Traffic pulse setup · free
One consent covers both pulses
The same read-only Google connection powers Search Pulse and Traffic Pulse — connect once, approve both permissions, and each client kit maps to its own analytics property. Then two small choices make the rest of it yours: tap up to six of the events Google actually recorded for that site, and set the service area by tapping the cities already showing up in the data or typing one that hasn't yet. Read-only throughout; nothing is ever written to the client's Google account.
“Set up Traffic Pulse for Acme — is Google connected, and which property is mapped to this kit?”
The agency's own Google account, connected once. Nothing written back, and disconnecting removes the stored credential.
The picker shows what Google actually recorded — sign-ups, purchases, calls. The report tracks only what you tap.
Tap the observed cities, or type one that hasn't shown up yet — a new local client has no traffic to observe.
Traffic pulse read · free, always
Three questions no analytics dashboard answers
The live read is current as of now, and it never charges — sessions, channels, landing pages, events, devices, each carrying its window and its change against the span before it. But the reason it exists is the three reads underneath: which assistants are sending anyone, whether the traffic can actually buy, and which pages are quietly leaking.
“How is Acme's traffic doing this month?”
Always a floor, never a total. An AI visit that arrives without a referrer lands in Direct like any other, so the honest number is “at least” — and the page says so every time it shows one.
What share of located sessions sits inside the service area — measured over located sessions, because a quarter arrive with no city at all.
Pages taking meaningful traffic but engaging under half the site average get flagged. The fix-first list, straight from the data.
Your chosen events with per-channel attribution — so “which channel actually produces sign-ups” has an answer.
Traffic pulse snapshot · 150 tokens
Bank the window — the movement is the story
The live read is free forever; banking is the paid act, and Claude states the price and waits for your go. A snapshot stores the full payload permanently along with an AI-written executive verdict — two confident sentences a client reads first, grounded in that window's numbers. Bank each month starting where the last one ended, and the movement between snapshots becomes the client-progress story no live dashboard can tell.
“Save a Traffic Pulse snapshot for Acme so we have this month on the record.”
Start where the last snapshot ended and the windows line up on their own — no bookkeeping.
An executive read written into every snapshot, so the headline is done before you open the report.
The bank returns a live link that becomes the full client report when it completes — no login, live for seven days.
Traffic pulse report · free
Forward the link — and print 1 to N if you want findings only
White-labeled with your agency mark and the client's logo, stating the window up front. It arrives as a clickable link, live for seven days, and prints to PDF with a client-ready filename. The method page is part of the deliverable, not an appendix — it states plainly that the read is read-only, that same-day figures settle over about a day, that the AI number is a floor, and that local share is measured over located sessions.
“Generate the Traffic Pulse client report for Acme and send me the link.”
The actions page starts a fresh printed page by design, so the same file is either your proposal or a findings document — your call, at print time.
Not the dashboard the client already ignores
Same underlying data. The difference is which four questions it decides to answer.
The AI channel, carved out
Assistant referrals get their own line instead of hiding inside Direct — counted as a floor, and labelled as one. Nobody else separates it.
Can this traffic buy?
The Local Lens answers the question a local client actually asks. Sessions are worthless if they're in the wrong country.
Leaks, not vanity
Pages are ranked by where attention is being lost, not by which got the most visits. The fix-first list writes itself.
Banked, so it compounds
A live dashboard forgets. Snapshots hold each month on the record, so month-over-month movement is provable a year later.
Four playbooks, one rhythm
Set it up once, read it whenever you like for free, and bank the month when it counts.
Google Analytics connected read-only, the property mapped, events and service area chosen.
The live traffic, read like an analyst — channels, AI referrals, local share, leaks, events.
The window banked permanently — payload, verdict, and the live link to watch it land.
The white-labeled traffic report — generated and linked, ready to forward.
The layer that proves the other four worked.
AI Visibility Pulse measures the answer engines. Search Pulse measures Google. Campaign Pulse measures the ads. Traffic Pulse is the only one that can say what any of it did once the visitor arrived — which is the question every client asks at the end of the month.