Platform / Match / Needs-review queue
We never guess who paid.
Every payment we can't match with certainty is listed with the reason. Nothing unclear reaches a campaign's numbers until you decide.
| Payer | Amount | Why it is kept apart | |
|---|---|---|---|
| CPChris Park | $1,200 | No lead with this phone or email | |
| DWDana White | $900 | Paid before any of this person's leads | |
| R1Row 14 · •••0177 | $2,400 | Same person, day and amount in another file | Keep apart |
| R7Row 7 · •••0199 | $1,050 | Phone and email point to two people | Keep apart |
| R3Row 31 · •••0412 | $900 | Amount unreadable |
How it works
Step by step.
What you actually get
Needs-review queue, in detail.
No lead yet
A payer with no matching lead is counted as cash — but for no campaign.
Paid before any lead
Usually a wrong match; shown instead of assigned.
Possible duplicate
Same person, day and amount already uploaded from another file.
Two people
Phone points to one person, email to another.
One click to close
Keep apart and the row leaves the queue. A corrected re-upload closes rows that carry an ID.
Nothing raw kept
Rows are kept by number and a masked contact, not the file itself.
Works with
Connect what you already use.
Meta, your website and a CSV from any CRM today. Direct CRM and payment connections are next.
Do unclear payments disappear?
No. Cash still counts as collected; it just isn't credited to any campaign.
How do I fix one?
Correct the row and upload the file again. Rows with an ID close by themselves; others you keep apart.
Why not just guess?
A guess that's wrong moves money between campaigns and teaches Meta the wrong thing.
We never guess who paid
on your own data.
Book a 30-minute call — we set it up with you live.
Book demo