Visits Are Missing or Lower Than Expected
Diagnose missing visits, page views, and sudden changes in tracking coverage.
Use this guide when visits or page views are missing, lower than expected, or dropped after a website change.
1. Identify the scope
Determine whether the issue affects:
- Every page or only specific landing pages
- Every visitor or a particular browser, device, or region
- All traffic or one campaign or channel
- A specific date when a site, domain, checkout, or consent change occurred
2. Check the affected pages
Confirm that the Northbeam Pixel loads on every affected page, including:
- Alternate landing pages
- A/B test variants
- Subdomains and newly launched domains
- Product and checkout pages
Open Pixel and Event Tracking to review your setup.
3. Test the complete landing URL
Open an affected ad's final URL and confirm that:
- It lands on the expected tracked domain.
- Northbeam and UTM parameters remain after every redirect.
- The parameters are not removed when the visitor moves to another required domain.
Use the account-specific parameters shown in the UTM Guide.
4. Review recent changes
Check whether the drop began after changes to your:
- Website theme or tag manager
- Cookie-consent flow
- Domain, subdomain, or DNS
- Landing-page builder
- Checkout or payment flow
Understand the comparison
A Northbeam Visit is not the same as an ad-platform click or an individual page view. A visit generally represents a session, which ends after 30 minutes of inactivity. Northbeam also filters bots and may load at a different point than another analytics tool.
If the pixel works on some pages but not others, fix page coverage before comparing totals. For order-level tracking, continue to Troubleshooting Pixel Tracking.
Updated 18 days ago