Use a branded redirect page for Customer Insights - Journeys links
Diesen Beitrag auf Deutsch lesen
A JavaScript redirect page can preserve trusted company domains and UTM parameters while replacing Customer Insights - Journeys built-in link tracking.
TL;DR
Customer Insights - Journeys has no branded-link feature in the described release context, so a company-hosted redirect page can validate a target URL, forward other query parameters such as UTM tags, and redirect visitors. Built-in Tracking must be switched off because Microsoft redirect pages can violate a no-external-domain policy.
Original on Powerplatform.se. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
Makers should assemble the company-hosted redirect URL with the encoded target and relevant tracking parameters, because the workaround requires manual or custom generation. Admins/CoE should review the JavaScript validation and destination handling before deployment, since the page redirects to a URL supplied in the query string. Security/Compliance should assess whether the redirect pattern satisfies the organisation’s trusted-domain policy. Webtracking was described as preview functionality at publication, so its current status should be verified.
Frequently asked questions
Why does a custom redirect page make sense for links from journeys?
Because Customer Insights Journeys offers no links on your own brand domain. The matching feature was deprioritized and removed from Release Wave 2 2024.
How does the self-built redirect page work technically?
It is a simple HTML page with a little JavaScript, hosted on the company domain, for example at contoso.com/redirect.html.
What has to be considered for click tracking in Customer Insights Journeys?
The built-in link tracking has to stay disabled, otherwise recipients land on a Microsoft redirect page again. As a replacement the author names two routes.