See what visitors do after they arrive.
Follow each tracked session from its source through pages and actions. See whether your chosen goal happened, and where to look when it didn't.
Example: 1,000 sessions viewed an article; 40 recorded a later goal event in that same session.
Check the article link and verify the goal event before changing your traffic strategy.
| Source | Sessions | Conversions | CVR | Revenue |
|---|---|---|---|---|
| Google / organic | 482 | 39 | 8.1% | $741 |
| Reddit / referral | 211 | 31 | 14.7% | $589 |
| Direct | 190 | 12 | 6.3% | $228 |
| X / social | 104 | 9 | 8.7% | $171 |
SESSION JOURNEYS
See the pages and actions in a visit.
Open a session to see its source, pages visited, actions and the time between them. A goal counts only when its event was recorded.
Illustrative flow. One session can visit multiple pages. A store click is not an install; revenue requires a monetary event.
Session A63F2C
Google / organic · Mobile · Illustrative events
This example shows a tracked store click, not a verified app install or sale.
Add my websiteDECISIONS
See what changed, then decide what to test.
Pulse shows the numbers behind a change. Optional Jev review can highlight one area to examine. You decide whether to run the suggested test.
Jev review is an optional pilot for selected Pro/Business projects. Pulse tracks recorded events; it does not record screens or infer installs or sales.
Example from a website · DEMO
An article gets visits. Few sessions record the chosen goal afterward.
POSSIBLE EXPLANATION
The link to the next step may be hard to find.
CHANGE TO TRY
Move the link higher on the page and compare recorded goal events.
What you can track
Sources and pages
Where sessions start, what they read and where they go next.
Funnels
Which tracked actions happened, and in what order.
Your goal
Signups, clicks or purchases—each only when its event is recorded.
Optional Jev review
A suggested area to check, based on aggregate event counts.
A visit is more than a pageview.
See the source, pages and tracked goal together. Revenue appears only when you send a payment event.
Arrive
See where a session started and which page it opened.
Browse
Follow the pages visited in that session.
Act
Track signups, clicks or payments as separate events.
Review
Compare the sessions that reached your goal with those that didn't.
Decisions
See which page, source or goal changed, with the numbers beside it.
Funnels
Choose tracked events and see how many sessions move between steps.
Sources and goals
Compare source traffic with your chosen goal and recorded payment events.
Pick a plan for your websites.
Start with one project. Upgrade for more sites, events and history.
Compare the plans
| Feature | Free | Pro | Business |
|---|---|---|---|
| Projects | 1 | Up to 10 | Unlimited |
| Monthly events | 10,000 | 100,000 | Unlimited |
| Dashboard history | 7 days | 30 days | Unlimited |
| Realtime + sources + pages | Included | Included | Included |
| Goals + revenue attribution | Included | Included | Included |
| AI integration guide | Included | Included | Included |
| CSV exports | — | Included | Included |
| Usage + traffic spike emails | — | Included | Included |
| 90-day + 1-year analytics ranges | — | — | Included |
FAQ
Does it slow down my site?
The tracker is dependency-free, deferred and sends events asynchronously.
Do you record sessions?
No. Pulse intentionally does not record DOM snapshots, keystrokes or form contents.
Does it work with Next.js and React?
Yes. It detects history API navigation in SPAs and normal page loads.
Can I track purchases?
Yes. Send pulse.track('purchase', { revenue: 49, currency: 'USD' }).