#msdynmkt_trackingcontext=

(0) Share

Report

Posted on by AsheshR

Hi everyone,

I'm encountering a strange behavior with email links generated from Customer Insights - Journeys. The links in the emails are being appended with a fragment like this:

#msdynmkt_trackingcontext=cb7d3280-529d-4e07-bdf3-5f91f5690300

Instead of using an ampersand (&) to add tracking parameters to the query string, it's using a hash (#), which introduces a URL fragment. This is causing issues on our landing pages, especially those using hash-based routing or anchor navigation.

Has anyone else encountered this?

Is this expected behavior from Microsoft?

Can this tracking fragment be disabled or modified?

Any recommended workarounds to prevent it from interfering with site functionality?

Categories:

Dynamics 365 Customer Insights - Journeys

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

MVP-Daniyal Khaleel 585 on at

Like (0)

Report
#msdynmkt_trackingcontext=

What is #msdynmkt_trackingcontext and why is it there?

The fragment is part of the Dynamics 365 Marketing / Customer Insights – Journeys internal tracking mechanism. It is used to carry tracking context for email clicks, interactions, and marketing attribution.

It is appended as a URL fragment (after the #) rather than as a query parameter, so it doesn’t show up in server-side query string parsing. The fragment is intended to be processed client-side (by JavaScript) for tracking logic.

The fragment uses msdynmkt_trackingcontext as an identifier to link that click back to the journey/email instance and record in the TrackingContext entity/table.

By placing it as a fragment, it ensures that it does not interfere with or override existing query parameters (e.g. UTM tags) in most scenarios.

So,yes,it is expected behavior (or at least typical behavior) of Microsoft’s marketing email system to append this fragment.

Why it causes issues in your case

If your landing page (or frontend routing) uses hash-based routing (e.g. React Router with /#/page), or depends on fragment identifiers for in-page anchors, the #msdynmkt_trackingcontext=... fragment may conflict with that logic

Because the fragment is redirected after the #, some client-side scripts might misinterpret or override it, or treat it as an anchor jump.

If your JavaScript logic expects certain fragments or anchors, this added fragment can break or hijack behavior

Can it be disabled or modified?

Officially, Microsoft does not offer a built-in toggle to disable or remove the #msdynmkt_trackingcontext fragment for outgoing email links (at least not in public documentation). From community discussions, people have asked about disabling it, but there’s no documented switch.

Because the TrackingContext is core to how journeys match clicks back to contacts, completely removing it might break analytics, reporting, or attribution.

Was this reply helpful? Yes No