One routing decision, made with everything known about the user.
How a click becomes a destination — including when the app that should receive it does not exist yet.
The link
A link is a routing intention, not a URL
Every Optolink link carries a path, parameters, a fallback, a deferred flag, a match window, and its own Open Graph card. Routing and attribution both read from that one object, which is why the two can never disagree about what was promised.
The decision
The redirect is not a bounce. It is a decision.
In the moment that looks like an instant hop, the page reads the device, decides whether your app can be opened directly, writes a clipboard token on a genuine user gesture where that method is enabled, and hands off to the store or the web. It runs on your domain under your certificate, so nothing in the chain looks like a shortener.
The match
Both sides of the boundary run the same code
Clipboard, install referrer, exact fingerprint, weighted fingerprint, IP fuzzy — the same priority chain is implemented in the backend and in the SDK, with the same confidence vocabulary on each. When the client and the server describe a match, they are describing it in identical terms, which is what makes the confidence value a measurement rather than a decoration.
The record
Every attempt is written down. Including the ones that failed.
Match attempts are recorded whether or not they succeed, with the method and the confidence attached to each. That record is the whole difference between a number you report and a number you can defend.
Every link finds its exact destination.
Bring us the journey that keeps breaking — the campaign that can't prove its installs, the printed code that lands on a home screen, the checkout link that only works for people who already have the app.
Optolink is built and operated by Optomatica