Testing & debugging

Using the browser console
After setting up the web tracking SDK, the best way to debug it is by going on the site it was installed on and monitoring the network traffic through your preferred browser's Inspect tool.
For example, if you are using Google Chrome, open the console by right clicking anywhere on your page and choosing Inspect. In order to find the events that are sent to CrossEngage, click on the Network tab in the top bar of the newly opened inspect area. In the search window, type track. Refresh the page to see all events sent to CrossEngage and continue browsing, analysing whether or not the events are triggered as expected.
To view the events in detail, unfold the Request Payload, you will see all information that is sent to CrossEngage:
Using the event stream
In addition to using your preferred browser's inspect tools to ensure that events are sending correctly, you can also verify this through the Event Stream feature of CrossEngage.
To monitor events in real-time, select "Event Stream" from the navigation bar.
Enter the desired User/Session ID, choose your desired filter category, and click "Start listening"
Example Error
If your domain is not yet authorized by CrossEngage, you will receive the following error message:
1
XMLHttpRequest cannot load https://api.crossengage.io/api/.... Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Copied!
In order to fix this, please submit a ticket with a request to include your website in the list of accepted domains.

Opt-out from tracking

Change Log

Last modified 2yr ago

Copy link

Contents

Using the browser console

Using the event stream

Example Error