Every link finds its exact destination.

The missing layer between user intent and the experiences brands promise.

Talk to the team See how resolution works

The user clicked. The company made a promise. The journey broke.

Someone taps a link to one specific thing — a product, a playlist, a checkout that is already half finished. The app isn't installed yet, so the phone sends them to the store. They wait. They install. They open. And they land on a home screen that has never heard of them.

01
Intent
A person decides where they want to go.
02
Handoff
The phone passes them to the store. The destination has nowhere to live.
03
Silence
Minutes pass. The click and the open are now strangers.
04
Nothing
A generic home screen. The promise is gone, and so is the attribution.

the breakThe operating system has nowhere to put the destination while the app does not exist. Everything after this point is a guess — unless something recorded the click.

Nobody involved did anything wrong. The platforms simply have nowhere to keep a destination while an app is being installed.

Something has to carry the destination across.

Optolink holds the intent from the moment of the click, and hands it back the instant the app opens — however many minutes, screens and store pages happened in between. When it cannot be certain, it says so rather than guessing quietly.

A token the phone carries

exact confidence

A one-time token written on a real tap and read on first launch. Not an inference — this is the same journey, and we can prove it.

The store's own receipt

high confidence

On Android, Google Play carries the referrer through the install. Signed by the store rather than reconstructed by us.

The device, exactly as it was

high confidence

Model, OS build, screen, locale, timezone and network all agree between the click and the open.

The device, mostly as it was

medium confidence

They changed networks, or updated the OS while they waited. What still matches is weighed rather than thrown away.

The last thing we know

low confidence

A network-level match. It is a guess, it is labelled as a guess, and it still beats a home screen.

Every resolution arrives with its own confidence attached. You are never told a match happened without being told how much to trust it.

A journey can start anywhere. It should end in the same place.

Five ways in. One destination each — the exact screen the link named, and the method that got it there.

Campaign · resolving

A paid click lands on a domain that carries your name. The destination survives the store, and the install is credited to the work that earned it.

The install carries the referrer through the store itself. Signed by Google Play, not inferred by us.

method: Play Install Referrer
confidence: high

Three promises, kept.

The destination survives the install

The gap between a click and a first launch is the one place the operating systems cannot help you. Closing it honestly is the entire product.

A route always resolves

When the preferred path is unavailable, the journey still ends somewhere deliberate — the store, the web page, the sensible second choice. Never a blank screen.

You can prove what happened

Routing and attribution are the same record, written once. The link that earned the install is a fact you can query, not a model you have to believe.

The parts you only notice when they're missing.

Deep linking is easy to demonstrate and hard to operate. These decide whether it survives a real customer, a real security review, and a real Monday morning.

Your domain, your certificate

Point a CNAME and Optolink provisions and renews the certificate. The links people click carry your name, not a shortener's.

Platform manifests, generated

Apple's and Android's association files are produced from your app configuration and served on your domain. One less file for someone to forget to redeploy.

Scoped from the schema up

Every link, domain, key and match belongs to an organisation. Two customers can both own /summer and never collide.

Keys you can take back

Stored hashed, listed by prefix, revoked individually. A leaked key is a rotation, not an incident.

A log that cannot be edited

Immutability enforced by the database, not by convention. It survives a compromised application server, which is the only time anyone reads it.

Limits where they matter

The endpoint that resolves identity is rate-limited at the edge. That is the one worth protecting, so it is the one protected.

Know which link earned it — and how sure the system is.

An attribution number that arrives without its method invites you to assume it is exact. Optolink records how each match was made and how sure it is, so you can tell a deterministic install from a network-level guess. That distinction is the difference between reporting a result and defending one.

Source
The link, the campaign, the code, the message.
Click
Captured with what the device offered at that moment.
Match
One method answers. Its confidence travels with it.
Outcome
The install, tied back to the thing that caused it.

Initialise once. Listen to one stream.

Direct opens and recovered journeys arrive through the same handler, carrying the same shape. There is very little surface area here, which is the point — the complexity belongs on our side of the boundary.

iOS 13+ in pure Dart. Android from API 21, with a small Kotlin plugin for the store referrer.
Every event says where it came from and how certain it is.
Turn off the clipboard method in one line if your team won't ship the iOS paste banner. The rest of the chain carries on.
Native iOS, Android and React Native are on the roadmap. Flutter covers the same ground today.

Read the integration guide

main.dartflutter sdk

// main.dart — before runApp()
await OptoLink.initialize(
  OptoLinkConfig(
    apiKey: 'ol_live_…',
    orgKey: 'acme',
    clipboardEnabled: true, // false skips the iOS 16+ paste banner
  ),
);

// One stream. Direct opens and deferred installs arrive the same way.
OptoLink.instance.onLink.listen((OptoLinkData link) {
  if (link.confidence == 'exact') {
    grantReferralCredit(link.params['ref']);
  }
  router.go(link.path, extra: link.params);
});

Infrastructure is judged at street level. One person. One device.

We never stop your traffic to make a point.

Cross a limit on any paid plan and eligible links keep resolving. If your accepted checkout or order includes overage, those terms apply on the invoice rather than interrupting users. The billing model is designed around continuity rather than an upgrade wall.

Talk to the team See plans

Starter
Free
free, every month
Growth
EGP 2,450
per month
Scale
EGP 7,500
per month

Frequently asked

For users who already have your app installed, it isn't — Optolink lets the platform handle that path directly and adds nothing to it. The difference is the user who doesn't have the app yet. iOS and Android have no mechanism to carry a destination through an App Store install, so the payload is lost. Recovering it is the entire job of the deferred matching chain.