Declared attributes must be consistent with the crawled site
The requirementstatement
The declared campaign attributes must be consistent with what the website shows, not only internally consistent with the form.
- Severityseverity
- HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- brand website + campaign attributes
- Where it liveslayer
- WebsiteWEBSITE
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- 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
- TCRTwilioAWS
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Reconcile each attribute against the website: age-gated products, lending offers, links and phone numbers in messaging.
A compliant exampleexample
Site sells age-restricted products → age gated: true.
Rules you will hit next
Other website rules at the same severity. A registration is judged as a whole, not rule by rule.
WEB-060 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.