Dynamics 365 Customer Insights – Journeys: Working with < safe-script > Update

Written by Coffee + Dunn



June 4, 2024



Dynamics 365 Customer Insights - Working with safe-script Update

💡Tuesday Tip: Is your real-time form not rendering how it should? You may need to take a look at HTML.

When Microsoft pushed out the <safe-script> code update for Customer Insights – Journeys version 1.1.38813.80 or newer, it not only moved any custom JavaScript from the <head> section to the <body> section of the HTML, but also inadvertently relocated the meta tags. This update affected the structure of the HTML forms, for example, you may see hidden fields as visible on your form.

Watch this video to see how to relocate your meta tags back to the appropriate location:

Dynamics 365 Customer Insights, Dynamics 365 Customer Insights - Journeys, Dynamics 365 Marketing, Marketing Strategy

Find what you’re looking for

Stay current

Get our monthly Dynamics 365 insights delivered to your inbox.

SUBSCRIBE →

Relevant Posts

Business professional reviewing revenue operations strategy charts and line graph performance data.

Blog

Revenue Operations Strategy: How to Align Teams, Data, and Tech

As a revenue leader, you've probably pulled 3 reports before a pipeline review and got 3 different numbers for the same quarter. The mismatch happens often because your marketing, sales, and customer success teams measure different metrics and hardly synchronize...

The Permission Slip: Managing Consent in D365 Customer Insights – Journeys

Preference center: ready. Journeys: built. But are you actually compliant? Made for marketers running Customer Insights – Journeys who need to understand how consent really works under the hood, we'll cover the consent hierarchy in CI-J, how it captures and...

RevOps Implementation Guide for Sales, Marketing, and CS

Revenue rarely stalls because of a lack of effort. The problem is that your sales, marketing, and customer success teams often work from 3 separate versions of the truth, while each team defends numbers the others reject. You can solve the disconnect with a RevOps...