Content
Event Tracer is required for tracking events that are sent by the client in real-time. Event Tracer is just a viewer tool for testing convenience.
General overview : Event listening starts when admin opens user profile and will end in 24h. Events are stored locally in that exact browser tab. Events will be cleared after page reload and timeout will be restarted.
TTL = 24h
🗺 Where to find
open App Users component in Admin Tool
open User Profile of required app user
go to “Events Tracer” tab
🕵️♂️ Listening start
Game Server starts listening events sent by the app user when the user profile is opened.
Connection is established automatically after opening page and will last for 24 hours. After page reloading TTL will be restored to 24h again.
📦 Events storage
Events are stored locally in browser tab. If you close the tab, server will continue events listening till the end of TTL, however they won’t be shown anywhere.
Steps to see events in real time
Open tracer before testing start
Launch the app on your test device. Green message will appear if the connection is established
Trigger and observe events
If a red message appears, check the internet connection and reload the page:
Click the [Clear] button to clear the page of all events
🪄 Filtering
Event batch can be filtered by two main filters (both require string as an input):
Event Name (requires full name of an event)
Event Contains (requires some part of an event)
Filters can be combined, also multiple strings are allowed to be added in one input.
Note : Events are not parsed inside one event object ( block ) though after filter applying full event object will be returned.
Filters can be cleared using [Clear Filters] button.
◼️ More about event blocks
Event block is a scope of events that is sent in one /events API call, it may contain [1; ∞+) events in itself. Many of the events are combined between each other which may make the block longer (e.g. GDPR_consent and screen_interaction)
Note : If user was offline for some time and then goes back online, client will make only one /events call with all the events since last /events call was made. That means that all events will be sent in one block.
⬇️ Sorting
Event objects can be sorted by the receiving time by server either ASC or DESC.
Chunks 1
Event Tracer is required for tracking events that are sent by the client in **real-time**. Event Tracer is just a viewer tool for testing convenience.
* * *
**General overview** : Event listening starts when admin opens user profile and will end in 24h. Events are stored locally in that exact browser tab. Events will be cleared after page reload and timeout will be restarted.
**TTL = 24h**
## 🗺 Where to find
1. open App Users component in Admin Tool
2. [open User Profile](/wiki/spaces/GS/pages/1379074056/Guide+How+to+find+my+device+or+user) of required app user
3. go to “Events Tracer” tab
## 🕵️♂️ Listening start
Game Server starts listening events sent by the app user **when the user profile is opened**.
Connection is established automatically after opening page and will last for **24 hours**. After page reloading TTL will be restored to 24h again.
## 📦 Events storage
Events are stored **locally in browser tab**. If you close the tab, server will continue events listening till the end of TTL, however they won’t be shown anywhere.
##
 Steps to see events in real time
1. Open tracer **before testing** start
2. Launch the app on your test device. Green message will appear if the connection is established
3. Trigger and observe events
If a red message appears, check the internet connection and reload the page:
Click the [**Clear**] button to clear the page of all events
## 🪄 Filtering
Event batch can be filtered by two main filters (both require string as an input):
- Event Name (requires **full** name of an event)
- Event Contains (requires **some** part of an event)
Filters can be combined, also multiple strings are allowed to be added in one input.
**Note** : Events are not parsed inside one event object ( **block** ) though after filter applying full event object will be returned.
Filters can be cleared using [**Clear Filters**] button.
## ◼️ More about event blocks
Event block is a scope of events that is sent in one `/events` API call, it may contain [1; ∞+) events in itself. Many of the events are combined between each other which may make the block longer (e.g. _GDPR\_consent_ and _screen\_interaction_)
**Note** : If user was offline for some time and then goes back online, client will make only **one** `/events` call with all the events since last `/events` call was made. That means that all events will be sent in **one** block.
## ⬇️ Sorting
Event objects can be sorted by the receiving time by server either ASC or DESC.
