How matching works
The channel and campaign are always exact. Tying a purchase back to the exact click is the interesting part — and every match comes with a confidence.
Why naïve matching fails
Between the web click and the app there is no shared cookie. The lazy approach — credit the most recent click from the same IP — is wrong more often than you'd think: an entire household shares one WiFi address, and an entire mobile network can share one. That's how cheaper trackers quietly credit the wrong campaign.
Signal-based matching
MakeRVN compares a set of privacy-safe device and network signals from the click against the install, and picks the best match — not just the most recent one. When you add the first-launch snippet, the exact click is carried straight through and matching becomes deterministic: there's nothing left to infer.
Confidence, on every match
Every attributed conversion carries a confidence tier, shown right next to it in your dashboard — a transparency most trackers hide:
| Confidence | What it means |
|---|---|
| Deterministic | The exact click was carried through to the purchase — a guaranteed match. |
| Strong | Multiple independent signals point clearly to one click. |
| Probable | The signals agree, with a little ambiguity. |
| Weak | Only a loose match was possible — shown for context. |
| Organic | No click could be confidently tied to this user. |
Want every match to be exact?