Stream Inspector allows you to capture live events sent to your collection server from all devices in real-time.
It is very useful for debugging but as all traffic is captured, it is sometimes best to filter the traffic to show only yours.
DESKTOP
This can be done easily through different methods, we will talk here about the main 2 which are through Tag Inspector and the Network tab of your web browser.
TAG INSPECTOR:
On Tag Inspector, you will be able to copy the value available in the Visitor ID (client-side) parameter:
NETWORK TAB:
For the network tab you first need to filter the requests to isolate your events. In this case the filter "event?s=" was used, you can use your collect domain for example..
You will then see the different events sent during your navigation, you can click on one and copy the value from the request header "idclient:".
MOBILE & other devices:
Testing on a mobile environment requires more planning but there are multiple solutions to isolate your own traffic:
We do recommend using a perimeter where less data can be sent, for example a development environment that is not accessible to all your users.
If you need to test on a live app, then the best is to use specific parameter that are not shared:
- UserID
- Very specific search keyword on your search bar
- ...
Those methods should allow you to capture your specific event and then use the user-agent or other elements to filter your next session.
You could also have a specific model for testing purposes that could be easily identified.
STREAM INSPECTOR:
Once the ID has been retrived, you can filter on the clientID and get your own traffic captured: