Payment tracking for Stripe revenue attribution.
Stripe knows the money. Your analytics knows the traffic. Neither knows the other. Point the webhook at SourceTrack and pass the visitor id when you create the Checkout Session, and a charge arrives attached to the session, campaign and click that produced it.
No credit card required · Under 5 minutes to install
Integrations
ATTRIBUTION STACK
Everything behind every payment tracking conversion, captured automatically.
SourceTrack captures the source on the first visit and keeps it tied to the lead all the way through to your CRM.
Traffic, conversions, and revenue by channel.
Know which channels drive qualified deals, not just empty clicks.
See every touch that led to the conversion.
Audit the full multi-touch discovery path before the conversion.
HOW IT WORKS
Three steps to track payment tracking with full attribution
One script tag, no complex setup, first-party tracking.
Connect Stripe / Shopify
Plug in your Stripe or Shopify webhook to sync customer purchases and subscriptions in real time.
Match buyer session history
SourceTrack connects online checkout payments back to the original visitor session and ad click.
True ROAS & revenue credited
Every dollar of customer revenue is tied to the ad, campaign, and referrer that created it.
HOW IT FITS TOGETHER
Payment tracking end to end.
One script tag on the left, your existing stack on the right, nothing to rebuild in between.
Payment sources
Revenue joins
The charge arrives by webhook and stitches to the visitor id that produced it. Refunds net out, and the idempotency key is claimed after the write so a retry cannot double-count.
WORKS WITH
Tools that pair with payment tracking.
The tools this feature is built around.
THE DIFFERENCE
The same conversion, before and after.
Without SourceTrack
- Stripe knows the money, analytics knows the traffic
- Refunds still counted as revenue
- Retries can double-count a charge
With SourceTrack
- One record holding both
- Refunds netted out of the channel
- Idempotency key claimed after the write
FAQ
UTM and lead source tracking FAQ
Do I need to change my checkout?
One small change. Point the Stripe webhook at SourceTrack, and when your backend creates the Checkout Session, pass the visitor id as client_reference_id or metadata.anonymous_id. The charge then stitches to the visitor on arrival. A payment that arrives without the id is still recorded, but as unattributed revenue rather than credited to a source.
What happens when an order is refunded?
The refund nets out of the channel it was credited to, so a source cannot look profitable on money that came back. This matters more than it sounds — unrefunded revenue reporting flatters paid channels most.
Stripe retries webhooks. Will a charge be counted twice?
No. The idempotency key is claimed after the write succeeds rather than before, so a retry can neither double-count nor silently drop the conversion.
EXPLORE PLATFORM
The rest of the SourceTrack platform.
Attribute every deal back to the click, AI referral, or ad that earned it.
SourceTrack connects your forms, bookings, and payments to first-party session journeys — so your team sees the source behind each conversion with no third-party cookies and no broken UTM fields.