{"id":46349,"date":"2026-09-29T17:34:08","date_gmt":"2026-09-29T12:04:08","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=46349"},"modified":"2026-09-29T17:34:08","modified_gmt":"2026-09-29T12:04:08","slug":"web-tracking-and-personalization-overview-customer-insights-data-preview","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2026\/09\/web-tracking-and-personalization-overview-customer-insights-data-preview\/","title":{"rendered":"Web tracking and personalization overview (Customer Insights Data) – (Preview)"},"content":{"rendered":"

\"WebWeb tracking and personalization<\/strong> in Dynamics 365 Customer Insights – Data (Preview) enables organizations to track website interactions from anonymous and known visitors. This data can be associated with customer profiles and used for segmentation and personalized website experiences.<\/p>\n

For example, an insurance customer may browse coverage plans and use a quote calculator before creating an account. Web tracking can help connect those earlier interactions with the customer’s known profile.<\/p>\n

Note:<\/strong> Web tracking and personalization is a prerelease feature and is subject to change.<\/p>\n

The scenario: an insurance quote calculator<\/h3>\n

Let’s say an insurance company have a customer portal on Power Pages. Visitors can browse coverage plans and calculate a quote without logging in. Once they like their quote, they register for an account to save it and manage future claims.<\/p>\n

The goal<\/strong>: don’t lose that pre-signup browsing history. When a site visitor calculates a quote as an anonymous visitor and then signs up, his account should show that he looked at the “Comprehensive Coverage” plan twice before registering \u2014 not start with a blank slate.<\/p>\n

How it works, conceptually<\/h3>\n

There are two moving parts:<\/p>\n

    \n
  1. Anonymous tracking<\/strong> \u2014 the moment anyone lands on your site, a small script drops a cookie and starts logging page views. Customer Insights creates an “Unknown” profile keyed to that cookie.<\/li>\n
  2. Identity merge<\/strong> \u2014 when that visitor eventually logs in or registers, you tell Customer Insights, “this cookie belongs to this real person.” Everything the cookie did gets folded into their actual customer profile.<\/li>\n<\/ol>\n

    That is the overall approach. Now, let\u2019s move forward with the implementation.<\/p>\n

    Step-by-step implementation<\/h2>\n

    Step 1 – Enable the feature and get your script<\/strong><\/p>\n

    In Customer Insights – Data<\/strong>, go to Web tracking & personalization<\/strong>, select Contact <\/strong>as your identifying table (this should almost always be Contact, not Account \u2014 Contact represents an individual person who can actually log in; Account represents an organization), and copy the generated JavaScript snippet.<\/p>\n

    \"Web<\/p>\n

    Step 2 – Add the script to your Power Pages site<\/strong><\/p>\n

    This is the part that trips people up: the “Header” web template in Power Pages isn’t the literal <head> tag \u2014 it’s a partial. The correct place is a Content Snippet<\/strong> named exactly Head\/Bottom, set to type HTML<\/strong>, with no language specified so it applies globally. Paste your tracking script in there and publish.<\/p>\n

    \"Web<\/p>\n

    Step 3 – Handle the Content Security Policy<\/strong><\/p>\n

    If your site was created recently, Power Pages enforces a Content Security Policy by default, and it’ll block the tracking script’s domain unless you allow it. Go to Portal Management \u2192 Site Settings<\/strong>, find (or create) HTTP\/Content-Security-Policy, and add the tracking script’s domain to script-src. You’ll see the exact domain to add in your browser console if it gets blocked \u2014 copy it from the CSP violation error rather than guessing.<\/p>\n

    \"Web<\/p>\n

    Step 4 – Test as an anonymous visitor<\/strong><\/p>\n

    Open your site in an incognito window and click through a couple of pages \u2014 say, your quote calculator and a coverage page. Back in Customer Insights, go to Customers \u2192 Unknown<\/strong>, and you should see a cookie-ID profile appear with those page visits logged, usually within about 30 seconds.<\/p>\n

    Step 5 – Link identity on login<\/strong><\/p>\n

    Add a small script to the same Head\/Bottom snippet, using Liquid to detect an authenticated visitor:<\/p>\n

    {% if user %}<\/p>\n

    <script><\/p>\n

    if (window.msci && typeof window.msci.setUser === “function”) {<\/p>\n

    window.msci.setUser(“{{ user.contactid }}”);<\/p>\n

    }<\/p>\n

    <\/script><\/p>\n

    {% endif %}<\/p>\n

    {{ user.contactid }} is Power Pages’ built-in way of exposing the signed-in contact’s ID via Liquid \u2014 no custom login code needed. This script runs on every authenticated pageview, which is fine; it just re-confirms the link each time.<\/p>\n

    Step 6 – Verify the merge<\/strong><\/p>\n

    Register a test account, log in, and refresh a page. Back in Customer Insights, search for that Contact under Known <\/strong>customers \u2014 their timeline should now show the quote-calculator visit and coverage page views that happened before they ever logged in.<\/p>\n

    \"Web<\/p>\n

    Step 7 – Make the data useful<\/strong><\/p>\n

    Once this is flowing, the real payoff shows up in two places:<\/p>\n