Stripe revenue attribution
Attribute custom Stripe Payment Intents to the session that paid
Talivia connects Stripe Payment Intents 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 Intents
PaymentIntent metadata keeps the session reference with a custom Elements, web, or mobile payment until Stripe confirms it. The confirmed provider event remains the source of truth for payment status, amount, currency, subscriptions, and refunds.
Implementation path
How Stripe Payment Intents 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
Add the current Talivia session ID to PaymentIntent metadata when your server creates the payment.
- 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 PaymentIntent created before the website session is known cannot be matched through metadata unless another reliable customer relationship already exists.
- 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 Intents attribution questions
What must I implement for Stripe Payment Intents?
PaymentIntent metadata keeps the session reference with a custom Elements, web, or mobile payment until Stripe confirms it. The required checkout action is: Add the current Talivia session ID to PaymentIntent metadata when your server creates the payment.
What happens when the Payment Intents signal is missing?
A PaymentIntent created before the website session is known cannot be matched through metadata unless another reliable customer relationship already exists.
How do I verify Stripe Payment Intents attribution?
Complete one sandbox or real Payment Intents 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 Intents 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