Identify the intended entry stage
Synthetic new visitor has no request identity. Page THANKS requires an existing completed request R-ID; page START accepts a new request entry. Draft campaign points THANKS. Local campaign is intended to invite new requests, not show a completion receipt.
| Destination | Required input | New visitor fit |
|---|---|---|
| THANKS | Completed R-ID | No |
| START | New-request entry | Yes |
Check destination prerequisites
- Read new-visitor stage
- Compare THANKS prerequisite
- Reject missing completed identity
- Map campaign to START
Do not invent a completed request ID merely to open the draft destination.
Which destination fits this campaign intent?
Show the worked answer
START. THANKS requires completed evidence the new visitor does not have.
Choose the supplied request entry
| Case | Decision or result | Reason |
|---|---|---|
| First visit→THANKS | Reject | Completion-stage prerequisite absent |
| First visit→START | Eligible entry | Matches new-request intent |
Keep entry stage beside each route in the landing manifest. A completion page can be valid for follow-up links while unsuitable for first-visit acquisition.