AdminConsole
Tutorials/Advanced
Advanced70 minDeep links

Operate deep links across every hand-off

Govern destination identity, universal-link association, privacy-safe attribution, fallback, expiry, and campaign retirement.

By the endA measurable zero-SDK journey that never confuses a click with arrival.
Real-world scenario

Build against an explicit contract

A multi-channel campaign must preserve one location intent through messaging clients, browsers, installed apps, stores, and privacy controls.

A Mappls developer projectA restricted Deep links applicationFixture data with no production credentialsA request, aggregate, or correlation ID strategy
Step 1

Define the user and system contract

A multi-channel campaign must preserve one location intent through messaging clients, browsers, installed apps, stores, and privacy controls. Record the region, data freshness, latency budget, privacy purpose, credential owner, and fallback before choosing an SDK or endpoint.

Step 2

Sign the destination contract

Allow-list documented place, route, or navigation shapes; bind a stable Mappls Pin or validated coordinate, campaign revision, expiry, and non-sensitive attribution fields.

App Widgets & Deep Links · SDK or product slice
<a
  href="https://mappls.com/MMI000"
  target="_blank"
  rel="noopener noreferrer"
>
  Open this place in Mappls
</a>
Step 3

Operate association and fallback

Monitor Android App Links and iOS Universal Links, prevent redirect loops, retain browser and store choices, and give users a visible copy/open destination.

Step 4

Measure only observable stages

Separate impression, click, resolver decision, app hand-off, and application acknowledgement; minimize attribution, expire campaigns, and retire destinations without rewriting history.

Step 5

Prove the production behavior

Automate the happy path and every named failure. The release is ready only when every device class reaches a useful destination; link rewriting cannot change the target origin; analytics make no unproved arrival claim; expired campaigns fail safely. Capture provider request identity without logging credentials or unnecessary precise location.

Recovery design

Failure modes you must exercise

association file is stale or unavailable

Fail fast with a typed, user-safe outcome and preserve the original request identity.

messaging client strips parameters

Keep the last verified state, mark freshness honestly, and retry only within the documented idempotency boundary.

app opens but does not acknowledge the intended destination

Reconcile durable local and provider evidence before declaring success or issuing a compensating command.

Never turn uncertainty into success

Timeout after a stateful command is an unknown outcome. Query by provider/idempotency identity or wait for authoritative events; do not blindly retry a new command.

Acceptance criteria

Definition of done

every device class reaches a useful destinationlink rewriting cannot change the target originanalytics make no unproved arrival claimexpired campaigns fail safely

Deep links production checks

User or confidential data never appears in query parametersAll variable values are encoded and length-boundedApp and browser fallbacks reach the same intentRedirect and campaign domains are allow-listed and monitored
Grounded implementation

Continue from source, contracts, and a full app

These links resolve to repository-derived evidence; unsupported package names and endpoints are not filled in from guesswork.

Study the complete Coordinated incident response state machine
Tutorial complete

Run it, break it, then observe it

Start with fixture credentials, execute the failure plan, and use request logs, usage, webhook evidence, and operational metrics before promoting traffic.