# \[React\] \[RUM\] - Not all user actions visible on react application

**URL:** <https://community.dynatrace.com/t/react-rum-not-all-user-actions-visible-on-react-application/11697>\
**Category:** Real User Monitoring\
**Tags:** real-user-monitoring-classic, javascript, dynatrace-api\
**Created:** [April 23, 2018, 12:16pm UTC](https://community.dynatrace.com/t/react-rum-not-all-user-actions-visible-on-react-application/11697 "2018-04-23T12:16:55Z")\
**Posts on this page:** 9\
**Page:** 1

<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:** [April 23, 2018, 12:16pm UTC](https://community.dynatrace.com/t/react-rum-not-all-user-actions-visible-on-react-application/11697/1 "2018-04-23T12:16:55Z")

</div>

Hello,

we have problem with react SPA applications. Not all actions are visible. For example when some of them not making full page reload (background XHR request to API). Are there any specific configurations should we make to extend what we see?

---

<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:** [April 26, 2018, 9:41am UTC](https://community.dynatrace.com/t/react-rum-not-all-user-actions-visible-on-react-application/11697/2 "2018-04-26T09:41:58Z")

</div>

Have you turned on XHR and Fetch API capturing? Please look at the application configuration - Async requests and single page apps.

---

<div class="post-metadata">

**Author:** ![Yosi\_Neuman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/yosi_neuman/32/9845_2.png) [@Yosi\_Neuman](https://community.dynatrace.com/u/Yosi_Neuman)\
**Post date:** [December 10, 2018, 10:47am UTC](https://community.dynatrace.com/t/react-rum-not-all-user-actions-visible-on-react-application/11697/3 "2018-12-10T10:47:05Z")

</div>

Hi Alexander,

We have the same issue and we turned on XHR and Fetch API capturing and still we dont see rb\_\* in devtools nor user actions

What else can do the trick here?

Yos

---

<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:** [December 10, 2018, 11:02am UTC](https://community.dynatrace.com/t/react-rum-not-all-user-actions-visible-on-react-application/11697/4 "2018-12-10T11:02:59Z")

</div>

I have spoken some times ago with somebody from DT about react support. According to my information it’s not fully supported right know but you should see at leas some of user actions.

---

<div class="post-metadata">

**Author:** ![Yosi\_Neuman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/yosi_neuman/32/9845_2.png) [@Yosi\_Neuman](https://community.dynatrace.com/u/Yosi_Neuman)\
**Post date:** [December 10, 2018, 3:00pm UTC](https://community.dynatrace.com/t/react-rum-not-all-user-actions-visible-on-react-application/11697/5 "2018-12-10T15:00:39Z")

</div>

Thanks for the update [@sebastian k.](https://answers.dynatrace.com/users/15061/view.html)!

---

<div class="post-metadata">

**Author:** ![akshay\_misra](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@akshay\_misra](https://community.dynatrace.com/u/akshay_misra)\
**Post date:** [February 20, 2019, 6:51am UTC](https://community.dynatrace.com/t/react-rum-not-all-user-actions-visible-on-react-application/11697/6 "2019-02-20T06:51:55Z")

</div>

Hi - Any update on this, facing same issue with React user action - wherein fragment parameter with **#/abcde** part of URL is not getting captured as part of the URL in user actions.

For example -

If my URL is like **/abcd/efgh.html#/xxxx**

Only following is captured - **/abcd/efgh.html** without the fragment.

Need the complete URL with fragment

---

<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 20, 2019, 9:55am UTC](https://community.dynatrace.com/t/react-rum-not-all-user-actions-visible-on-react-application/11697/7 "2019-02-20T09:55:28Z")

</div>

You can create user action naming rules based on anchor:

 ![19799-zrzut-ekranu-2019-02-20-o-105509.png](https://global.discourse-cdn.com/dynatrace/original/3X/9/5/95a890849bc1a94a4fbffed0a9747faa6e2084be.png)

---

<div class="post-metadata">

**Author:** ![ravi](https://avatars.discourse-cdn.com/v4/letter/r/58956e/32.png) [@ravi](https://community.dynatrace.com/u/ravi)\
**Post date:** [March 5, 2019, 12:56am UTC](https://community.dynatrace.com/t/react-rum-not-all-user-actions-visible-on-react-application/11697/8 "2019-03-05T00:56:47Z")

</div>

Do we have any solution on this? I am facing similar issue and turning on fetch or XmlHttpRequest() is not the solution. It just tracks the individual requests as pages.

What we are really looking for is, for the DT JS to trigger again, when the browser push state is done. What I have currently tried is, using Google Tag Manager (GTM) we instrument the site manually with DT javascript code. When the browser history changes, we fire the DT javascript again (via GTM). But the DT javascript has checks in place that prevent it from loading again on the same page. Removing these checks also did not help.

How are your customers using manually instrument web applications that are Single page apps that use react (react router) for frontend navigation.

---

<div class="post-metadata">

**Author:** ![jchabot86](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@jchabot86](https://community.dynatrace.com/u/jchabot86)\
**Post date:** [May 24, 2023, 1:36pm UTC](https://community.dynatrace.com/t/react-rum-not-all-user-actions-visible-on-react-application/11697/9 "2023-05-24T13:36:12Z")

</div>

Same issue here
