Reconcile Ignyte IQ with GA4
Ignyte IQ’s GA4-powered metrics — the Site Traffic section and any GA4-sourced tiles — pull directly from GA4. Most differences against GA4 itself reduce to date range, the GA4 property being read, or how GA4’s attribution settings are configured.
Step-by-step
Section titled “Step-by-step”-
Confirm the same GA4 property. Open the GA4 integration in Settings → Integrations and verify which property is connected. Mismatched properties produce wildly different numbers.
-
Match date ranges and time zones. GA4’s time zone is set at the property level. Confirm Ignyte IQ’s reporting time zone matches.
-
Match attribution settings on both sides. GA4’s Attribution settings (data-driven vs last-click, lookback window) determine which conversions Ignyte IQ pulls.
-
Compare a specific metric. Sessions, Conversions, and Revenue are the most direct comparisons. Check the ℹ️ panel on the Ignyte IQ tile for the exact GA4 metric being read.
-
If a session/conversion gap persists, check whether GA4’s data thresholding is hiding rows on the source side (GA4 may obscure small dimensions to protect user privacy).
What’s expected
Section titled “What’s expected”| Difference type | Expected? |
|---|---|
| Sessions match within ~1% | Yes |
| Conversions match within a few % | Yes |
| Conversion paths differ noticeably | Depends — GA4’s data-driven model can produce path-level differences |
| Platform-reported conversions differ massively from GA4 | Yes — this is platform attribution vs GA4 attribution, not a sync issue |
For why ad-platform numbers differ from GA4, see Why numbers don’t match.