See what your traffic brings.
Bring Stripe payments alongside your web analytics. Understand the sources behind sales, with a clear account of refunds, fees, and payments that remain unattributed.
No card required. All features included.Last-touch attribution links the payment to its last recorded source. It does not describe every influence on a purchase.
A checkout has a starting point.
A sale matters. Knowing which traffic led to it gives you another way to judge the work behind your site.
1.1Connect Stripe
Configure your payment connection and pass the visit’s attribution identifier into checkout. Pulse can then associate supported payment events with that visit.
1.2Last-touch attribution
Credit the last recorded touch associated with a payment. Read revenue alongside traffic sources and campaigns without switching between separate reports.
1.3Revenue over time
Follow payment trends across the selected period and compare them with the previous period.
More than the number at the top.
Gross revenue tells part of the story. An itemised view helps you understand what happened after the payment, too.
2.1Gross and refunds
See sales before deductions and refunds recorded through your payment connection.
2.2Fees and net
Keep recorded payment fees visible and read the resulting net revenue. Available fee data depends on the payment events received.
2.3Attributed and unattributed
Distinguish payments linked to a visit from those that could not be matched. Missing attribution remains visible in the report.
Traffic volume is only one measure.
Use payment attribution to ask a more useful question about the people coming to your site: which visits are connected to a purchase?
3.1Compare acquisition sources
Look at revenue by source to understand which channels are connected to payments, alongside how much traffic they bring.
3.2Explore campaigns
Connect tagged campaign visits with their attributed revenue to give your next launch a better reference point.
3.3Keep the limits in view
Treat last-touch as one attribution model. It does not describe every interaction that may have influenced a purchase.
A clear boundary around attribution.
Revenue attribution uses a tab-scoped identifier held in sessionStorage and hashed before insertion. Payments without a matching attribution identifier stay unattributed. This is separate from cookie-free visit counting, and is not a cross-device identity or a multi-touch attribution model.
Read about privacy at Pulse ↗