Troubleshooting Your Distil Bot Discovery Tag

August 1, 2017
If you do not see human traffic and bot traffic segments correctly populating in your Google Analytics (GA) dashboard after deploying your Distil Bot Discovery (DBD) tag to your site, you can follow the troubleshooting steps in this video to make sure all of the tag elements are loading on the page and that the Distil Bot Discovery events are successfully gathering and sending data back to your google analytics account. First, Verify the google Analytics Tag is Deployed on the Page Visit a page of a domain where your bot discovery tag is deployed. For this video, we’ll use distilnetworks.com. If you are using Google’s Chrome browser, Right-click anywhere on the page and then select Inspect. After the browser launches the Developer Tools menu, select the Elements tab. Search for “analytics” to locate an instance of the google analytics.js. If the google Analytics tag is not found in your search, the google Analytics tag is not loading on the page. Please stop here and deploy the google Analytics tag on your site. Since the current google Analytics tag is present, we can proceed. Now, we’ll verify the Proper google Analytics Tracking ID is Loading on the Page While we’re still on the Elements tab, search for “ua-” to locate your google Analytics tracking ID. NOTE: Your google Analytics tracking ID is different from the google analytics tracking ID shown here (UA-25583222-1). Confirm the google Analytics tracking ID is the same as the google Analytics tracking ID used when setting up your DBD tag. If the google Analytics tracking ID is not the same, deploy the google Analytics tag with the same google Analytics tracking ID used when setting up your DBD tag. Since the google Analytics tracking ID is the same, we can proceed. Now, we’ll Verify the Distil Bot Discovery Tag is Deployed on the Page search for “distiltag.com” to locate the DBD tag on the page. If the bot discovery is not deployed on the page, stop here and deploy your bot discovery tag. Since the bot discovery tag is deployed on the page, we can proceed. Confirm the bot discovery tag includes the same google Analytics tracking ID as confirmed earlier in this video. Confirm the bot discovery tag includes the same custom dimension index you used when creating your bot discovery tag. Your Custom Dimension index number is preceded by CDI= and be a number between 1 – 20. Now that we’ve confirmed the google analytics tag, the google analytics tracking ID, and DBD tag are included on the page, let’s confirm the DBD script is executing successfully. With the Developer Tools menu still open (Step 3), select the Network tab. Search for “distiltag” to locate the DBD tag on the page. The item shown is the script tag invocation. Verify the value in the Status column is 200 (success code). Search for “areyou” to locate the API calls made by the DBD tag. First, we see a kitten call and an event call, which collect metadata about the client and request, such as browser and biometric data used by Distil to determine whether or not the visitor is a bot. Following the kitten call and event call, there is another DBD API call. This call indicates the DBD tag was able to detect the GA tag running on the page, detect the GA running under the UA ID that was passed into it, and pass the data back into your GA account. Select the GA call (first item following the event call) and then select the Headers tab. Review the Request Payload to verify the correct UA ID and CID are properly included. For more information on Distil Bot Discovery, check out www.distilnetworks.com
Previous Video
OWASP Automated Threats Explained - Fingerprinting, Footprinting, and Vulnerability Scanning
OWASP Automated Threats Explained - Fingerprinting, Footprinting, and Vulnerability Scanning

Penetration testers as well as black hat hackers look for vulnerabilities in websites. Both groups use the ...

Next Video
Bot Defense for API & Mobile Apps
Bot Defense for API & Mobile Apps

This video explores Distil Networks' two latest protection products: Bot Defense for API and Bot Defense fo...