Connect website traffic to payment revenue attribution

This skill sets up and verifies Talivia revenue analytics through its MCP server, which connects website traffic and visitor journeys to payment revenue. It inspects an existing Talivia setup, installs or verifies website tracking, and reviews traffic-to-revenue attribution, while keeping account, website, file, and payment changes behind explicit user consent.

Its safety gate requires: confirming the user owns or is authorized to manage the Talivia account and target website; using only the configured official MCP endpoint, https://talivia.com/mcp, and stopping if any tool, redirect, or local configuration points to a different or insecure host, never sending a credential to an unverified endpoint; keeping credentials out of chat, prompts, tool arguments, source files, and logs, and never requesting or exposing payment API keys, OAuth secrets, or bearer tokens; reading the current account and website state before changing anything, reusing an existing website where possible, and calling talivia_websites_create only after the user explicitly asks to create one; and, before any state-changing MCP call, stating the exact account, website, action, data involved, and expected effect, then getting explicit confirmation.

The workflow has three stages. Inspecting the current setup calls the read-only tools talivia_account_status, talivia_websites_list, and talivia_setup_status_get, without inferring account ownership or website identity from a domain name alone, asking when more than one website matches. Planning and installing tracking calls talivia_tracking_snippet_get and talivia_framework_install_plan_get for the selected website, shows the files and changes before making them (since Talivia MCP cannot edit local files itself), edits locally only after explicit confirmation while preserving existing analytics, consent, and security controls, and runs the project's normal build and test commands before deployment. Verifying after deployment calls talivia_tracker_verify and talivia_setup_status_get, reporting what was actually verified including any delay, missing event, or unverified deployment, and never claiming revenue attribution from a tracking check alone.

For payment attribution specifically, the skill explains that it starts a browser-based authorization flow, gets explicit confirmation before calling talivia_payment_connect_start, sends the user only to the secure URL returned by the official flow rather than asking for pasted credentials, and finishes with talivia_payment_status_get and talivia_checkout_attribution_guide_get, clearly separating connected status from verified revenue data.

Use it when the user explicitly asks to set up or verify Talivia revenue analytics, mentions the Talivia MCP server, talivia-group/agent, or @talivia/agent, or wants to know which referrers, campaigns, pages, or visitor journeys are associated with revenue.

Do not use it for generic analytics work or unrelated payment-provider setup. It also does not establish legal authority, cookie consent, or privacy or payment-provider compliance for the user, and it does not install packages, change MCP configuration, create a website, deploy code, or connect payments without an explicit request and confirmation at the relevant step. Talivia's own metrics may be delayed or incomplete and do not prove causation.

Inputs are the Talivia account and website to inspect or configure, and explicit user confirmation at each state-changing step. Outputs are account and website status, a tracking snippet and framework install plan with a shown local diff, tracker verification results, and payment connection and attribution status, always reported with their evidence and uncertainty rather than inferred causation.

It integrates with the official Talivia MCP server at https://talivia.com/mcp and, through it, with the user's website tracking and connected payment provider. The reviewed package version is @talivia/agent@0.1.0, pinned to a specific reviewed upstream commit of talivia-group/agent rather than a guarantee about future upstream changes.

It is for marketers and site owners who use Talivia to connect website traffic to payment revenue and want tracking installation and payment attribution handled with explicit confirmation at every account, file, or payment-affecting step.