With Coveo Qubit explorer

The Qubit Explorer, provides a real-time insight into the accuracy, completeness, and overall quality of the data being triggered on a page and is our recommended tool for taking your first steps in validating your QProtocol setup.

To start Qubit Explorer, select Experiences from the side menu and select Launch Explorer:

Alternatively, open an experience from one of your lists and select in the upper-right hand corner of the page. Once your site has loaded, you’ll see an on-page prompt:

Select this to open the Explorer and then select Events:

So, we’ve opened the Explorer and we can now see a list of events triggered on the page. For each event, we report the event name, a count showing how many times the event was emitted on the page, and a status:

To give you a better view of your site, you can minimize the Explorer window by selecting

Particularly useful those users interested in validating their QProtocol implementation against a Qubit product or implementation level, filters enable you to concentrate on those events that really matter to you.

For example, you might wish to validate against the events required for a particular product such as Recommendations or Social proof. Alternatively, you might wish to validate against an implementation level, such as Best practice.

By default, the Explorer will show all events emitted on the page. To change this, make a selection from the combo box provided:

The filters available to you’ll vary according to vertical and will be based on your Qubit setup. When you select a filter, the events panel is updated and will show the QProtocol events emitted on the page that are associated with that filter.

Refer to the following table, which shows the filters and events included in each filter for the ecommerce vertical as an example:

To clear the events from the Explorer, select Reset. You can now refresh the page or continue with your navigation to re-populate the Explorer with events.

By default, when you navigate to a new page or refresh a page, the events emitted on the previous view are cleared. This gives you a clean view of the events emitted on each page. Because some experiences and features span multiple pages, we have provided the option to view the events emitted on each page in your session.

To enable this option, select and Enable events per session.

For more advanced event debugging, you can enable console logs to write event errors to your browser’s console.

To do this, select and Enable console logs. Let’s take a look at an example:

In the above example, we write the 3 errors reported in the Explorer to the console. We can then inspect each of these errors. Let’s take a look at the ecBasketSummary event error:

Here we can see in even more detail the root cause of the error, including the QProtocol path:

Some third-party privacy or security-related browser extensions, such as Ghostery, may prevent Qubit Explorer from loading correctly in the browser.

If you have enabled the option Enhanced Anti-Tracking, Ghostery will trigger a re-authentication with Qubit and will prevent you from logging in. You can avoid this by disabling this option in the Simple View: