Skip to main content

Developer Debug Mode

Once you have PureClarity integrated and the master function is on all your pages you can use the developer debug bar to help ensure zones are being detected, view any data associated with them and ensure tracking events are working correctly and being passed to PureClarity. To activate the debug bar, ensure you are logged into the PureClarity Admin console, and then on your website add the following query string parameter to the end of the URL: pc_debug=true
Example: www.yoursite.com/shop?pc_debug=true
The PureClarity Debug Bar will appear showing a number of selectable tabs at the top. The first tab shows the status of the PureClarity integration, and will only show if you’re logged into the admin at the same time and PureClarity is active, and have the correct store view selected in the admin. The Template Preview mode tells you whether any templates on the site are in Preview mode (explained in further detail below). The Events tab shows all the events sent from the site to PureClarity on the current page, and the responses from PureClarity. This is useful to see, for example, if on a product page the product view tracking event is being sent with the correct Id. The Zones tab gives you an overview of all the zones that are active on the page. It shows what context information is being sent to PureClarity (such as the product Id associated with a zone) and also shows whether PureClarity understood the request. Finally the Previews tab shows you which, if any, templates are being previewed, what type of template it is, and what version it is. This developer debug, when active, enables templates marked as “in preview” to be used rather than the current live template to assist with styling. Only you will see templates in preview and not your customers. Further information on editing and previewing templates see the Templating section.
If you are using server-side integration, zones may be rendered on the server and thus may not be detectable by the developer debug system. More information about this is outlined in the server-side implementation section in this guide.