Reusable editorial asset · N10026-009

Rehearse the creator's destination before traffic arrives

Follow one exact mobile path. The viewer's promised task, visible completion and event receipt are separate checks. Record what failed, who owns it and what would trigger a new rehearsal.

This page does not save or send entries. Copy your completed card into your own authorized record. The downloads are blank and fictional examples; they do not contain what you type here. A browser may retain local field values, so use only harmless test details on a shared device. The Morrow Pantry example below is entirely fictional, not a Superdirector signup test.

The five-step path

Creator CTA and exact link
Redirects and final URL
Offer and mobile task
Visible confirmation and promised result
Configured event receipt and decision

Test the intended market, language and offer version. A page view is not task completion. A configured analytics event is a separate observation. Performance diagnostics may help explain friction, but they do not replace the task check.

Blank rehearsal card

1. Freeze the promise and route

Creator CTA wording

Quote what the viewer is promised, including “free,” “book,” “buy” or “join” when used.

Exact tagged URL and creator surface

Copy the complete proposed URL and name profile, story, post or other surface.

Redirect hops, status and tag handling

Record first URL, every hop and where campaign values are captured or lost.

Final URL

2. Complete the viewer's task

Promised target task

Device, browser, viewport and locale

Product or offer version and availability

Form labels and error feedback

Try one harmless invalid value as well as the valid path.

Final confirmation and actual promised result

Name the file, booking, accepted request or order authority actually reached.

3. Retain the evidence and decision

Analytics event and test receipt

Name the property/source, event, test ID and timestamp. Keep tests out of campaign totals.

Performance diagnostic source and scope

If used, say mobile lab, page field or origin field; “not measured” is valid.

Tested-at timestamp and timezone

Result: send, repair/retest or delay

Destination and measurement owner

Retest trigger and remaining coverage limit

Fictional filled example: Morrow Pantry

Invented teaching case. The `.example` domain, F-MP-01/F-MP-02 receipts, event observations and outcomes below are fictional. No live Product or Superdirector destination was tested.

Creator CTA: “Download the free pantry restock planner.”
Exact tagged URL and surface: Fictional Instagram profile link: https://morrow-pantry.example/r/creator-a?utm_source=instagram&utm_medium=creator&utm_campaign=autumn-planner&utm_content=creator-a
Redirect hops: Both fictional passes open the staged creator profile link inside Instagram on a phone. No separate platform-wrapper URL is exposed in this imagined trace; the first observable destination is the exact tagged URL. An illustrative 302 then leads from /r/creator-a to /planner/v3; campaign values are retained in the final URL and fictional analytics record. A real rehearsal must record any wrapper address actually observed.
Final URL: https://morrow-pantry.example/planner/v3?utm_source=instagram&utm_medium=creator&utm_campaign=autumn-planner&utm_content=creator-a
Target task: Open the free planner PDF version 3 after the email form.
Device, browser and locale: Fictional 390-pixel Instagram in-app browser view on a phone; en-US; intended U.S. audience.
Offer version: Free pantry restock planner PDF v3; no account or payment promised.
Labels and error feedback: Visible “Email address” label. Invalid synthetic entry receives “Enter a valid email address.”
Confirmation and result: F-MP-01: delay. Submission ended at “Thanks” with no planner link or delivered file. F-MP-02: send exact staged profile link under checked conditions. Repaired confirmation named the planner, exposed a v3 PDF link, and the fictional tester opened the file.
Analytics receipt: Fictional GA4 DebugView showed generate_lead for F-MP-01 and planner_download for F-MP-02 on the synthetic device. These are imagined setup checks, not campaign results. No filter or report-exclusion rule is verified in this case; the measurement owner must verify exclusion before publishing a campaign total. An event alone is not proof of the file.
Performance diagnostic: Not run in this fictional case. No PageSpeed, field-data or speed claim.
Tested at: F-MP-01: 2026-10-28 10:05; F-MP-02: 2026-10-28 11:20; both America/Los_Angeles and entirely fictional.
Owner: Fictional destination owner repaired the confirmation/file route; fictional measurement owner checked the event receipts.
Retest trigger and limit: Repeat after any redirect, offer, form, file, analytics or creator-surface change. One imagined mobile path cannot establish behavior for all devices, locales or future viewers.