Stripe revenue attribution
Connect Stripe Checkout revenue to the session that created it
Talivia connects Stripe Checkout Sessions 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 Checkout Sessions
Checkout metadata carries the current Talivia session ID into the Stripe payment lifecycle. The confirmed provider event remains the source of truth for payment status, amount, currency, subscriptions, and refunds.
Implementation path
How Stripe Checkout Sessions 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
Attach the current Talivia session ID when your backend creates the Checkout Session.
- 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
- Attribution depends on adding the session signal when the Checkout Session is created. A checkout created without it may require a weaker return-page or customer match.
- If the required session or customer signal is absent, the payment is retained in revenue diagnostics instead of receiving a guessed source.
Questions
Stripe Checkout Sessions attribution questions
What must I implement for Stripe Checkout Sessions?
Checkout metadata carries the current Talivia session ID into the Stripe payment lifecycle. The required checkout action is: Attach the current Talivia session ID when your backend creates the Checkout Session.
What happens when the Checkout Sessions signal is missing?
Attribution depends on adding the session signal when the Checkout Session is created. A checkout created without it may require a weaker return-page or customer match.
How do I verify Stripe Checkout Sessions attribution?
Complete one sandbox or real Checkout Sessions 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 Checkout Sessions 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