Installation

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>

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

Install with a coding agent

Settings → Tracking also provides a short, ready-to-copy prompt with your website's actual script, domain, and installation guide link. Give it to a coding agent working in your site's codebase. The prompt asks the agent to install the tracker across the site using the framework's shared layout and send a signup event after registration succeeds. Review the resulting code and verify a real page view and signup event in Talivia.

If you are preparing the request manually, use this version and replace the placeholder with the complete snippet from your website settings:

Install Talivia in this project. Add the script below site-wide via the shared layout. After a successful signup, call window.talivia?.track('signup'). Verify events arrive.

PASTE_TRACKING_SCRIPT_HERE

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.

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.

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

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