This article will detail steps you can take to ensure that your BTT script or plugin is set up optimally and performing at the level we expect it to perform. This is not meant to be a troubleshooting document. While not exhaustive, this list will give you some ideas to explore if you're looking to improve the script's performance.
- First and foremost, the more customers are prompted to log into your site, the better. As a general rule, having customers sign in will improve our script's ability to identify the browser and thus track and store their behavior for use in WhatCounts.
- Are events coming through on the BTT Validator page in WhatCounts? Use the sample events and the advanced report to verify that the data looks accurate, reasonable, and generally in line with what you would expect.
- On the site, go through the following scenarios (if applicable) and verify that they send identify events. Make sure to use "incognito mode" or some other form of cookie-less browsing, and close/open your browser window between each step.
- Sign into an account page
- Sign up for a mailing list
- Go through the guest checkout process
- If it is a multi-step process, an identify event should fire as soon as an email address is submitted to the backend.
- If it is a one-step process, or an email address submission is not requested until the end of the process, an identify event should fire as soon as the order is completed.
- Out of incognito mode, verify the following: If you log into an account, close your browser, and then go back to the site, if the site "remembers" who you are and doesn't require you to log back in, it also sends an identify event to let you know.
- Verify that anywhere a product can be added to a cart (including category pages), doing so triggers an add-to-cart event.
- Verify that anytime a cart is viewed or updated (including if your site has popover cart functionality as opposed to a designated cart page), a viewed-cart event is triggered. Please note: This is only needed for Cart Recovery and not for Browse Abandonment.
Steps to Verify an Event Occurred from Your Browser
Note: We suggest using Google Chrome for this.
Use Chrome's incognito mode to avoid keeping data around and mixing signals.
Open up Developer Tools (Settings > More Tools > Developer Tools).
Got to the Network tab, click "preserve log," and filter requests down to requests with the text "windsor".
With the Network tab open, go to a page on your store you want to test. You should see a few requests label "event" of method "POST" appear. Those are the WhatCounts site analytics events.
Click on one of the events, and then scroll down to the request payload section.
The request payload section holds the event data, and you can examine it to see what information is sent in the events.
Remember that you need to have the Network tab open when the events happen to capture them, and the request log clears when you move to a new page. You can stop that second behavior from happening by clicking the "preserve log" option at the top of the network panel. This can be helpful for events like "add to cart" that might cause you to change pages when you trigger them.
Privacy Law Compliance