Decode a 10DLC rejection · Warning
Your rejection said something like this
“Public URL shortener detected in message content”
This means your samples or traffic use a shared public shortener, which masks the destination and is a spam signal to carriers. Use your own branded domain or a dedicated (non-shared) short link instead.
What this maps to
A rejection worded like that is the known 10DLC reason Public URL shorteners in messages. Shared shorteners (bit.ly, tinyurl) are heavily filtered because they mask the destination.
The fix
Use your own branded domain or a dedicated (non-shared) short link; avoid public shorteners in sample and production traffic.
Other ways this rejection is worded
Providers, TCR and the carriers phrase the same reason differently. If yours read more like one of these, it still maps to Public URL shorteners in messages:
- “Shared link shorteners (bit.ly, tinyurl) are not permitted”
- “Shortened links flagged in sample messages”
Common questions
What does the 10DLC rejection "Public URL shortener detected in message content" mean?
This means your samples or traffic use a shared public shortener, which masks the destination and is a spam signal to carriers. Use your own branded domain or a dedicated (non-shared) short link instead. It maps to the known rejection reason "Public URL shorteners in messages". The fix: Use your own branded domain or a dedicated (non-shared) short link; avoid public shorteners in sample and production traffic.
Why can't I use bit.ly in 10DLC messages?
Public shorteners hide the destination, which is a common spam tactic, so carriers filter them heavily. Links using shared shorteners can get a campaign flagged, rejected, or throttled.