If you are sending a long url parameter in the Engagement Builder, you may encounter character limits affecting your payload or your message delivery. This can be fixed shortening the url using a command in our Engagement Builder.
Simply add | shorten to any URL-bearing macro in an Engagement Builder email or SMS body and the rendered message will present a short link instead of the full URL. Clicks are attributed back to the workflow and trigger event that sent them.
How to use it
In the email or SMS body, mark the macro with a shorten pipe:
Ad Url: {{ article.props.url | shorten }}
Some details:
Works in both email and SMS.
Works on any macro path in the trigger event payload.
The macro resolves per recipient at send time, so the same template produces a different short link for each recipient's URL.
What can be shortened?
The macro's value is unwrapped back to a plain URL before shortening, so all of these work:
Value in the payload |
Result |
|---|---|
|
shortened as-is |
|
shortened as-is; the encoded parameter is preserved |
|
percent-decoded, then shortened |
|
base64-decoded, then shortened |
base64 of a percent-encoded URL |
both layers unwrapped, then shortened |
A value must include a scheme. www.example.com does not resolve; https://www.example.com does. This is deliberate — guessing http vs https would mean guessing the destination.
What happens when a value will not resolve
The two channels differ on purpose:
SMS: the send is blocked. An unshortened long URL will cause an error and the SMS will not be successfully dispatched.
Email: falls back to the full URL. For email, the original url is used instead but the email will be sent as normal.
Comments
0 comments
Please sign in to leave a comment.