Data Discrepancies
Why numbers might differ between platforms
Updated 2024-12-20
Understanding Data Discrepancies
It's normal for numbers to vary slightly between Glarify, GSC, and GA4.
Why Numbers Differ
Measurement Methods
| Platform | Measures | Method |
|---|---|---|
| GSC | Clicks | Server-side, Google's servers |
| GA4 | Sessions | Client-side JavaScript |
| Glarify | Both | API aggregation |
Data Processing
- GSC: 24-48 hour processing delay
- GA4: 24-48 hours for standard reports
- Glarify: Syncs based on your schedule
Bot Filtering
Each platform filters bot traffic differently:
- GSC has aggressive bot filtering
- GA4 filters based on known patterns
- Edge cases may be counted differently
Common Scenarios
Clicks vs Sessions
Why they differ:
- User clicks but doesn't wait for page load
- JavaScript fails to execute
- Multiple clicks in single session
- Bot clicks filtered by GA but not GSC
Expected variance: 10-30%
Today's Data
Why it's incomplete:
- GSC data is 2-3 days behind
- GA4 standard reports have 24-48hr lag
- Only GA4 real-time is current
Historical Data Changes
Why past data changes:
- Google reprocesses historical data
- Spam filtering applied retroactively
- Bot detection improvements
Best Practices
For Reporting
- Use the same source for trend comparisons
- Don't try to reconcile exact numbers
- Focus on trends, not absolutes
- Document which source you're using
For Analysis
- Use GSC for search visibility
- Use GA4 for user behavior
- Use Glarify for combined insights
For Stakeholders
- Explain data source differences upfront
- Show trends rather than absolute numbers
- Be consistent in which metrics you report