Blackleaf Help Center
Platform and texting FAQ
Direct answers about Blackleaf, customer messaging, contacts, campaigns, delivery, compliance, billing, and troubleshooting.
Compliance information is general guidance, not legal advice. Requirements vary by jurisdiction, sender, content, and use case.
age-gates
Identity gates and regulated content
Why Blackleaf confirms the intended recipient before showing regulated campaign content.
Why do I have to use an age gate?
Short answer: For regulated campaigns, Blackleaf uses the gate to confirm that the visitor is the person the message was intended for before revealing the campaign destination.
The sender is expected to know that the recipient is eligible before sending. The gate supports the regulated carrier workflow by matching the visitor to information already associated with the intended recipient; it is not a new age determination and does not replace consent, sender registration, or legal review.
Does an age gate prove legal age?
Short answer: No. Blackleaf’s gate is an identity check, not an age determination. It asks the visitor to recognize the birthday associated with the intended recipient record before opening the message.
Why does the identity gate ask for a birthday?
Short answer: Birthday is a practical detail the intended recipient previously supplied and can recognize, so it can help match the visitor to the customer record without asking them to enter additional information.
The business must establish eligibility before sending. Recognizing a birthday at the gate does not create consent, prove ownership of a phone, or replace any required eligibility process.
Is passing an age gate the same as opting in?
Short answer: No. Identity confirmation and SMS consent are separate. Passing the gate does not subscribe someone to messages.
Which domain does the age gate use?
Short answer: The campaign uses the age-gate link domain selected in the landing-page toolbar. Available domains depend on account configuration.
Can I bypass the age gate?
Short answer: Do not bypass the approved identity-gated workflow for content that requires it. If you believe a campaign does not need the gate, ask Support before sending.
Why is my age-gate link not working?
Short answer: Check the selected domain, destination mode, landing or redirect content, button URL, and save state. Send a test, then check System Status or Support.