Link shortening is not supported for links stored in Relational Tables in Acoustic Campaign. This is a platform limitation, not a configuration issue. If your shortened links are not working in SMS campaigns, check whether the links are being pulled from a Relational Table.
What works and what doesn't
| Supported | Not supported |
|---|---|
| Static links added directly to SMS message content | Dynamic links pulled from Relational Tables using personalization syntax |
| Links hardcoded within the SMS template | %%RT::/Path/TableName::FieldName%% |
Why this limitation exists
Link shortening in SMS campaigns requires the system to process and convert URLs at send time. Relational Tables are designed to organize and relate data — they do not support link tracking or URL transformation. When a link is populated from a Relational Table field, the system retrieves the raw URL value and does not apply link-shortening logic.
Workarounds
Option 1: Pre-shorten URLs using a third-party service
Before storing URLs in the Relational Table, shorten them using a service such as Bitly or a custom short domain. The shortened URLs are then saved directly in the Relational Table field and will send correctly without requiring the platform to apply shortening at send time.
Option 2: Use static links when possible
If the same link applies to all recipients, include it directly in the SMS content instead of pulling it from a Relational Table. Static links are fully supported for link shortening.
Option 3: Generate pre-shortened URLs at the data source
For campaigns that require unique links per recipient, generate pre-shortened URLs in your data source before importing them into the Relational Table. This ensures each contact receives a unique shortened link without relying on the platform to apply shortening logic.
Related documentation
For more information on configuring and analyzing shortened links in SMS campaigns, see Configure and analyze shortened links in SMS.