Know which channel actually pays
Connect Stripe once and PulseTrack ties every payment back to the traffic source that produced it. Revenue per channel, not pageviews per channel.
Session → payment
Attributed to
Source · Twitter / X
Revenue per source
Google, Reddit, your newsletter — each one gets a euro figure, a transaction count and an average order value.
Landing pages ranked by money
The page with the most traffic is rarely the page that earns the most. See both numbers side by side.
Read-only, revocable access
You paste a restricted Stripe key that can only read charges. Revoke it from your Stripe dashboard at any time.
How it works
Add the tracking script
One tag on your site starts recording sessions and their traffic source.
Identify your customers
Call pulsetrack.identify(email) at signup or checkout so a session can be linked to a person.
Connect Stripe
Paste a restricted key. PulseTrack imports charges and matches them to sessions by email.
Frequently asked
Does PulseTrack take a cut of my revenue?+
No. PulseTrack reads your Stripe charges to attribute them and never touches money movement. You pay a flat monthly subscription regardless of the revenue you track.
What if a customer pays without ever being identified?+
That payment counts in your totals but sits in an unattributed bucket. The attribution rate shown on the dashboard tells you how much of your revenue is matched, so you know how far to trust the split.
Which Stripe permissions are required?+
A restricted key with read access to Charges and Customers. Nothing else. It cannot create charges, issue refunds or modify your account.
Does it work with payment providers other than Stripe?+
Stripe is supported today. Other providers are on the roadmap — the matching logic is provider-agnostic.