A QR opt-in must supply the QR code image itself
The requirementstatement
A QR-code opt-in must include the QR image in the registration evidence.
- 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 evidence (OptInImageURLs)
- 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
- Twilio
- When it appliesapplicabilityText
- Applies when consent was collected by QR code.
Why this rule existsrationale
The QR code is the only part of a QR flow a reviewer can independently verify: they scan it and see where it actually goes, which is the one thing the description cannot establish. A code that resolves somewhere other than the stated destination is the specific defect this evidence exists to catch, and it is invisible in every other field.
How to fix itremediation
Attach the QR image exactly as it appears on the printed piece — the same code, not a regenerated one pointing at the same URL — and scan it yourself from a printout before submitting. Done when scanning the attached image lands on the opt-in destination the flow describes.
Common mistakespitfalls
- Regenerating a "clean" QR for the submission defeats the check: the reviewer is verifying the code that is actually in the wild, and a code that has since been re-pointed will scan differently from the one on your poster.
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 |
Notesnotes
The presence half is settled here; whether the scanned destination is a compliant opt-in surface is CON-QR-DEST and CMP-103, which read the destination rather than the file. Split because they fail differently and are fixed by different people — one by attaching a file, the other by rebuilding a landing page.
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-101 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.