Building CPA.express: proof-first tracking for people running paid traffic. Join beta waitlist
When numbers don’t match, you need proof — not guesses.
CPA.express is built for affiliates and media buyers who ship changes while traffic is live. It helps you see what broke, where it broke, and why — so you can fix it or roll back fast.
Conversion proof: raw postback + match result + reason codes
Send-back log: what we posted back to the source (sent / failed / throttled)
Versioned publishes: compare before/after and roll back without rebuilding everything
We won’t promise 100% match between platforms. We will show the raw events and reason codes so you can tell “model difference” from “something broke.”
Screenshot placeholder
Conversion proof + send-back log + version history
UI screenshot coming later (beta waitlist is open now)
Built for people running paid traffic (not beginners)
Fast drilldowns, no spreadsheet archaeology
Versioned publishes + rollback (safe changes)
Privacy-first: your data stays yours
Why this exists
The real killer isn’t “a bad report”. It’s shipping changes and going blind.
When your numbers look weird, you need to answer: did my change break tracking, did my postback fail, did click IDs get lost, or is it just attribution windows?
What this feels like
“I changed the lander / offer routing and EPC dropped. I can’t prove what caused it.”
“Clicks are there, conversions are missing. Debugging postbacks again.”
“Meta/Google/GA4 don’t match and I don’t know what part is model vs broken.”
MVP outcome
Show the raw conversion event + match result (or why it didn’t match)
Show what you sent back to the source (and what you intentionally didn’t)
Version every publish so you can compare and roll back fast
Run pre-flight checks before you burn spend
What you get in MVP
Proof-first tracking + safe changes
MVP is about trust and control: conversion proof, send-back logging (with throttling), version history + rollback, and health checks.
Conversion proof log
Raw postback + parsed fields + match result. If it didn’t match, you’ll see why.
Send-back log (postbacks to source)
Sent / failed / retried / throttled — with response codes and timestamps.
Versioned publishes + rollback
Every publish is a version. Compare before/after and roll back without panic.
How it works
A simple workflow that matches how you actually operate
1) Track the chain
Click → redirect hops → conversion. Nothing disappears silently.
2) Prove what happened
Raw events + reason codes. Match or “orphan” with a clear explanation.
3) Close the feedback loop
See what you sent back to the source (and what you throttled on purpose).
4) Ship changes safely
Publish versions, compare before/after, roll back when needed.
Screenshot placeholder
Proof log drilldown (raw payload + match reason)
UI screenshot coming later (beta waitlist is open now)
Screenshot placeholder
Version history + before/after + rollback
UI screenshot coming later (beta waitlist is open now)
Fit
Who this is for (and who it isn’t)
If you’ve ever lost a day because a small change broke tracking, you’re the person we’re building for.
Perfect for you if…
You run paid traffic and care about debugging and proof.
You ship changes weekly/daily and want a safe rollback path.
You send conversions back to sources and want proof when they “miss” them.
You’re tired of cross-checking dashboards to make one decision.
Probably not for you if…
— You want the cheapest tracker possible.
— You expect perfect 100% matching across platforms.
— You’re still learning basics (postbacks, click IDs, macros).
Beta waitlist
Join the beta waitlist (and steer the MVP)
If you run paid traffic and you’ve ever lost a day to missing conversions or broken postbacks, I’d like your input. This MVP is about proof, debugging, and safe changes — not shiny features.
Invite-only private beta — invites go out when it’s stable enough for real traffic
No spam. One email when invites open for your use case
Short survey helps prioritize the MVP (optional)
FAQ
Quick answers
No. But it will show you what is model/window differences vs what actually broke (missing params, failed postbacks, lost click IDs, etc.).
Yes. You can set a send-back rate per source, and the send-back log will show what was throttled and why.
No. If you’re still learning basics, you’ll probably hate it. This is for people who want proof, debugging, and safe changes.
Later. MVP is about trust and control first.
Want a beta invite when it’s ready for real traffic?