LemonSqueezy Subscriptions and Renewals
Preserve attribution across subscription signup, renewals, failures, and lifecycle changes.
Attribute the first subscription checkout with the same Talivia session field used for a one-time order. Use automatic decoration for a standard Checkout Link, or set checkout_data.custom.talivia_session_id through the Checkout API.
LemonSqueezy includes that custom data in the initial order and subscription webhooks. Talivia stores the LemonSqueezy customer and subscription relationship so later renewals can stay connected even though no new browser checkout occurs.
Events Talivia maintains
The managed webhook processes:
- subscription creation and updates;
- cancellation, resumption, pause, unpause, and expiration;
- successful, failed, and recovered subscription payments;
- subscription payment refunds.
Successful renewal invoices become new revenue payments. Failed payments update subscription state without creating paid revenue, and refunds reduce the original payment's net revenue.
Keep the customer relationship stable
Do not create a new LemonSqueezy customer for every renewal or plan change. Keeping the provider customer and subscription IDs stable lets Talivia reuse the attribution established by the initial checkout.
If a renewal is unattributed, first confirm the initial checkout contained meta.custom_data.talivia_session_id, then confirm later events use the same LemonSqueezy customer and subscription.