Pulse counts the people who visit your sites with no cookies, no stored IP addresses, and no consent banner. This site shows it running on the fictional StrataForge Robotics’ own websites.
Pulse is two things: a tracking script that counts pageviews and events, and a dashboard, an API, and 62 agent tools that read them back. Everything below is built today.
Visitors, pageviews, sessions, bounce rate, and average visit length for Today, 7 days, 30 days, 90 days, 12 months, all time, or any range you pick, with an hourly or daily chart. Click a row anywhere and every number filters to it.
Pages, sources, campaigns, keywords, countries, regions, cities, devices, browsers, operating systems, screen sizes, and languages. Entry pages and exit pages are available through the API and agent tools.
A count of visitors in the last five minutes, a chart of the last 30, and the top pages, sources, and countries, refreshed every five seconds.
A feed of sessions as they move through the site, pushed to the page over a server-sent event stream. Sessions are grouped under the first eight characters of an hourly hash and drop off after 30 minutes.
Largest contentful paint, layout shift, interaction to next paint, and first input delay, measured in the visitor's own browser and shown at the 75th percentile by site, page, or device, colored by Google's thresholds.
Off until a site turns them on. Clicks are stored as a percentage position on the page and scroll depth as a percentage, never the text or the element, and drawn as a scatter on a plain background.
A goal is a page pattern such as /products*, a named event, or an event that carries revenue. Conversions and conversion rate come back from the API and agent tools.
Chain page views and events into steps and see how many visitors reach each one and where they drop out.
Give each visitor a variant, count impressions and conversions from the same script, and read a chi-squared significance test. Concluding a test names the winner when the result clears the confidence level you set.
pulse.track(name, props) from your own code, or data attributes in the HTML. Outbound link clicks, file downloads, form submissions, and 404 pages are tracked on their own unless you turn that off.
Five report types: traffic summary, top pages, source analysis, goal conversions, and device breakdown. Run one and download it as CSV through the API.
Five attribution models (last touch, first touch, linear, time decay, and position based) over a visitor's touchpoints, and named milestones that annotate the timeline. Both are API and agent tools.
The script sets no cookie and writes nothing to local or session storage. It sends nothing from a browser that says it is under automation.
A visitor is a SHA-256 hash of the site, the connection, the browser, and a salt that changes at midnight UTC, so the same person looks new tomorrow. The hash is the only identifier stored.
A hit is counted only when its page address is the site's domain, one of its allowed domains, or a subdomain of either. Anything else is dropped without an error.
Known crawlers are dropped by their user agent, and each site can list addresses to exclude, such as the office, so staff visits do not count.
Real captures of the running tool, with fictional StrataForge Robotics data. They follow your theme.
Add one script tag with the site's id to your pages. It loads from Pulse's own tracker host, weighs about 2.5 KB gzipped, and has no dependencies.
Each pageview and event goes to the collection endpoint. Pulse checks the host, drops bots and excluded addresses, reads the browser and the country, hashes the visitor, and throws the address away.
The dashboards, the API, and the agent tools read the same stored rows, with hourly snapshots speeding up the headline numbers.
Set goals, build funnels, run an A/B test, and save the reports you check every week.
Pulse's dashboard is a web app, and this is what its code, its tests, and an axe-core scan run for this site show today. It has a skip link, landmarks, labeled controls, and an automated axe test that passes in jsdom. The same axe-core run in a real browser on every captured view finds serious color-contrast failures (white text on the app's violet accent, 2.9 to 1) and a labeling failure on clickable breakdown rows. It has not been tested with a screen reader. We do not claim a conformance level for the app, and the app's README claim of WCAG 2.1 AA is not one this site repeats.
Partly supported
Every page starts with a "Skip to main content" link, the site switcher is a labeled select, the navigation items are links, and each clickable row in a breakdown is a button that takes Tab focus and answers Enter and Space. The date range and tab controls are buttons. Nobody has walked every flow with only a keyboard, and the heatmap canvas and charts have no keyboard equivalent.
Partly supported
Controls carry labels, and the site's own pages have landmarks. An automated vitest-axe test passes on the app and eight routes in jsdom. The browser axe run found two structural gaps: the pages open with a second-level heading and no first-level one, and the clickable breakdown rows have a label ("Filter by /") that does not contain the text shown. Pulse has not been tested with VoiceOver, NVDA, or JAWS, whatever the app's README says.
Not supported
The app's violet accent behind white text, used for primary buttons and the active date range, measures 2.9 to 1, below the 4.5 to 1 that WCAG AA asks for. axe-core reported color-contrast failures on all 13 captured views, in light and in dark, 325 elements in all. Most of the rest of the palette comes from the Renkara design system and was not measured on its own.
Partly supported
The design system's global stylesheet shortens animations and transitions to almost nothing when the system asks for reduced motion. The Realtime page's counter pulse is drawn with an animation library, and nobody has confirmed in a browser with the setting on that it stops.
Not yet tested
Nobody has tested Pulse at larger text sizes or browser zoom. Several labels are set in small fixed sizes (11 to 13 pixels), so large text may crowd them.
Not yet tested
Nobody has run the dashboard at 375 pixels. Reading the code, the left navigation is hidden below 768 pixels and the top bar is given no menu items for a site's pages, so on a phone there may be no way to move between Dashboard, Realtime, Goals, and the rest. That is unverified in a browser.
| Tracking script |
|
|---|---|
| Backend |
|
| Dashboard |
|
| Location and devices |
|
| Agents and API |
|
| Quality |
|
| Stands in for | Google Analytics, Plausible |
Pulse ships an MCP server so a coding or planning agent can read the numbers and set up measurement: ask how a campaign did, add a goal, start an A/B test, or save a report.
list_sitescreate_siteget_siteupdate_sitedelete_siteget_snippetget_statsget_timeseriesget_pagesget_entry_pagesget_exit_pagesget_sourcesget_campaignsget_keywordsget_locationsget_regionsget_citiesget_devicesget_browsersget_osget_screensget_languagesget_eventsget_realtimeget_visitor_typesget_web_vitalsget_heatmapget_attributioncreate_eventbatch_eventslist_goalscreate_goaldelete_goalget_goal_conversionslist_site_goalscreate_site_goallist_funnelscreate_funnelget_funneldelete_funnelget_funnel_resultslist_testscreate_testget_teststart_testconclude_testdelete_testget_test_resultslist_milestonescreate_milestoneget_milestonedelete_milestonelist_reportscreate_reportget_reportdelete_reportcreate_report_schedulelist_report_schedulesdelete_report_scheduleget_mecheck_service_healthget_diagnosticsThe tracking script sets none and uses no local or session storage, and every request it makes omits credentials. That is checked in the code on this site's behalf, and the Privacy page says what that does and does not prove. The dashboard itself, which only the people running the analytics use, keeps its sign-in token in the browser's local storage.
This site does not claim that. Pulse is built to collect less: no cookies, no stored IP address, an identifier that changes daily. Whether a given site needs a notice or consent depends on the law where its visitors are and on what else the site does, and that is a question for a lawyer, not for this page.
StrataForge Robotics, the fictional company from the novel The Deferral. Its six websites, their daily traffic, and its campaigns come from a shared fictional dataset, and the screens show one visit in ten of that traffic so the numbers stay light. No real site, visitor, or customer appears anywhere.
Pulse runs in production for Renkara's own sites, and this site is a preview of what it does. To ask about access, write to contact@renkara.com.
No. Nothing in the tracking script, the collection path, or the dashboard calls a language model. The agent tools let your own agent read the numbers.
Write to Renkara Media Group and a person will answer.