Deep-link pipeline
The customer-visible lifecycle from a public link click to an app route, store destination, or web fallback.
Resolution lifecycle#
- 1
Accept
LocusVia normalizes the host and path and identifies the matching tenant and environment. - 2
Authorize context
The resolver rejects disabled, expired, or scope-mismatched configuration. - 3
Choose destination
Platform, device, policy, and experiment rules select an eligible destination. - 4
Respond and observe
The resolver returns the redirect and records privacy-safe journey diagnostics.
Destination priority#
Verified app routes take priority when the device and link configuration allow them. Otherwise the resolver selects the configured store destination or web fallback. A link without an eligible destination fails closed.
Context continuity#
Approved campaign and journey context can be carried into the app without placing personal data in the public URL. Context is bounded, signed where required, and scoped to the originating tenant and environment.
Note
Use Journey Flight Recorder to inspect the decision path for a specific click.