Overview

Meta Events Manager may display data quality warnings for your Pixel or Dataset, including an Affected Ad Spend amount. These warnings are based on diagnostics and recommendations Meta has identified for the events and data sources connected to your account.

The specific diagnostics contributing to these warnings can vary between accounts. Some may be related to event configuration, parameters, deduplication, domains sending data, or other aspects of your Meta setup. Because each account and implementation is different, individual diagnostics should be reviewed before determining their cause or potential impact.

This article explains how Meta's data quality warnings work, what Affected Ad Spend represents, and how to review the diagnostics and recommendations associated with your account.

What Are Data Quality Warnings?

Meta uses data quality diagnostics to evaluate the events being received by your Pixel or Dataset and identify potential opportunities to improve the accuracy and completeness of your event data. These diagnostics can appear regardless of how events are being sent, including through Shopify's native Meta integration, Google Tag Manager implementations, server-side tracking platforms, and Elevar.

The diagnostics and recommendations shown will depend on the data Meta receives for your individual account. Some recommendations may be straightforward to resolve, while others may require a closer review of your tracking implementation to determine the cause and appropriate next steps.

What “Affected Ad Spend” Means:

Affected Ad Spend is Meta's estimate of the amount of advertising spend potentially impacted by the data quality issues or recommendations it has identified. The amount shown can vary depending on factors such as your overall ad spend and the significance of the individual diagnostics Meta has identified. Because of this, the potential impact of a particular recommendation will vary from one account to another.

The goal should be to review and resolve as many applicable diagnostics and recommendations as possible. As these items are addressed, the amount of Affected Ad Spend should decrease. According to Meta, if all applicable issues and recommendations have been resolved, Affected Ad Spend should no longer display. If Affected Ad Spend continues to display after all identified diagnostics and recommendations have been resolved, the warning may need to be reviewed by Meta Support for your individual account.

How Individual Diagnostics Affect Data Quality:

Meta may provide different diagnostics, action items, and recommendations depending on the data it receives from your account. These recommendations are intended to improve the accuracy of the data Meta can use for measurement and ad optimization. The cause and significance of each diagnostic can vary. For example, a warning may be related to:

• Event parameters or values that Meta considers inconsistent.
• Event ID coverage or deduplication between browser and server events.
• Domains Meta has detected sending data to your Pixel or Dataset.
• Tags or events firing from additional pages or domains.
• Other event configuration or data quality recommendations identified by Meta.

These examples are not an exhaustive list. Always review the specific diagnostic and its associated recommendation before determining what is causing the warning.

Event ID Coverage and Deduplication Keys:

Meta uses deduplication to identify when a Pixel (browser) event and a Conversions API (server) event represent the same customer action. This is typically accomplished by sending a matching Event ID with both versions of the event. If Meta identifies an issue with Event ID coverage or deduplication keys, review the specific diagnostic and the events affected.

These warnings can sometimes indicate an issue with the tracking configuration, but the cause cannot be determined from the warning alone. Reviewing the affected events and implementation is necessary to determine whether changes should be made to improve deduplication.

New Domains Sending Data

Meta may also identify new or unexpected domains sending data to your Pixel or Dataset. The domains shown and the reason they appear will be specific to your implementation and customer journey.

If an unfamiliar domain appears, review where your Meta tags are firing and whether events from that domain are expected. Depending on your setup, additional domains may appear because tags are firing during a checkout or payment flow, through a third-party service, during testing, or in another environment where your Meta Pixel is present.

The presence of one of these domains does not automatically indicate a tracking problem. However, it should be reviewed to confirm whether events are expected to fire from that location and, if so, whether the events follow Meta's recommended implementation practices.

Why These Warnings Occur

Data quality warnings can occur for a variety of reasons, and the exact cause will depend on the events, parameters, domains, and integrations associated with an individual account.

For example, Meta may flag an event when it detects differences between the information it expects and the information it receives. This does not always mean the underlying event or value is incorrect, but the discrepancy can still trigger a diagnostic.

One example is Meta's Currency Mismatch diagnostic. In some configurations, the numeric values sent for an event may differ because of currency conversion even though they ultimately represent the same value. Meta's diagnostic logic is designed to identify genuine inconsistencies, so differences between the values can still trigger a warning and contribute to Affected Ad Spend.

Similarly, additional domains, deduplication issues, or other event configuration differences may generate recommendations. However, the presence of these scenarios does not automatically explain a warning. Each recommendation should be evaluated based on the customer's specific implementation.

What To Do If You See This Warning

If Meta displays a Low Data Quality or Affected Ad Spend warning, start by reviewing the diagnostics, action items, and recommendations associated with your Pixel or Dataset in Meta Events Manager. Meta may surface these recommendations in different areas of Events Manager. Some may appear alongside the Affected Ad Spend warning, while others may be available within the Actions or diagnostics areas for the affected events.

How to Review Your Account:

• Navigate to Meta Events Manager and select the affected Pixel or Dataset.
• Review any diagnostics, action items, or recommendations Meta has provided.
• Open each recommendation to identify the affected event, parameter, domain, or configuration.
• Review whether the recommendation applies to events managed by Elevar or another data source connected to your Pixel or Dataset.
• Address as many applicable recommendations as possible to improve the accuracy and completeness of the data available to Meta. Continue monitoring the Affected Ad Spend amount as recommendations are resolved.

If a diagnostic appears to involve events managed by Elevar, or you are unsure whether your Elevar implementation is contributing to the warning, contact the Elevar Support team. Provide the specific diagnostic, affected events, and any recommendations displayed by Meta so the team can review your implementation and help determine the appropriate next steps.

If all identified diagnostics and recommendations have been resolved but Affected Ad Spend continues to display, contact Meta Support to have the warning reviewed for your individual account. We also recommend sharing this scenario with Elevar Support so we can track whether similar behavior is occurring across multiple customers.