FAQs

Why might there be discrepancies in EdgeTag data compared to other tracking methods?

There could be few reasons why discrepancies may occur: - The site is not completely covered in terms of website event code addition and hence user data is not captured on the site properly - There may be multiple sources firing on the same pixel causing discrepancies - Compare both sources data to server to server or browser to browser.

My ROAS in GA4 looks different from what Meta or Google Ads reports. Which is right?

All three are “right” within their own attribution model. GA4 uses data-driven attribution across channels, while Meta and Google Ads each take credit using their own models. The value of having all three populated is triangulation — when two or more agree that a channel is performing, you can scale with confidence.

Will this cause double-counting in GA4?

No. EdgeTag sends events to GA4 exclusively through the client-side data stream. Server-side events are routed to advertising platforms only. GA4 receives one copy of each event.

Does this affect my server-side data quality or match rates?

No. The client-side stream operates independently. Your server-side events to Meta, Google Ads, TikTok, and other platforms continue to flow through EdgeTag’s infrastructure with full match-rate optimization. Your media buyers’ signal quality is unaffected.

Can I use my existing GA4 property instead of creating a new one?

Yes. If your marketing team is comfortable sending EdgeTag’s client-side events directly to your production property, simply enter that property’s Measurement ID during plugin configuration. We recommend testing with a separate property first so you can compare data quality side-by-side before making the switch.

What if I already have a gtag.js snippet on my site?

Remove or disable it before activating EdgeTag’s client-side stream to prevent duplicate events. EdgeTag’s stream replaces the standard snippet entirely.

How quickly will my remarketing audiences recover?

Audience membership in GA4 is forward-looking — it builds from the moment events start flowing. Most teams see meaningful audience sizes within 7–14 days, depending on traffic volume and audience window length.