# Dynatrace JS tag not injected/no RUM monitoring for certain users

**URL:** <https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422>\
**Category:** Real User Monitoring\
**Tags:** real-user-monitoring-classic, user-sessions\
**Created:** [February 4, 2019, 12:23pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422 "2019-02-04T12:23:31Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![boban\_josipovic](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@boban\_josipovic](https://community.dynatrace.com/u/boban_josipovic)\
**Post date:** [February 4, 2019, 12:23pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/1 "2019-02-04T12:23:31Z")

</div>

We noticed that for about 10-15 users the JS tag is not being injected and there is no RUM when they hit an application using Chrome. When they user Chrome incognito mode, everything seems to be working fine. Has anyone experienced similar issues?

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [February 4, 2019, 12:32pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/2 "2019-02-04T12:32:12Z")

</div>

Check if users has setup Nofollow flag in browser. If dynatrace settings are set to respect it, this can happen. Dynatrace is deciding about injection of script on webserver side. This is also option about quota limitation of rum injection (no 100%) for huge applications to limit license consumption.

Sebastian

---

<div class="post-metadata">

**Author:** ![boban\_josipovic](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@boban\_josipovic](https://community.dynatrace.com/u/boban_josipovic)\
**Post date:** [February 4, 2019, 12:35pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/3 "2019-02-04T12:35:34Z")

</div>

Thanks for the response. I did verify that the nofollow flag is off and the application is not that large (150 users during peak times). I also made sure that I turned off the Dynatrace feature to respect the nofollow flag for now

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [February 4, 2019, 12:38pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/4 "2019-02-04T12:38:37Z")

</div>

So you have set up for catching 100% of users sessions?

Sebastian

---

<div class="post-metadata">

**Author:** ![boban\_josipovic](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@boban\_josipovic](https://community.dynatrace.com/u/boban_josipovic)\
**Post date:** [February 4, 2019, 12:43pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/5 "2019-02-04T12:43:04Z")

</div>

Yes, we have set up to catch 100% of user sessions

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [February 4, 2019, 12:47pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/6 "2019-02-04T12:47:49Z")

</div>

When you clear cookies on regular browser (not incognito mode), does it work?

Sebastian

---

<div class="post-metadata">

**Author:** ![boban\_josipovic](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@boban\_josipovic](https://community.dynatrace.com/u/boban_josipovic)\
**Post date:** [February 4, 2019, 12:51pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/7 "2019-02-04T12:51:35Z")

</div>

No, I did try clearing cookies and browser cache. I also compared all other browser settings for that user to my settings and they matched.

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [February 4, 2019, 12:52pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/8 "2019-02-04T12:52:42Z")

</div>

Browser switching? Have you any limitation to which browsers or browser versions should dynatrace been injected (application → edit → Advanced)?

Sebastian

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [February 4, 2019, 2:26pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/9 "2019-02-04T14:26:00Z")

</div>

Any chance they are using adblocker such as uBlock origin? In my case uBlock blocked the RUM JS agent in its default configuration.

---

<div class="post-metadata">

**Author:** ![AlexanderSommer](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/alexandersommer/32/2501_2.png) [@AlexanderSommer](https://community.dynatrace.com/u/AlexanderSommer)\
**Post date:** [February 5, 2019, 7:58am UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/10 "2019-02-05T07:58:36Z")

</div>

@Boban J.: You wrote that the JS tag is not injected - so looking at the html source you are not seeing the JS tag? Injection means: adding the RUM JavaScript code to the html.  
The injection is done by the OneAgent on the server side and therefore no AddBlocker or DoNotTrack setting has an impact on the injection.

If the injection was successful and the RUM JS code (tag) is added to the html but no beacon is send back by the browser, than it could be that an AddBlocker is blocking the download of the JS file or the beacon itself.

If the browser has the DoNoTrack feature turned on, the beacon will still be send back to the Dynatrace cluster, but depending on your Dynatrace application configuration, the data will be anonymized or dismissed at the cluster.

---

<div class="post-metadata">

**Author:** ![boban\_josipovic](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@boban\_josipovic](https://community.dynatrace.com/u/boban_josipovic)\
**Post date:** [February 5, 2019, 11:48am UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/11 "2019-02-05T11:48:04Z")

</div>

I did also try difference browsers and confirmed that we do not have setup inject on specific browsers. Digging through it further we noticed that the group policy for the users we are not able to track has some proxy configurations setup that the other users, which we track, does not. I will update this question once I confirm that is the case.

---

<div class="post-metadata">

**Author:** ![boban\_josipovic](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@boban\_josipovic](https://community.dynatrace.com/u/boban_josipovic)\
**Post date:** [February 5, 2019, 11:51am UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/12 "2019-02-05T11:51:21Z")

</div>

[@Alexander S.](https://answers.dynatrace.com/users/12024/view.html)

- Yes, no JS tag in the HTML of the page only for certain users, but it works in incognito mode for those users. We have narrowed it down to a potential group policy issue since the users that are not seeing the JS tag in the HTML do have some proxy configuration in their group policy and the other users do not. I will update this thread once I confirm that is the case.

---

<div class="post-metadata">

**Author:** ![MANISH\_R\_VED1](https://avatars.discourse-cdn.com/v4/letter/m/91b2a8/32.png) [@MANISH\_R\_VED1](https://community.dynatrace.com/u/MANISH_R_VED1)\
**Post date:** [December 4, 2019, 3:01pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/13 "2019-12-04T15:01:03Z")

</div>

Hi Boban, Was it the proxy config or something else?

---

<div class="post-metadata">

**Author:** ![boban\_josipovic](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@boban\_josipovic](https://community.dynatrace.com/u/boban_josipovic)\
**Post date:** [December 4, 2019, 3:21pm UTC](https://community.dynatrace.com/t/dynatrace-js-tag-not-injected-no-rum-monitoring-for-certain-users/19422/14 "2019-12-04T15:21:51Z")

</div>

It was group policy related. The users in question did not have the right policy pushed. Once the policies were pushed it resolved the issue.
