Postclick Preflight

Prove your conversion signal survives — before the spend goes live.

Run one controlled conversion through your real landing page and form. Postclick Preflight follows it hop by hop — browser, server, destination, deduplication — and shows exactly where proof stops. Before your budget finds out for you.

Free · no signup · checks only what's publicly observable

See a completed launch record →

Conversion signal chain

One controlled conversion, followed hop by hop. Each hop stands only on its own evidence.

Browser/server deduplication

Deduplication not provenNot proven

Browser/server deduplication — not proven. A browser Meta Pixel "Lead" event was observed directly, and your pipeline reported Meta CAPI acceptance for a "Lead" event with the same observed platform event ID. No receipt states these were deduplicated.

Fix this hop
Meta
No deduplication statement supplied
Run b7f3d2a1-4c5e-4f6a-9b8c-1d2e3f4a5b6cVerifiedStopping hop: Browser/server deduplicationExpires Jul 10, 2026 · 17:05 UTC

The output is a launch record — a verdict, and the exact hop to fix.

Not a score. Not a tag audit. A decision — Ready for spend, Ready with warnings, or Not ready — scoped to the evidence that actually exists, with the failed hop named and the fix spelled out.

Launch record

Server delivery proof — correlated destination evidence

Ready with warnings

Your customer pipeline reported acceptance for every required destination, but did not supply browser/server deduplication evidence for all of them.

Proof stops at: Browser/server deduplication

Next action

Configure event_id deduplication between the Meta browser Pixel and the CAPI event, have your pipeline report "deduplicated": true on its receipt, then run one new controlled conversion.

https://trialflow.example/get-started?utm_source=meta&utm_medium=paid-social&utm_campaign=q3-trialScanned Jul 8, 2026 · 17:02 UTC
See the full sample report →

Three steps. Each one earns its evidence.

  1. Quick scan

    Point it at your live campaign URL. See what's publicly observable: tags, campaign context, form handoff, obvious blockers.

    Observed directly

  2. Controlled conversion

    Authorize one test lead through your real form. Watch the browser evidence land: pixels fired, event IDs carried, cookies survived.

    Observed directly

  3. Server delivery proof

    Your pipeline posts one receipt per hop. Postclick correlates it with the observed browser event and tells you exactly where the chain holds — and where it doesn't.

    Reported by your pipeline

What this tool refuses to claim.

  • Configuration is not delivery.
  • Correlation is not acceptance.
  • Acceptance is not deduplication.
  • Customer-pipeline receipts are labeled as customer-reported.
  • Connected CRM and analytics reads are supporting evidence.
  • Cannot verify is an honest result.

Connected CRM and analytics reads support record and configuration questions. They never replace the controlled conversion or your pipeline's receipts.

Settle the argument before the campaign starts.

When conversions go missing, marketing blames the pixel, engineering blames the platform, and the budget keeps spending. A launch record ends the argument: every hop carries its evidence and its source — what Postclick observed, what your pipeline reported, what a connected system says on record.

Observed directly
Postclick's own browser saw it.
Reported by your pipeline
Your pipeline's own statement, not independently confirmed with the destination.
Connected read
A read-only record from a connected system.

Run the preflight before the campaign does it for you.

See a completed launch record