The call to action described in the registration must exist on the site
The requirementstatement
Where consent is collected on the site, the call to action the registration describes must be findable on the crawled site.
- 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
- live site vs campaign.message_flow
- Where it liveslayer
- WebsiteWEBSITE
- How Ekas settles itdetectability
- AI · crawlCRAWL
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
- What the fix involvesfailureClass
- Fix the websiteTERMINAL_WEBSITE
- The fix lives on your site. No amount of rewording the form clears it.
- Who requires itauthorities
- TwilioZoom
- When it appliesapplicabilityText
- Applies when consent was collected by web form, checkout and QR code.
Why this rule existsrationale
A described opt-in that cannot be found reads to a reviewer as consent that does not exist, which is the strongest possible reason to refuse a campaign — and it is usually true by accident: the page moved in a redesign, the form sits behind an interaction the crawler never triggers, or the description was written from the plan rather than from the site. The consumer-side stake is the same one: an opt-in nobody can locate is one nobody can audit.
How to fix itremediation
Give the exact URL of the page holding the consent control in the message flow, and confirm the control is present in the page source rather than injected after an interaction. Done when opening that URL in a private window shows the opt-in without clicking anything.
Common mistakespitfalls
- A consent box that only appears after a product is added to the cart is invisible to a crawler that never adds one. Supply a screenshot of the checkout step as well, or the reviewer sees a page with no opt-in on it.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twiliogen1 | 30891 | Yes |
Notesnotes
The twin of WEB-069, which audits the described and live opt-ins as two passes. This rule is the narrower question underneath it: does the described surface exist at all.
Rules you will hit next
Other website rules at the same severity. A registration is judged as a whole, not rule by rule.
WEB-001A brand website URL is requiredBlockingBLOCKINGWEB-009The website must resolve and return contentBlockingBLOCKINGWEB-012A parked or for-sale domain is not a websiteBlockingBLOCKINGWEB-013A pre-launch placeholder is not a websiteBlockingBLOCKINGWEB-014Staging, admin and internal hosts must not be the brand websiteBlockingBLOCKINGWEB-016The website must be machine-crawlableBlockingBLOCKING
WEB-070 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.