Talivia Docs
Talivia Docs
HomeDashboard
IntroductionInstallationTeamGetting updates
Stripe
Yolfi
Dodo Payments
LemonSqueezy
LemonSqueezy Checkout LinksLemonSqueezy Checkout APILemonSqueezy Return URL FallbackLemonSqueezy Subscriptions and RenewalsTest and troubleshoot LemonSqueezy
Polar
Manual Payment APITesting payment integrations
Integrations
llms.txtllms-full.txt
RevenueLemonSqueezy

LemonSqueezy Return URL Fallback

Match an order through the tracked return page when checkout metadata is unavailable.

View Markdown

Direct session metadata is the strongest attribution method. Use the return URL only when you cannot modify the checkout link or the API request.

Add the order ID to the return link

In the LemonSqueezy product settings, set the confirmation modal button link to a tracked page and include the supported order_id variable:

Confirmation button URL
https://your-site.com/thanks?order_id=[order_id]

After payment, LemonSqueezy replaces [order_id] with the real order ID. When the customer opens that page, the Talivia tracker records the order reference and matches it with the verified order_created webhook.

Limits of return attribution

  • The tracker must be installed on the return page.
  • The customer must click the confirmation button and return in the same browser.
  • If the customer opened a shared checkout without first visiting your site, Talivia can record the payment but there is no earlier acquisition session to recover.
  • Do not use the return page to fulfil the order; the signed webhook remains the payment source of truth.

For links rendered on your tracked website, use Checkout Links instead. For server-created checkout, use Checkout API.

LemonSqueezy Checkout API

Pass the Talivia session when your backend creates a custom LemonSqueezy checkout.

LemonSqueezy Subscriptions and Renewals

Preserve attribution across subscription signup, renewals, failures, and lifecycle changes.