If you've installed and verified our tracking script but are not seeing the volume of profiles collected that you expect, consider the following factors that may be affecting data collection:
1. Low Website Traffic
The amount of data collected is directly proportional to your website’s visitor traffic. If your site has low traffic, fewer data points will naturally be collected.
Solution: Monitor your site’s traffic patterns to ensure that visitor levels align with your data expectations.
2. Geographical Limitations
Our tracking script is optimized to collect data from U.S.-based visitors only. If a large portion of your audience is outside the U.S., this will reduce the volume of data captured.
Solution: Review your audience's geographical distribution to confirm it aligns with the U.S. focus of our script.
3. Selective Identification Process
The script is designed to identify and collect data from approximately 20-30% of U.S. visitors, focusing on generating high-quality and relevant data. This may result in lower overall numbers.
Solution: Understand that this selectivity is intentional for data quality, but if you seek higher capture rates.
4. Server-Side Caching Issues
Server-side caching can sometimes prevent newly added scripts from functioning correctly or being immediately visible on your site. This can temporarily hinder data collection during the initial setup.
Solution: Clear your server cache or consult your hosting provider to ensure new scripts are updated and functioning properly.
5. WordPress Plugin Interference
Certain WordPress plugins, such as WP Rocket, which are used for caching and site speed optimization, may interfere with the tracking script by delaying updates. These plugins often cache pages, causing changes like the addition of the script to not immediately take effect.
Solution: Clear your WordPress plugin cache and adjust settings to allow the tracking script to update correctly. Regularly check for compatibility issues between plugins and your tracking script.
6. Script Function is Tied to Cookie Policy Acceptance
If you have tied the function of RB2B's tracking script to your user's acceptance of your cookie policy banner, this will greatly affect the ability of RB2B to identify visitors.
Solution: There are currently no jurisdictions within the United States that require visitors to first accept a cookie policy for RB2B to run, rather, that they just need to be notified that cookies are used on the site. Consider removing the control of the script from the user's acceptance of your cookie policy. Note: your own corporate policies may still require it. Ensure as well that you have updated your privacy policy and cookie banner per our guidelines.
Summary
To troubleshoot and resolve these issues:
Review your site’s traffic levels and audience demographics.
Confirm that your audience is primarily U.S.-based.
Check for server-side caching or plugin-related delays that might impact script updates.
Configure your caching plugins (if using WordPress) to ensure your tracking script is properly implemented and updated.
If the issue persists after checking these factors, contact support for further assistance.