Chapter 2
Build an opt in page people can trust
trust-first opt-in page is the practical output of this chapter. Complete it in one focused work session so you can decide the promise, scope, fields, consent language, and proof needed for a clear value exchange, without trading email access through ambiguity or excessive form friction.
What you’ll get
- A completed trust-first opt-in page ready for the next chapter.
- A documented decision about the promise, scope, fields, consent language, and proof needed for a clear value exchange.
- A pass or fail signal: a visitor can explain what they receive, when it arrives, and what emails they agreed to.
- A first implementation move: Write the headline, three concrete outcomes, delivery expectation, privacy/consent statement, and one CTA before designing.
State the exchange plainly
The page should answer:
- What will I receive?
- What can I do with it?
- Who is it for—and not for?
- What format is it?
- What emails should I expect next?
- How will my information be handled?
Use a product preview instead of a decorative mockup alone. Show a real page, field, template section, or output—without giving away private customer data.
Separate delivery from marketing consent where required
Applicable privacy and marketing rules differ by location and business. Use clear, specific language; link the privacy notice; identify the sender; and provide a working way to unsubscribe from marketing. Do not use pre-checked consent or hide recurring communications behind “Get the download.” Obtain qualified legal advice for the jurisdictions you serve.
Apply this chapter to your store
Start with the live customer path, not a hypothetical version. Open the relevant content, profile, Tapmy page, email, or operational record and capture what a buyer sees now. Keep the scope to one campaign and one decision so the result can be measured.
Implementation move: Write the headline, three concrete outcomes, delivery expectation, privacy/consent statement, and one CTA before designing.
Connect the decision to evidence: customer language, transition counts, questions, observed behavior, or a completed end-to-end test. If another person cannot understand why you chose the action, add the missing evidence rather than more strategy language.
Decision checkpoint
| Check | Pass condition | If it fails |
|---|---|---|
| Scope | One buyer, one campaign, and one next action are named | Narrow the work before creating more assets |
| Evidence | The current state is visible in a live route or record | Capture the source, destination, and decision point |
| Decision | the promise, scope, fields, consent language, and proof needed for a clear value exchange is written clearly | Remove competing goals and choose one priority |
| Verification | a visitor can explain what they receive, when it arrives, and what emails they agreed to | Rework the weakest boundary, then retest it |
Common failure mode
Using a generic ‘join my newsletter’ form to distribute a task-specific resource. It creates activity without reliable learning. Use the chapter deliverable as a gate: the work is complete only when the decision is written, applied to the live path, and verified with the stated signal.
20-minute implementation sprint
- Open the live route or record and capture the starting state.
- Complete the smallest useful version of the trust-first opt-in page.
- Apply the decision to one campaign or Tapmy path.
- Test the pass signal from the buyer’s point of view.
- Save the evidence and the next review date.
