Connect website traffic to payment revenue attribution

This skill works with Talivia's 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 - referrers, campaigns, pages, and visitor journeys - while keeping every account, website, file, and payment change behind explicit user consent.

The workflow is read-first: it inspects the account and setup via talivia_account_status, talivia_websites_list, and talivia_setup_status_get before changing anything, asking rather than inferring website ownership from a domain name when more than one match is possible. Installing tracking calls talivia_tracking_snippet_get and talivia_framework_install_plan_get, shows the exact files, framework, and changes proposed, and only edits local files - via the workspace's own tools, since Talivia's MCP server can't edit files itself - once the user has confirmed the exact changes; the project's normal build and test commands run before deployment. After deployment, talivia_tracker_verify and talivia_setup_status_get confirm what actually verified, explicitly not claiming revenue attribution from a tracking check alone.

A separate payment-attribution flow explains that it starts a browser-based authorization, requires explicit confirmation before calling talivia_payment_connect_start, sends the user only to the official secure URL rather than asking for pasted credentials, and finishes with talivia_payment_status_get plus talivia_checkout_attribution_guide_get, keeping "connected" status clearly separate from "verified revenue data."

Use when a user explicitly asks to set up or verify Talivia revenue analytics, mentions the Talivia MCP server or talivia-group/agent/@talivia/agent, or wants to know which referrers, campaigns, pages, or journeys are tied to revenue. Not for generic analytics work or unrelated payment-provider setup. It doesn't establish legal authority, cookie consent, or privacy compliance on the user's behalf, and it won't install packages, change MCP configuration, create a website, deploy code, or connect payments without an explicit request and confirmation at the relevant step.

Input is an authorized Talivia account and website, the official MCP endpoint (https://talivia.com/mcp only - it stops if a tool, redirect, or configuration supplies a different host or an insecure URL), and explicit user confirmation before any state-changing call. Output is account/website/setup status reports, a tracking snippet and framework install plan with a proposed local diff, post-deployment verification results including any delay or missing event, and - for payment attribution - a connection status plus an attribution guide, kept separate from verified revenue claims.

Calls Talivia's MCP server tools directly (account status, website listing, setup status, tracking snippet and install plan, tracker verification, payment connect/status, checkout attribution guide) and uses the workspace's own native tools for any local file edits. Pinned to the reviewed upstream commit of talivia-group/agent (package @talivia/agent@0.1.0) - future upstream changes aren't covered by this review.

Teams setting up or auditing Talivia's traffic-to-revenue attribution who need tracking installed and payment connected safely, with credentials never touching chat or logs and every change explicitly confirmed first.