Lemon Squeezy revenue attribution
Carry website attribution into Lemon Squeezy API checkouts
Talivia connects Lemon Squeezy Checkout API 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 API
Custom checkout data returns with the Lemon Squeezy order webhook and bridges the paid order to its website session. The confirmed provider event remains the source of truth for payment status, amount, currency, subscriptions, and refunds.
Implementation path
How Lemon Squeezy Checkout API 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 reference to custom checkout data when your server creates the checkout.
- 03
Wait for confirmed revenue
Lemon Squeezy 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
- The backend must preserve the session value exactly; an API checkout created without it may remain unmatched.
- If the required session or customer signal is absent, the payment is retained in revenue diagnostics instead of receiving a guessed source.
Questions
Lemon Squeezy Checkout API attribution questions
What must I implement for Lemon Squeezy Checkout API?
Custom checkout data returns with the Lemon Squeezy order webhook and bridges the paid order to its website session. The required checkout action is: Add the current Talivia session reference to custom checkout data when your server creates the checkout.
What happens when the Checkout API signal is missing?
The backend must preserve the session value exactly; an API checkout created without it may remain unmatched.
How do I verify Lemon Squeezy Checkout API attribution?
Complete one sandbox or real Checkout API payment, wait for Lemon Squeezy 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 Lemon Squeezy Checkout API 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