Find the local leads
visiting your
clients’ websites.
LocalPulse is hosted analytics for the agencies and local businesses that care about leads, not bounce rates. Drop one snippet on the site — every visit from the target city gets classified, identified, and pushed to Slack in real time.
Three lines of script. Real leads in seconds.
No SDKs, no cohort builders, no funnel composer. The whole product collapses into: install the snippet, set a target city, watch for the alert.
One snippet, paste before </body>
Generated per client with a unique key. Uses sendBeacon with a fetch + keepalive fallback.
Add the cities you care about
City match wins over region. Multi-location? Add a target per branch and every visit tags itself with the matched location.
Slack fires the moment one lands
Header, location, company, device, dwell, source, keyword, page journey — and a one-click deep link straight into the visit detail.
Built around where a visit came from.
Most analytics treat geography as a filter. We treat it as the primary signal. Every visit is classified against your client’s target cities, region-matched as a fallback, and tagged with the matched location.
- City beats region. A perfect city match wins; region is fallback. The result is stored on every visit.
- Multi-location. Franchises tag visits per-branch and filter the dashboard to one location at a time.
- ISP buckets. Business, consumer ISP, hosting, education, government — so a Comcast subscriber doesn’t read like a lead.
- VPN-aware. iCloud Private Relay and ~20 named VPNs are flagged so misleading geo doesn’t silently mis-attribute.
The whole session, in one row.
Click any visit. It expands inline into a session timeline — page-by-page dwell, attribution, device, locale, ISP, identity. No second page, no modal.
- Filter for signal. Local, Businesses, Identified, Today, This week. Tabs that match the question you actually ask.
- Returning is a badge, not a row. Re-visits inside a 30-minute window extend the session instead of inflating counts.
- Per-location scope. Multi-location clients can pin the feed to a single branch and the analytics follow.
- Honest pagination. Past 10,000 visits the UI shows “10,000+” instead of walking the table.
An alert that earns the ping.
Four-mode scope per client — off, local, all, b2b. When one fires, it gives you the six things you need: who, where they are, how long they were on the site, what page they hit last, what they searched for, and a deep link straight into the visit detail.
- One webhook per client, test-fired from settings
- First visit of a session pings; subsequent pageviews don’t
- Optional digest companion — daily, weekly, or monthly
- /· 0:38
- /services/water-heater-repair· 2:11
- /about· 0:54
- /contact· 2:58
Get a name next to the visit. No CRM required.
The snippet itself watches for form submissions on the host site, scores each input against HTML5 type, autocomplete, and a hint built from name + id + placeholder + aria-label + label text, then upserts identity on (clientId, visitorId). Sensitive fields are refused unconditionally.
- password — sensitive type
- message — no identity hint
Who this is for.
Three ways teams use LocalPulse today. Same product, same install — different rosters and different reporting needs.
Per-client snippet keys, per-client Slack channels, per-client digests on the client's own timezone. The whole workflow is built around running a roster, not a single site.
Configure one target per branch and every visit tags itself with the matched location. The per-location filter scopes both the visit feed and the analytics charts to a single branch at a time.
One site, one channel, one digest. The full feature set is the same as the Agency tier — the difference is roster size, not capability.
Flat monthly fee. No pageview caps.
Three plans, each with a fixed client-site count. Charged by tier, not by visit — a regional law firm pulling 80,000 sessions a month and a body shop pulling 800 cost the same.
Operator
- Up to 3 client sites
- Real-time feed + Slack alerts
- Identity capture + email digest
- Multi-location targets
Studio
- Up to 25 client sites
- Everything in Solo
- Per-client timezone + digest schedule
- Per-location filter on dashboard
- Install verification + status pill
Network
- Up to 100 client sites
- Everything in Studio
- Priority support · 4-hour
- Onboarding assistance
The questions agencies always ask first.
Will it work alongside Google Analytics or Plausible?
Yes. LocalPulse is a parallel install — the snippet doesn’t conflict with other analytics tags or tag managers. Most agencies run it alongside whatever the client already has, because LocalPulse is asking a different question (who is here, right now, from our target city) than top-of-funnel analytics.
How do you handle GDPR and privacy?
Do you charge by pageview?
What if my client site is behind Cloudflare?
Can I add target locations to a client after the fact?
Find the leads you’re already missing.
LocalPulse is currently running for internal pilots. Drop a line and we’ll line you up for the next access wave the moment we open seats.