Record the session before Yolfi checkout
Talivia stores the first referrer, campaign values, landing page, visitor identity, and the product activity that happened on your website.
Yolfi revenue attribution
Talivia connects Yolfi Payment Links and Checkout Sessions with the visitor source, campaign, landing page, and activity that led to payment.
YolfiPayment providerThis payment was attributed to a customer from google.com who landed on /pricing
How the integration works
Connect the Yolfi organization once. Payment Links and backend Checkout Sessions return their Checkout Session ID to a tracked success page, where Talivia joins the verified payment with the active visitor session.
Talivia keeps the payment event as the source of truth for revenue and the website session as the source of acquisition context. When the available identifiers agree, the payment inherits its referrer, campaign, landing page, visitor, and first-touch or last-touch attribution fields.
Supported checkout paths
Choose the path your customers already follow. Talivia uses the strongest supported session signal available for that flow, without forcing you to replace the provider or move checkout onto a new page.
A reusable Yolfi link returns the completed Checkout Session ID to your tracked site.
Attribution method
A completed payment becomes useful marketing data only after its provider identity is joined with the browser session. Talivia records that relationship as one inspectable attribution record instead of hiding the match inside a conversion total.
YolfiTalivia stores the first referrer, campaign values, landing page, visitor identity, and the product activity that happened on your website.
The native integration supplies the payment status, amount, currency, checkout identity, customer identity, and supported subscription or refund events.
Talivia uses Checkout Session ID, return-page data, or the strongest supported fallback to connect the payment with a session and report the match confidence.
Revenue reporting
Attributed Yolfi payments appear beside the website dimensions you already use to understand traffic. Compare referrers, channels, campaigns, keywords, and landing pages by revenue, then expand a row to inspect the latest payment behind it.
The payment record keeps the amount, provider, payment status, acquisition source, landing page, and match confidence together. That makes aggregate reporting useful without losing the ability to investigate an individual customer journey.
Open the Yolfi setup guidePayments after checkout
Revenue attribution does not stop at the first successful checkout. Talivia keeps later payment events attached to the strongest known customer relationship and leaves unmatched revenue visible when that relationship is missing.
$29.00ConnectionTalivia receives the payment record from Yolfi and keeps browser attribution separate from payment verification.
$29.00Return matchThe returned Checkout Session ID links the completed Yolfi checkout with the active tracked session.
$89.00RenewalsOnce the initial subscription checkout is matched, future payments can reuse the saved relationship.
Practical answers about connecting Yolfi payments with website sessions, checkout signals, subscriptions, and refunds.
Talivia receives verified Yolfi payments and uses the Checkout Session ID on the tracked return page to connect each payment to a browser session.
Yes. Configure the link to return to a tracked page with the Yolfi Checkout Session ID after payment.
Yes. Checkout Session API flows use the same success-page match as dashboard-created Payment Links.
Yes. The first subscription payment must be matched so later renewals can reuse the established customer relationship.

Yolfi revenue attribution
Connect one website, complete a test payment, and verify the source, landing page, and paid session in Talivia.