Skip to content

Documentation

Deferred Link Resolution

Deliver click-time context to users who install after clicking a link.

How it works

text
User clicks link (before app is installed)
  -> OS cannot open app -> request reaches LocusVia
  -> Worker creates Click Context with route payload snapshot
  -> User installs app from store
  -> SDK first launch calls /api/v1/sdk/deferred-link/resolve
  -> Backend finds matching Click Context
  -> Returns click-time route payload
  -> App opens to the intended screen

Match types

  • Deterministic — default. Uses device ID or install referrer token for exact matching.
  • Probabilistic — tenant opt-in. Uses coarse device context with confidence scoring.
  • None — no match found. Returns processed: true, link: null.
No match is a processed result, not an error. The SDK must handle link: null gracefully.

Rules

  • Deferred resolution is single-shot / first-launch behavior.
  • A disabled Link suppresses pending Deferred Links, even if a Click Context exists.
  • Editing a Link Target affects future Click Contexts only; existing snapshots remain valid.
  • Click Contexts expire aggressively (configurable TTL).