What it means
GTMAPIs exposes valid_role_based as a first-class status. It is not hidden inside valid because teams need to distinguish personal contacts from inboxes such as sales, info, support, or admin aliases.
All concepts
Email validation semantics
Valid role-based email
A valid_role_based result means the mailbox can be accepted while still being a low-value team or function address for outbound targeting.
Canonical status
valid_role_based
Status language is backed by the shared validation result contract and product publish gates.
Quality signals
- valid_role_based
- low
- role-based
Recommended actions
- Do not count as high-value validation
- Route to suppression or low-priority review
- Keep the canonical status distinct from valid
How to use it
Outbound systems should keep role-based results visible for reporting, but should usually avoid treating them as personal send-ready leads.
- Preserve valid_role_based in exports
- Avoid upgrading it to high-value
- Review campaign rules before sending
Contract behavior
valid_role_based is one of the five canonical statuses in the public validation contract and passes through normalization unchanged. It is never classified as high-value, and validation summaries count it in its own bucket instead of folding it into valid.
- Canonical status, normalized as-is
- Never counted toward high_value
- Own bucket in validation summaries
Routing playbook
Role-based inboxes such as sales, info, support, or admin are usually shared. Route them by campaign intent rather than deleting them.
- Suppress from personal-touch sequences
- Keep for account-level or operational outreach where a shared inbox is the right target
- Report them separately so list-quality metrics stay honest
Related resources
Common questions
Is valid_role_based the same as valid?
No. It is a canonical public status with lower outbound quality than a high-value personal valid result.
Do role-based results consume credits?
Credits are consumed only for chargeable high-value validations. valid_role_based is never high-value, so it follows the non-chargeable path under the credit policy.
Should I delete role-based emails from my list?
Not necessarily. They are deliverable inboxes and can fit operational or account-level outreach. Suppress them from personal sequences and keep them visible in reporting.