# How to use the cloud variable to obtain the monitoring data change?

**URL:** <https://community.thunkable.com/t/how-to-use-the-cloud-variable-to-obtain-the-monitoring-data-change/1653642>\
**Category:** Questions about Thunkable X\
**Created:** [December 13, 2021, 6:59pm UTC](https://community.thunkable.com/t/how-to-use-the-cloud-variable-to-obtain-the-monitoring-data-change/1653642 "2021-12-13T18:59:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bibbi](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@bibbi](https://community.thunkable.com/u/bibbi)\
**Post date:** [December 13, 2021, 6:59pm UTC](https://community.thunkable.com/t/how-to-use-the-cloud-variable-to-obtain-the-monitoring-data-change/1653642/1 "2021-12-13T18:59:27Z")

</div>

hi

I read this interesting post

[How to use the variable cloud to obtain the monitoring data change function of the real-time database? - #2 by muneer](https://community.thunkable.com/t/how-to-use-the-variable-cloud-to-obtain-the-monitoring-data-change-function-of-the-real-time-database/1549604/2)?

which partly answers one of my concerns, however if I want to know which user whose data is modified it is not possible?

---

<div class="post-metadata">

**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\
**Post date:** [December 13, 2021, 7:12pm UTC](https://community.thunkable.com/t/how-to-use-the-cloud-variable-to-obtain-the-monitoring-data-change/1653642/2 "2021-12-13T19:12:44Z")

</div>

I don’t think you can do that with Thunkable blocks but it looks like you can use the API for that:

[https://firebase.google.com/docs/reference/rest/database/#section-streaming](https://firebase.google.com/docs/reference/rest/database/#section-streaming)

I haven’t tried it but if it can send the **path** and **data** values, you’ll have what you need:

> The server may send the following events:
> 
> ### put
> 
> The JSON-encoded data is an object with two keys: **path** and **data**. The **path** key points to a location relative to the request URL. The client should replace all of the data at that location in its cache with **data**.
> 
> ### patch
> 
> The JSON-encoded data is an object with two keys: **path** and **data**. The **path** key points to a location relative to the request URL. For each key in **data** , the client should replace the corresponding key in its cache with the data for that key in the message.

---

<div class="post-metadata">

**Author:** ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)\
**Post date:** [December 13, 2021, 7:34pm UTC](https://community.thunkable.com/t/how-to-use-the-cloud-variable-to-obtain-the-monitoring-data-change/1653642/3 "2021-12-13T19:34:32Z")

</div>

It is also worth reading this

> [@RealtimeDB DataChanged Refresh Issue when reopen screen](https://community.thunkable.com/t/realtimedb-datachanged-refresh-issue-when-reopen-screen/1652492/4):
>
> Thank you for the detailed explanation. I can tell you that will not work for two reasons. 1- Starts and Opens These names are confusing, actually they work different that what people think. One thing for sure that if you go back to your screen using a button which uses the Navigate to screen block then both Starts and Opens will execute. the only time the Starts will not execute is when you go back to the screen using the screen swipe gesture. To overcome this issue create an app variable f…

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/0/f/0f59f292712368bce16ff80133ae10de8a6f27e8.png) [@system](https://community.thunkable.com/u/system)\
**Post date:** [March 13, 2022, 7:34pm UTC](https://community.thunkable.com/t/how-to-use-the-cloud-variable-to-obtain-the-monitoring-data-change/1653642/4 "2022-03-13T19:34:44Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
