Talivia Docs
Talivia Docs
HomeDashboard
IntroductionInstallationGetting updates
SessionsReplaysHeatmapsPerformanceCompareBreakdownGoalsFunnelJourneyRetentionUTMRevenueAttribution
Analysis

Attribution

Understand how Talivia connects traffic and revenue.

Attribution connects a payment back to the visitor and session that created it.

Matching signals

Talivia can match payments with:

  • visitorKey, sessionKey, or sessionId from window.talivia.getSession().
  • Stripe checkout session id from session_id={CHECKOUT_SESSION_ID} on the return URL.
  • Provider customer ids passed through identify.
  • Email or email hash when available.
  • Payment provider events and imported payment records.

Settings

Open Settings -> Attribution to configure:

  • Default currency and timezone.
  • First-touch or last-touch model.
  • Owned domains.
  • Ignored query parameters.
  • Payment URL detection.
  • Cross-domain tracking settings.

Unknown attribution

If Talivia receives a payment but cannot match it to a visitor, the payment appears as unattributed. Use Revenue Diagnostics to see which signal is missing.

Search keyword revenue

Google and Bing do not reveal the exact search query for each individual visitor session. Talivia estimates keyword revenue by distributing organic page revenue across imported query clicks for that page.

Revenue

Previous Page

Using boards

Next Page