Clarvivo

Free tool by Clarvivo · no login

Check the browser half of Reddit Pixel and CAPI deduplication

Inspect a public conversion page for the stable browser conversion ID that CAPI must share; server requests remain explicitly out of scope.

Public conversion page

Inspect a public Reddit browser conversion for a stable conversion ID. We clearly distinguish browser evidence from CAPI requests, which never pass through a browser.

This tool answers: Does the Reddit browser conversion expose the ID needed to deduplicate with CAPI?

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

Why this happens

Running the Reddit Pixel and the Reddit Conversions API together gives better coverage than either alone, but only if Reddit can tell when both sent the same conversion. That depends on a shared conversion ID. Without it, one purchase becomes two.

The server side is invisible from the browser, so most teams can't easily check whether their browser events carry an ID at all. If the Pixel event has no conversion ID, deduplication can't work, whatever the server sends.

This checker looks at the browser half of that pair: it loads your conversion page and checks whether the Reddit conversion event exposes a stable ID. It's explicit that the server half can't be observed.

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. We load your conversion page

    The public page is opened in an isolated browser and Reddit Pixel requests are recorded.

  2. We look for a conversion event and its ID

    We check whether a conversion event fired and whether it carried a conversion ID that a matching CAPI event could reference.

  3. We report the CAPI limit plainly

    Conversions API requests go from your server to Reddit and never pass through the scanned browser. The result says so rather than guessing.

Common causes and fixes

No conversion ID on the Pixel event
Add a conversion ID (for example the order number) to the Pixel conversion event.
CAPI and Pixel use different IDs
Both sides must send the same ID for the same action. Generate it once and pass it to both.
Pixel conversion doesn't fire
If there's no browser conversion, there's nothing to deduplicate; CAPI alone will report the conversion.
Random IDs generated per request
IDs regenerated on each page load don't match the server's ID. Use a stable business identifier.

Frequently asked questions

Can this tool see my Reddit CAPI events?
No. Server-side requests never pass through the browser, so only the Pixel half can be checked.
What should the conversion ID be?
A stable identifier for the action, such as the order or lead ID, sent identically from the browser and the server.
Do I need both Pixel and CAPI?
Running both improves coverage when browsers block the Pixel. It requires deduplication to avoid double counting.
What if no conversion event fires?
Test the page reached after a completed purchase or lead.
Is anything submitted?
No. The check only loads the page and records the browser requests it makes.

Remove inflated claims before changing paid-social spend.

Clarvivo keeps platform claims beside revenue truth.

Reconcile Reddit with revenue

What this tool reads, and what it keeps