A web opt-in must supply the form itself, not just describe it
The requirementstatement
A web-form or checkout opt-in must supply the link to the opt-in page, or a screenshot of the form.
- Severityseverity
- BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- campaign.message_flow + opt-in evidence
- Where it liveslayer
- CampaignCAMPAIGN
- How Ekas settles itdetectability
- DeterministicDETERMINISTIC
- Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
- What the fix involvesfailureClass
- Supply evidenceTERMINAL_EVIDENCE
- Needs proof only you hold: a screenshot, a recording, a scan of the form people signed.
- Who requires itauthorities
- BandwidthTwilio
- When it appliesapplicabilityText
- Applies when consent was collected by web form and checkout.
Why this rule existsrationale
A reviewer confirms a web opt-in by looking at it, and a description with nothing to look at is an assertion rather than evidence. This is the most common shape of an incomplete submission because the flow text reads as complete — every element is described, and there is simply no way to check that any of it is on the page.
How to fix itremediation
Put the deep link to the page carrying the consent control in the message flow, and attach a screenshot of that control taken on a fresh page load. Done when someone with no account can open the link and see the box you described.
Common mistakespitfalls
- A link to the homepage is not a link to the opt-in form. If the control is three clicks in, the screenshot is doing the work and the link is not enough on its own.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twilio | 30896 | Yes |
Rules you will hit next
Other campaign rules at the same severity. A registration is judged as a whole, not rule by rule.
CMP-003Message flow must not begin or end with whitespaceBlockingBLOCKINGCMP-017Every mandatory campaign attribute must be explicitly setBlockingBLOCKINGCMP-024Registration fields must be written in EnglishBlockingBLOCKINGCMP-028Opt-in evidence must be a JPG, PNG or PDF under 500 KBBlockingBLOCKINGCMP-035The description must describe this programme, not messaging in generalBlockingBLOCKINGCMP-037The description must name the business that sends the messagesBlockingBLOCKING
CMP-095 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.