Clarvivo
DocumentationRevenue attribution

Revenue attribution

See the marketing work behind a paying customer

Revenue attribution joins a signed payment event to the visit and campaign context that led to it. Connect the provider first, then make the small checkout change that carries the browser visitor ID to your server or provider metadata.

Supported payment providers

Clarvivo supports signed revenue webhooks from Stripe, Lemon Squeezy, Polar, Paddle, Razorpay, and Dodo Payments. It also provides a signed custom revenue API for a payment system that is not on that list.

Connect a provider

  1. 1

    Open Integrations

    Go to Dashboard → Integrations → Payment Providers and select the provider your checkout uses.
  2. 2

    Create the webhook

    Copy the provider-specific webhook URL and event list from the setup panel into your payment provider’s webhook settings.
  3. 3

    Store the signing secret

    Copy the provider signing secret into the Clarvivo integration settings. Do not put it in browser code or an MCP prompt.
  4. 4

    Add attribution context

    Use the integration wizard or MCP to add the recommended server-side checkout edit. It passes the Clarvivo visitor ID (clv_vid) through provider metadata, custom data, or notes.
  5. 5

    Complete a test payment

    Confirm the payment arrives in Revenue, then check revenue by source to make sure the visit is being connected to the payment.

Use the custom revenue API safely

For a custom checkout, send revenue only from a trusted backend. The project ingest secret is private and must never be placed in frontend JavaScript, a browser pixel, or a public repository. The full signed-request contract and provider-by-provider webhook steps are in Manual integrations.

Read attribution honestly

Revenue with campaign context can be grouped by source. Revenue without it is grouped as Direct or unattributed; that does not mean the customer appeared from nowhere, only that the purchase could not be tied to a recorded campaign.