By Tangenix · Published 2026-10-24 · Free template

Custom Product Page Deep Link Journey QA

Verify the journey from an Apple custom product page into the promised app destination, including installation, sign-in and unsupported device conditions.

Read this resource as Markdown

When to use this template

Use this after a custom product page and its deep link have been prepared for a real iPhone or iPad app. It records observed routing and access-state behavior separately from the creative promise.

Choose another approach when: You only need a screenshot storyboard, have no implemented destination, or intend to mark an untested device and account combination as working.

Gather these inputs

The actual custom product page URL, reviewed deep link and intended in-app destination.
Test devices, OS versions, installed app builds and relevant access states.
The promise made before the store visit and the minimum actions needed to fulfill it.

Copy and adapt the template

Edit the text below and copy it into your own document. Edits stay in this browser field and are not submitted or saved by this page.

Custom Product Page Deep Link Journey QA: editable text

Worked example

Illustrative example, not a Crany customer result. Replace every example detail with facts you can verify.

Fictional example: a scanning app's custom page promises that returning users can open the receipt workflow. A test on a supported OS reaches the scan screen for a signed-in account, but a signed-out account lands on a generic home screen after authentication.
The worksheet records that mismatch and assigns the return destination for correction. It does not mark sign-in itself as a defect or remove the requirement from the marketing promise.
The fresh-install journey and an older device are listed separately. The older system is outside Apple's documented custom-page deep-link support, while an untested fresh installation remains unknown. The team cannot claim all visitors complete the intended journey merely because one installed-app case worked.

How to use it

Translate the incoming promise into an observable destination and completed task.
Exercise the actual custom-page route across the listed device and access conditions.
Fix mismatches and retest the affected cases before broadening the public claim.

Check before using it

Observed behavior includes OS, app build and account state.
Installation, authentication and destination fulfillment are separate checkpoints.
Unsupported and untested cases are not silently counted as successful.

What to measure

Count completed journey cases and unresolved mismatches within the explicit matrix. Compare the actual destination with the promise rather than optimizing only link-opening success. This is journey verification, not an attribution system or a conversion experiment.

Research and sources

Apple specifies OS support for custom-page deep links and requires the page and associated metadata to be reviewed. The state matrix and acceptance process are original editorial tools; no reader’s app or device has been tested here.

Apple: Custom Product Pages — checked 2026-10-24. Audience-specific product-page variants and shareable URLs; metadata is subject to review.
Apple: Submit a custom product page — checked 2026-10-24. Custom-page and deep-link review; first-version submission dependency and edit restrictions while under review. No guaranteed approval duration.

This original template and worked example were prepared with AI assistance. Source documentation supports the principles stated above; it does not endorse Crany or guarantee this template’s performance.

About Crany

Crany is an AI marketing co-founder in development for software founders and vibe coders, designed to strategize, execute approved marketing and improve based on results. This free resource is usable independently of the product. Join the public waitlist.