Analytics Not Tracking
Diagnose and fix missing analytics data, tracking problems, and visibility issues on your campaigns.
Analytics not showing data? This guide helps you diagnose and resolve common tracking problems so you can monitor your campaign performance accurately.
Understanding Analytics Tracking
Firebuzz collects analytics data only when your campaign is published. The system separates Preview and Production environments, and data aggregation may take a few minutes to appear in your dashboard.
Real-time data updates every 30-60 seconds. Historical charts may take 10-30 minutes to aggregate. If you just published your campaign, wait a few minutes before expecting data.
Common Issues
No Data Appearing in Dashboard
Your analytics dashboard shows no visitors or events even though your campaign is published.
This typically happens when viewing the wrong environment, when the campaign isn't actually published, or when insufficient time has passed for data to aggregate.
Solution:
- Go to Analytics in your campaign
- Verify your campaign status is Published or Scheduled
- Check the environment toggle at the top of the analytics page
- Select Preview if you published to Preview, or Production if you published to Production
- Open your published landing page in a new incognito window
- Complete a test visit by browsing the page for a few seconds
- Wait 2-3 minutes, then click Refresh in the analytics toolbar
Use incognito mode when testing to avoid cookie-based tracking that might interfere with accurate data collection.
Preview Data Not Showing
You published your campaign in Preview mode but don't see any preview analytics.
Preview and Production analytics are completely separate. You must explicitly select the Preview environment to view preview data.
Solution:
- Navigate to Analytics
- Click the environment toggle in the analytics toolbar
- Select Preview from the dropdown
- Verify your campaign status shows Preview
- Visit your preview URL to generate test traffic
- Wait 2-3 minutes and refresh the analytics page
Preview mode is designed for testing. Only Production data reflects real visitor traffic from your published campaigns.
Ad Blockers Preventing Tracking
Some visitors aren't appearing in your analytics data.
Ad blockers, browser privacy settings, and tracking prevention tools block analytics scripts. This affects all analytics platforms, not just Firebuzz.
Solution:
- Understand that no analytics platform captures 100% of visitors
- Disable your own ad blockers when testing analytics
- Use incognito mode without browser extensions for clean tests
- Focus on relative comparisons rather than absolute numbers
- Trust that A/B test comparisons and conversion rate trends remain valid
Firebuzz uses first-party tracking through our own infrastructure, which is less susceptible to blocking than third-party trackers like Google Analytics.
Self-Visits Inflating Numbers
Your own test visits are counting toward your analytics data.
Testing and development visits can inflate visitor counts, especially in the early stages of a campaign.
Solution:
- Publish to Preview for all testing activities
- Only publish to Production when ready for real traffic
- Use the Preview environment to verify analytics without affecting production data
- Focus on production metrics for actual campaign performance
- Compare conversion rates and trends rather than absolute visitor counts
Real-Time Shows Activity But Historical Charts Are Empty
The real-time tab displays active visitors, but historical charts remain empty.
Historical data requires aggregation time. Real-time data is immediate, but charts and trends update on a periodic schedule.
Solution:
- Wait 10-30 minutes for historical data to aggregate
- Check your date range selector at the top of the analytics page
- Select Last 24 hours or Last 7 days to include recent data
- Click Refresh to force a data reload
- Verify traffic is actually occurring by checking the real-time tab
Conversions Not Tracking
Page views appear in analytics but conversion events are missing.
Conversions only track when a primary goal is configured and when visitors complete the specific conversion action.
Solution:
- Go to Settings in your campaign
- Navigate to the Goals section
- Verify you have configured a Primary Goal
- Test the conversion by completing the action yourself (submit a form, click a button, etc.)
- Wait 3-5 minutes for conversion data to appear
- Check that your conversion event matches the defined goal exactly
Custom conversion events require proper implementation. Form submissions and button clicks automatically track, but custom events need explicit tracking code.
Analytics Environments
Firebuzz separates analytics into two environments to prevent test data from polluting your production metrics.
| Environment | Purpose | When Data Appears |
|---|---|---|
| Preview | Testing, QA, and development visits | When campaign is in Preview status |
| Production | Real visitor traffic from published campaigns | When campaign is fully Published |
Always verify you're viewing the correct environment when reviewing analytics data.
Debugging Checklist
Use this checklist to systematically diagnose tracking problems:
- Verify publish status — Campaign must be Published or in Preview
- Check environment selection — Toggle between Preview and Production
- Generate test traffic — Visit the published page in a new incognito browser
- Wait for data sync — Allow 2-3 minutes for data to appear
- Disable ad blockers — Turn off blocking extensions when testing
- Refresh analytics page — Force reload to fetch latest data