How verified conversions work

Ad platforms grade their own homework: the pixel reports a conversion, the bidding algorithm optimizes toward it, and the dashboard says everything's working. PilotPM checks those claims against your own data — that's the core of the Ads app.

The three sources of truth

Each connected account verifies against one of:

• Support inbox. PilotPM counts real leads that arrived in your inbox — for example, actual demo-request emails — and compares them with what the platform reported for the same period.
• Data warehouse. A read-only count from your own warehouse (signups, purchases — whatever your business counts as a conversion).
• Product events. Trial starts or signups your app sends to PilotPM. For mobile apps this is the ground truth Apple's attribution can't see: "the platform reports 45 installs — your app saw 12 trial starts."

What the cards look like

When claims and reality diverge, you get a reconciliation card, for example:

Ads reports 13 conversions in the last 30 days — your inbox confirms 0 matching leads.

That usually means the conversion action is firing on the wrong thing (a click, a page view) and the platform is optimizing toward noise. The card links the evidence on both sides.

When your data stream isn't connected yet

If your chosen product event has never been received, PilotPM treats it as "not connected yet" — you'll see that state on the account rather than a false "your data confirms zero" accusation. A configured-but-silent pipeline is a setup issue, not proof your ads don't work.

What to do with a mismatch

1. Check what the conversion action actually fires on (the card names it).
2. Fix or replace the broken action in the ad platform.
3. Keep the card open until the next nightly read confirms claims and reality agree — it re-checks automatically.