Clarvivo

Free tool by Clarvivo · no login

Find campaign context that leaks before payment

Supply the public page and checkout destination on either side of your handoff. We compare observable URL context without adding items, starting a checkout, or placing an order.

Campaign page

Supply the two public URLs on either side of the payment handoff. We compare URL-level campaign continuity and never add an item, start checkout, or place an order.

This tool answers: Does campaign context disappear before a payment-provider handoff?

Enable JavaScript to run the check — the diagnosis itself is free and needs no account.

Why this happens

A checkout provider is often a separate domain. That breaks first-party cookie access and can replace an acquired source with a payment referral, Direct session, or no attribution at all.

The browser cannot truthfully prove what a gateway stored in its session or webhook, but it can expose the first visible break: campaign context present before the handoff and absent on the explicitly supplied public destination.

Next checks

These answer the questions this one tends to raise.

How this check works

So you can trust the result — and your developer can verify it.

  1. Use two caller-supplied URLs

    We do not discover or click checkout buttons. You provide the known public URLs, which are guarded and opened in one isolated browser session.

  2. Compare the handoff honestly

    UTM and click-ID keys are compared before and after the boundary. The result explicitly states that referrer headers and provider-side session data need a test order to verify.

Common causes and fixes

A fixed checkout redirect
A provider or integration may construct a destination without forwarding the existing query string.
No supported cross-domain linker
The payment domain cannot read the source domain's cookie unless the integration passes a supported reference or metadata value.

Frequently asked questions

Will this place a test order?
No. It only opens the two public URLs you supplied and does not click, add to cart, authenticate, or pay.
Does URL continuity prove a payment is attributed?
No. Validate the provider webhook, order metadata, and purchase event in a safe test environment.

Make the handoff to payment measurable.

Clarvivo joins acquisition with payment truth even when customers move between domains and systems.

Connect campaigns to payment truth

What this tool reads, and what it keeps