The opt-in URL must land on a page that carries the opt-in
The requirementstatement
The page at the submitted opt-in URL must contain the opt-in form itself, not merely mention or link to it.
- 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
- opt-in page DOM
- Where it liveslayer
- Consent flowCONSENT_FLOW
- 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 fieldRETRY_FIELD
- A better value in the form fixes it. Ekas can rewrite it and re-check.
- Who requires itauthorities
- AWSBandwidth
- When it appliesapplicabilityText
- Applies when consent was collected by web form, checkout, account settings, QR code and third party.
Why this rule existsrationale
A reviewer opens the URL and expects to see the thing being registered. Landing on a homepage, a marketing page, or a page whose signup lives one click further in reads as evidence that could not be produced, and it is rejected without anyone hunting for the real page. Brands submit the wrong URL constantly because the opt-in is a modal or a footer widget and the page they think of as "the signup page" is the one that advertises it.
How to fix itremediation
Submit the URL of the page the form is actually on, opening the modal first if that is where it lives and using the deep link if one exists. Done when loading that URL in a fresh browser shows the phone field and the consent control without any further clicks.
A compliant exampleexample
opt_in_url: https://acmecoffee.com/checkout — not https://acmecoffee.com
Common mistakespitfalls
- A form that only appears after a delay, a scroll, or an exit-intent trigger is not on the page as far as a crawler is concerned — host a permanent version and register that.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Bandwidth/DCA | 2125 | Yes |
Rules you will hit next
Other consent flow rules at the same severity. A registration is judged as a whole, not rule by rule.
CON-008The live CTA and the declared message flow must say the same thingBlockingBLOCKINGCON-010The three subscriber-management attributes must be declared trueBlockingBLOCKINGCON-013Subscriber attributes must agree with the message bodies suppliedBlockingBLOCKINGCON-023Evidence URLs must resolve without a loginBlockingBLOCKINGCON-024The opt-in URL must serve a certificate that verifiesBlockingBLOCKINGCON-034The business name on the artifact must match the registered brandBlockingBLOCKING
CON-027 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.