The short answerApp deep-link QA checks whether a campaign reaches the intended supported destination in each relevant user state. An existing logged-in user and a new installer can follow different paths. A link opening the app is not proof that it completed the promised journey.

Define the intended destination

Write the task, app screen and prerequisites. Specify what should happen when the user is not logged in, lacks access or has not installed the app. A feature unavailable to the customer needs an honest fallback, not an error or misleading purchase prompt.

Platform linking behavior depends on supported configuration. Android documents App Links and their verification requirements. Check the implementation's current guidance rather than assuming any web URL will automatically route into every app state.

Build a state matrix

StateExpected check
Installed and eligibleCorrect task destination
Installed but logged outAppropriate authentication and return path
Not installedSupported store or web fallback
Content unavailableClear alternative or explanation
Access restrictedAccurate conditions, not a false promise
Link modified in transitCampaign and destination parameters remain valid

Test actual supported devices and versions where possible. Do not claim deferred routing survives installation unless that path is implemented and verified.

Worked example: the campaign task disappears after login

Illustrative example: a reporting campaign links to a shared report, but logged-out users land on the home screen after authentication. The app opened successfully while the promise failed. The QA record should verify continuation to the intended report or a clear supported next step.

Also inspect tracking. Link opens, installs, logins and useful task completion are different events. A campaign report should not merge them into one outcome.

Keep the test record with the campaign

Record the URL, destination, user state and observed result. Repeat the relevant checks after release or routing changes. If behavior was not tested, state that internally rather than describing the link as verified.

Use the data contract guide to define events and the custom product page guide for store-to-app continuity.

Primary-source context: Android Developers: App Links. Checked 2026-10-13.

Ayoub Mouhachtt
Growth & performance marketing. Explore my working background.

An AI-assisted educational guide commissioned for Ayoub’s Growth Notebook. Worked examples are illustrative; they are separate from the portfolio’s client evidence. How these guides are prepared.