Installation

Install the tracker and connect payments so Talivia can attribute revenue to traffic.

Installation has two useful steps: add the tracker to your site, then connect the payment system that creates revenue.

Step 1. Install the tracker

The Talivia tracker works anywhere you can add a script tag. Start with the universal snippet, then use a framework guide only when you need exact placement for your stack.

Universal snippet

In the app, open the website, go to Settings -> Tracking, and copy the snippet generated for that website.

<script
  defer
  src="https://talivia.com/script.js"
  data-website-id="YOUR_WEBSITE_ID"
  data-domain="example.com"
></script>

Always copy the snippet from your website settings. Replace YOUR_WEBSITE_ID with the real ID from Talivia Settings -> Tracking. Do not reuse the example value.

Place the snippet before the closing </body> tag, or load it through your framework's shared document/layout component.

Talivia Cloud usually includes data-domain in the generated snippet. A website running on one hostname also works without it, but keeping the generated value lets the root website and its subdomains share the same visitor and 30-minute rolling session. You do not need to add or remove this attribute manually for a normal installation.

If your flow crosses to a different root domain, add the owned domains under Settings -> Attribution and copy the refreshed snippet.

Tracking overviewSee what the script records automatically and which runtime functions it exposes.Tracker configurationUnderstand optional script attributes, storage, filtering, and collection settings.Subdomain trackingKeep one visitor identity across a root website, app, docs, and checkout.

Framework and builder guides

If your site uses a framework, CMS, ecommerce platform, or no-code builder, open the guide below for the exact place to paste the same snippet. Framework examples focus on placement and may omit optional attributes, so use the complete code generated in Settings -> Tracking.

Next.jsApp Router and shared layouts.ReactVite, CRA, and static HTML shells.VueVue apps and shared HTML entry points.NuxtNuxt app head and plugin setup.AngularWorkspace index.html or runtime injection.SvelteKitGlobal app template placement.AstroBase layouts and content sites.RemixRoot document and Scripts component.SolidStartRoot document setup.QwikRoot layout and head placement.GatsbySSR document hooks.ExpoExpo Web and static HTML.LaravelBlade layouts and shared app views.DjangoBase templates and inherited pages.Ruby on RailsApplication layout and ERB templates.ExpressEJS, Pug, or static HTML shells.NestJSServer-rendered templates or static clients.FlaskJinja base templates.PhoenixRoot layouts and LiveView pages.WordPressTheme footer, child themes, or snippet plugins.ShopifyTheme layout and storefront pages.WixDashboard custom code settings.WebflowSite custom code and project settings.SquarespaceCode injection for all pages.FramerCustom code before body end.TildaSite-wide HTML before body close.

Step 2. Connect payments

Traffic only becomes useful revenue analytics after Talivia can see payment events. Choose the payment path that matches your checkout.

StripeConnect a restricted API key and let Talivia configure webhooks.YolfiConnect the account and configure the Checkout Session return URL.LemonSqueezyUse provider events when LemonSqueezy powers checkout.PolarUse Polar payment events when your product sells through Polar.Dodo PaymentsConnect one API key; Talivia creates the payment and refund webhook.Manual Payment APISend payments from your backend or custom processor.

For hosted providers that expose a unique checkout return ID, configure that provider's return placeholder. For custom payment flows, pass window.talivia.getSessionId() as supported provider metadata or as sessionId to the Manual Payment API. The Revenue guides document each provider's preferred signal.

Verify the install

Open your website in a normal browser tab.
Visit a page that includes the tracker.
Return to Talivia and open the website dashboard.
Look for a new session, page view, referrer, browser, and country.
After payment setup, make a test payment and confirm revenue appears in the same website.

Installation has two useful steps: add the tracker to your site, then connect the payment system that creates revenue.

Step 1. Install the tracker

The Talivia tracker works anywhere you can add a script tag. Start with the universal snippet, then use a framework guide only when you need exact placement for your stack.

Universal snippet

In the app, open the website, go to Settings -> Tracking, and copy the snippet generated for that website.

<script
  defer
  src="https://talivia.com/script.js"
  data-website-id="YOUR_WEBSITE_ID"
  data-domain="example.com"
></script>

Always copy the snippet from your website settings. Replace YOUR_WEBSITE_ID with the real ID from Talivia Settings -> Tracking. Do not reuse the example value.

Place the snippet before the closing </body> tag, or load it through your framework's shared document/layout component.

If your flow crosses to a different root domain, add the owned domains under Settings -> Attribution and copy the refreshed snippet.

Open your website in a normal browser tab.
Visit a page that includes the tracker.
Return to Talivia and open the website dashboard.
Look for a new session, page view, referrer, browser, and country.
After payment setup, make a test payment and confirm revenue appears in the same website.