Stripe revenue attribution
Track which session generated each Stripe Payment Link sale
Talivia connects Stripe Payment Links payments with the website session that led to checkout. The integration preserves an attribution signal before leaving the tracked site, waits for the provider to confirm payment, and then shows the source, campaign, landing page, and activity behind the revenue.
How it works
The attribution signal for Payment Links
Stripe client_reference_id or the verified Checkout Session returned to the success page supplies the bridge between the browser session and payment. The confirmed provider event remains the source of truth for payment status, amount, currency, subscriptions, and refunds.
Implementation path
How Stripe Payment Links attribution works
- 01
Track the website session
Install Talivia before checkout so the current session contains source, campaign, landing page, and visitor activity.
- 02
Carry the checkout signal
For a standard buy.stripe.com anchor, Talivia decorates client_reference_id with the current session. A tracked success page can use the returned Checkout Session ID as a fallback.
- 03
Wait for confirmed revenue
Stripe confirms the paid event. Talivia does not treat an opened or incomplete checkout as revenue.
- 04
Verify the paid journey
Open the payment in Talivia and confirm its source, landing page, session activity, and matching method.
Transparent limits
Important attribution limits
- A Payment Link shared outside the tracked website may produce a valid payment without any website session to attribute.
- If the required session or customer signal is absent, the payment is retained in revenue diagnostics instead of receiving a guessed source.
Questions
Stripe Payment Links attribution questions
What must I implement for Stripe Payment Links?
Stripe client_reference_id or the verified Checkout Session returned to the success page supplies the bridge between the browser session and payment. The required checkout action is: For a standard buy.stripe.com anchor, Talivia decorates client_reference_id with the current session. A tracked success page can use the returned Checkout Session ID as a fallback.
What happens when the Payment Links signal is missing?
A Payment Link shared outside the tracked website may produce a valid payment without any website session to attribute.
How do I verify Stripe Payment Links attribution?
Complete one sandbox or real Payment Links payment, wait for Stripe to report it as paid, then open the payment in Talivia and verify the matching method, source, landing page, pageviews, and events.
Explore related workflows
Related revenue tracking guides
Use your own data
Connect Stripe Payment Links to the session that paid
Install Talivia, follow the checkout-specific guide, and verify one sandbox or real payment before relying on the report.
Add my website