AdminConsole
Tutorials/Beginner
Beginner15 minDeep links

Create a zero-SDK location campaign

Build safe place links, add fallback behavior, instrument hand-offs, and test every device.

By the endA campaign that opens a useful Mappls experience everywhere.
Real-world scenario

Build against an explicit contract

A campaign must open one useful place experience from email, QR, social, and web without requiring an SDK or assuming the Mappls app is installed.

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 campaign must open one useful place experience from email, QR, social, and web without requiring an SDK or assuming the Mappls app is installed. Record the region, data freshness, latency budget, privacy purpose, credential owner, and fallback before choosing an SDK or endpoint.

Step 2

Build from stable location identity

Use a documented place or navigation link, encode each parameter once, allow-list campaign metadata, and never embed credentials.

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

Design the fallback chain

Test installed-app, universal/app-link, mobile browser, desktop browser, and store outcomes while preserving only non-sensitive campaign context.

Step 4

Measure the hand-off honestly

Record click and fallback class on your domain, avoid claiming downstream arrival without evidence, and keep a visible copy/open alternative.

Step 5

Prove the production behavior

Automate the happy path and every named failure. The release is ready only when every target device reaches a useful destination; malformed input cannot change the target origin; analytics contain no precise user location. Capture provider request identity without logging credentials or unnecessary precise location.

Recovery design

Failure modes you must exercise

app not installed

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

link association misconfigured

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

messaging client strips or rewrites parameters

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 target device reaches a useful destinationmalformed input cannot change the target originanalytics contain no precise user location

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 Application-owned widget selection 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.