Knowing which partner earned the install.

The shape of it

Each partner gets their own link, or their own parameter on a shared one. When somebody taps it, that identifier travels with them: into the app if they have it, and through the install if they do not. Your code receives it on first launch and can credit the partner without asking the person to type a code.

Any parameter you put on a link comes back to you. A partner identifier, a campaign, a placement — we carry what you set rather than imposing a schema, because an affiliate programme’s vocabulary is its own.

The part that decides whether this works

A tap that leads straight into an installed app is certain: the link survived the whole way and there is nothing to infer.

A tap that leads to a store, an install, and a first launch is not. The link cannot cross that boundary on iOS, so the install has to be matched to the click after the fact. How well that works is published, including the case where it does badly — a busy shared network, where several people look alike to any matching method.

This is the number to interrogate before choosing anybody, including us. A programme paying real money on attributed installs is exactly where an inflated match rate stops being a marketing exaggeration and starts being a wrong payment.

Why the confidence is on every row

An attributed install is not one thing. Some matches are certain; some are inferred from coarse signals and could be somebody else. A report that shows both as “attributed” is hiding the distinction your finance process needs.

So every attribution carries a confidence band, in the report and in the live view, and the installs we could not match to any link are shown beside the ones we could rather than left out of the total. You can pay on certain matches only, or pay on all of them knowingly. What you cannot do is be told everything was explained when it was not.

Where we stop

We do not calculate commission, run a partner portal or move money. We tell you which link produced which install and how sure we are; what a partner is owed is your system’s decision, reached through the API or the webhooks.

Webhooks are the usual route — an attributed install arrives as it happens, and the event that carries a purchase value carries the link that earned it.