Debug Tracking using the Browser Console
When setting up the tracking, the best way to debug it is to head over to your site and try it out. You can view the events that are sent to CrossEngage by using the Browser Console, for example in Chrome.
If you are using Google Chrome, to open the console, right click anywhere on your page and click Inspect. In order to find the events that are sent to CrossEngage, click on the Network tab in the top bar. In the search window, type "track". Refresh the page and you will see events that are sent to CrossEngage.
Click on one of these events to inspect it in detail. If you unfold the Request Payload, you will see all information that is sent to CrossEngage:
In order to debug the setup, trigger the events the way you have set them up and make sure that they are sent correctly to CrossEngage with all fields the way you want them set up.
Verify Tracking in the Event Stream
After making sure that you are sending the events correctly, you can verify the setup in CrossEngage to make sure they are arriving correctly. This is the last step in the setup process for an event.
Log into you CrossEngage account, navigate to Settings -> Event Stream. Click on Start to see any events as they are coming in.
You now have the option to filter down to the event type you are trying to verify, for example
Viewed Page or
If you want to be even more specific, find your
xngGlobalUserId using the method described above and enter it in the search window. The
xngGlobalUserId is used by CrossEngage to track any user, even if they are anonymous. If you now trigger more events, you should see them coming in in the stream.
You can click on an event to see more detail about what information is being sent together with it.