Let’s say that you have made a configuration change in the portal (adding a page name rule, for example) and already waited the recommended amount of time for those changes to take effect, but new data coming in does not seem to be following the new rule. One of the first steps of troubleshooting is to verify that your change made it into the btt.js tag, and that it looks correct. You can verify that by following the steps below:
- Open a website that is currently tagged with btt.js
- Open the developer tools (right-click on the page > Inspect, or F12, or Ctrl+Shift+i)
- Click on the "Network" tab (might be under the >> icon if your developer tools window is too small)
- Click on btt.js
- Select "Preview" in the popup menu (this may be named differently depending on your browser)
- Press Ctrl+F and search for the configuration change you made
- Verify that the configuration change can be found in the tag and that it looks correct
For example, let’s say we added a page name rule to name the page “Industry Benchmarks” if the URL contains “/industry-benchmarks”. In the screenshot below, we can see that the new rule is indeed in the tag and that the formatting looks great. In some cases, especially when copy/pasting from other sources, there might be whitespace or some special characters that are messing up the rule (for example, the rule could instead have pS: “/industry-benchmarks “ and URLs do not contain whitespace so searching for the URL to contain that substring will never work).
*Pro tip: When you click on the “Preview” tab to open btt.js, the entire tag’s code might be displayed on one line instead of in the pretty-printed format shown in the screenshot above. If you see everything on one line, then we recommend clicking the {} symbol at the bottom of the window (displayed to the left of the “20 characters selected” text in the screenshot above” to pretty-print the file’s contents. This is purely for convenience and does not make any changes.