# Web applications: Source actions are missing for subdomain navigations

**URL:** <https://community.dynatrace.com/t/web-applications-source-actions-are-missing-for-subdomain-navigations/44558>\
**Category:** Troubleshooting\
**Tags:** real-user-monitoring-classic, web-monitoring\
**Created:** [March 19, 2024, 11:40am UTC](https://community.dynatrace.com/t/web-applications-source-actions-are-missing-for-subdomain-navigations/44558 "2024-03-19T11:40:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![maliborskaya](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@maliborskaya](https://community.dynatrace.com/u/maliborskaya)\
**Post date:** [March 19, 2024, 11:40am UTC](https://community.dynatrace.com/t/web-applications-source-actions-are-missing-for-subdomain-navigations/44558/1 "2024-03-19T11:40:00Z")

</div>

Starting with November 2022, browsers implemented a stricter&nbsp;[referrer policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy). This resulted in missing subdomain source actions for your applications monitored with Dynatrace.

The referrer policy controls the&nbsp;[`document.referrer`](https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer)&nbsp;property on a target page. After the default referrer policy changed from&nbsp;`no-referrer-when-downgrade`&nbsp;to&nbsp;`strict-origin-when-cross-origin`&nbsp;in 2022,&nbsp;`document.referrer`&nbsp;is populated only with the&nbsp;[origin](https://web.dev/same-site-same-origin/#origin), while the full URL of the source page is stripped away for cross-origin requests. For example, if you navigate from&nbsp;`https://www.dynatrace.com/pricing`&nbsp;to&nbsp;`https://community.dynatrace.com`, the&nbsp;`document.referrer`&nbsp;on the target page contains just&nbsp;`https://www.dynatrace.com`.

As the full URL of the source page is truncated, Dynatrace can’t determine the exact origin of the navigation and has to drop the source action information. This results in navigation actions that are shorter than they would have been if the full URL of the source page had been available.

To fix this issue, set the&nbsp;[referrer policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy)&nbsp;of the origin page to&nbsp;`no-referrer-when-downgrade`&nbsp;either via the&nbsp;`Referrer-Policy`&nbsp;HTTP header or inside HTML. This will populate&nbsp;`document.referrer`&nbsp;on the target page with the full URL of the source page (only when the protocol security level stays the same or improves: HTTP \> HTTP, HTTP \> HTTPS, HTTPS \> HTTPS).

_ **Note:** _ Privacy-focused browsers like Brave ignore the set referrer policy, so it’s always&nbsp;`strict-origin-when-cross-origin`. For this reason, Dynatrace can’t generate source actions for subdomain navigations within such browsers.
