Overview

Meta Events Manager may display several data quality warnings for your Pixel or Dataset, including an Affected Ad Spend banner, Event ID Coverage or Deduplication Key warnings, and a list of New Domains Sending Data. Because these warnings often appear together, and sometimes include a dollar amount tied to "affected ad spend", they can seem alarming. In most cases, however, these warnings are not caused by Elevar and do not indicate that your Meta tracking is broken. This article explains what these warnings mean, why they occur, and how to verify that your Elevar-managed tracking is functioning as expected.

What Are Data Quality Warnings?

Meta uses data quality diagnostics to evaluate the events being received by your Pixel or Dataset. These diagnostics help identify situations where Meta has incomplete information or cannot fully evaluate incoming events. These warnings are generated by Meta and can appear regardless of how your events are being sent, including Shopify's native Meta integration, Google Tag Manager implementations, Other server-side tracking platforms, and Elevar. These diagnostics evaluate all data sources connected to your Meta Pixel or Dataset, they should not be interpreted as an indication that a specific platform is causing the warning.

What “Affected Ad Spend” Means:

This figure is Meta’s own estimate of ad spend tied to events it has flagged as lower quality by its internal scoring, for reasons ranging from missing parameters to signal mismatches across all connected sources for that pixel or dataset, not just the connection coming from Elevar. It is a diagnostic estimate, not a confirmed loss of performance, and the same banner appears on pixels using Shopify’s native integration, custom GTM builds, or other server-side platforms.

Additionally, this number scales with overall ad spend, the more a brand spends on Meta, the larger the affected ad spend figure will typically look, even if the underlying percentage of flagged events stays the same. A bigger dollar or euro amount on its own doesn’t mean the issue got worse, it often just reflects a bigger media budget.

What Event ID Coverage and Deduplication Keys Are:

Meta deduplicates a Pixel (browser) event and a CAPI (server) event that represent the same customer action by matching a shared identifier, most commonly the Event ID. The “coverage rate” shown reflects what percentage of events include a usable dedupe key on both sides. A coverage rate below 100% does not necessarily mean events are missing or duplicated, it means Meta cannot always confirm a browser and server event are the same action, which can happen for reasons unrelated to any specific tracking vendor, including third-party redirects and non-storefront traffic reaching the pixel.

What “New Domains Sending Data” Means:

The list shows every domain Meta has ever seen firing an event tied to your pixel or dataset, not just your storefront. Meta’s domain detection casts a wide net by design, it flags anything that touched the pixel code at any point, including pages your customers pass through during checkout, links your emails point to, or tools your team has used for testing.

A domain showing up here does not mean tracking was installed there, only that a browser loaded the pixel while on that domain at some point.

Why These Warnings Occur

We’ve reviewed this pattern across a wide range of implementations, on Shopify stores using Elevar, stores using other tracking vendors, and stores using no third-party server-side tool at all, both before and after Elevar was deployed.

The same domains and coverage patterns show up consistently, which tells us this is inherent to how Meta’s own tooling works, not something specific to Elevar’s setup. Common, harmless sources we see flagged include:

What To Do If You See This Warning

Meta doesn’t explicitly label these warnings as environmental noise, but our review across many brands shows this consistently, well before and independently of Elevar’s involvement. It’s very unlikely this reflects a gap in your Elevar-managed tracking specifically.

Verify Your Core Tracking Is Healthy:

The most reliable way to confirm your Elevar-managed data isn’t the source of the warning is to check the metrics tied to your actual storefront domain rather than the aggregate banner.

How to check:

• Navigate to Meta Events Manager and open your pixel or dataset.
• Under Event Deduplication, review the Event ID coverage rate for your Purchase and key funnel events.
• Under Actions, open the New Domains Sending Data list and confirm your storefront domain (for example, yourdomain.com) is present and reporting normally.

What to look for:

For the New Domains list specifically, cross-check any unfamiliar entries against the table above. Payment redirect domains, webmail clients, link trackers, and testing tools can be safely reviewed and ignored, or added to your allowlist if you’d like them out of the active list going forward. This is routine Meta account housekeeping, not evidence of a tracking defect.

If, after checking these two areas, your storefront’s own coverage and event accuracy look strong, that confirms the broader “affected ad spend” banner reflects Meta’s account-wide diagnostic, not a problem with the events Elevar is sending on your behalf.