The QR landing page must be publicly reachable
The requirementstatement
The page a QR code opens must be fetchable by anyone — no login, geo-gate, app-install wall or captive portal in front of 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
- QR destination fetch
- 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
- TwilioBird
- When it appliesapplicabilityText
- Applies when consent was collected by QR code.
Why this rule existsrationale
How to fix itremediation
Host the QR destination on a public https page on the brand domain, with no login, no app interstitial and no dependence on the venue network. Done when scanning the code on a phone with mobile data and no app installed shows the opt-in.
Common mistakespitfalls
- Test the printed code, not the URL. A code printed from a draft, or one pointing at a short link whose account has lapsed, opens something entirely different from what was designed.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twiliogen2 | 30909 | Yes |
| Bandwidth/DCA | 804 | Yes |
Rules you will hit next
Other website rules at the same severity. A registration is judged as a whole, not rule by rule.
WEB-098 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.