This token allows you to append an entire URL onto your tracking link which LinkTrust will use to redirect the consumer to as the Landing Page of the campaign. By adding a Landing Page URL to your Tracking Link and saving the [=NonEncodedURL=] token as the landing page for a campaign, LinkTrust will redirect consumers to the URL placed on the tracking link. Why can't I do this with my own custom named token? LinkTrust will not URL encode the value of this token like it normally does with all other tokens that are placed in a URL. If LinkTrust were to URL encode this URL, browsers would not successfully redirect the consumer.
How to use the token to setup a dynamic landing page for a campaign:
- Add a complete landing page URL to the end of your tracking link using the "NonEncodedURL" as the name of the value.
Example: http://www.TrackingLink.com/click.track?CID=XXX&AFID=XXX&NonEncodedURL=http://www.google.com.
Note: Since you are appending a complete URL to a URL, ensure that you URL encode characters in your landing page URL if necessary. - Enter the [=NonEncodedURL=] token as the campaign's landing page.
- Resulting landing page will be http://www.google.com
Additional Information:
Any data passed to LinkTrust should be url encoded to ensure any special characters are not improperly interpreted. We do parse query strings per the standard and thus characters such as & and = can create issues when they are not properly encoded. You can pass double encoded values to us we will only unencode them once.
The NonEncodedURL token and other nonencoded tokens refer to what is done with the data when passing it out of LinkTrust. Normally when token values are replaced in a redirect url we url encode the values as we build the url to ensure any special characters do not create problems in the final resulting url. There are cases though where the value of a token should not be url encoded when building the final redirect url. That is what that token is for. One specific use case is as follows:
A campaign needs to redirect to different urls based on logic that is not held within LinkTrust. I should note that using Landing Page rules the need for this is much less. However if you need LinkTrust to track the click but redirect to different urls based on data outside of LinkTrust you could pass the url to LinkTrust that you want to redirect to. That url would be passed to LinkTrust as an additional data parameter on the click url. It should be url encoded. If you were to put that token in the landing page url box then we would normally url encode the value before sending the redirect which would not be good if the value was a url. So you could put in the landing page box the NonEncodedURL token which would tell LinkTrust not to URL encode the value when replacing the token.
You can request a demo to see LinkTrust up close and experience how it can help you, or start your free 14-day trial now.
Need help with this feature or have questions? You can contact our support team at support@linktrust.com