On August 6, 2026, Meta silently deprecated three critical reporting breakdowns — device, hourly, and frequency — across both the Marketing API and Ads Manager. The change was not announced via changelog, email, or error message. Instead, the API continues to return HTTP 200 responses, and Ads Manager renders reports with zeroed rows, creating the illusion of normal operation while data is missing.

Technical Manifestations

Media buyers observed dashboards showing mobile impressions collapsing to zero despite active delivery. Combined queries, such as device by placement or device by age, also fail, returning empty datasets. This failure mode is particularly dangerous because it mimics a performance drop rather than a reporting deprecation, misleading operators into misdiagnosing campaign health.

Operational Impact

The absence of device-level data disrupts creative diagnostics, mobile share analysis, and hook testing. Hourly breakdowns, previously used for dayparting and bid rule inputs, now return blank outputs, undermining time-based optimization. Frequency data, essential for enforcing caps and saturation analysis, is no longer accessible unless accounts had explicitly opted in before the cutoff date. There is no retroactive opt-in path, leaving many advertisers permanently without these breakdowns.

Community Signals

Affiliate forums and PPC communities reported widespread confusion, with operators initially suspecting delivery anomalies or auction instability. Reddit threads in r/facebookads and STM Forum discussions highlighted the silent nature of the change, emphasizing the risk of misinterpreting zeroed reports as campaign failure. Several agencies confirmed that client dashboards across US and LATAM markets were affected simultaneously, reinforcing that this was a systemic deprecation rather than isolated account issues.

Practical Consequences

• — Device-level optimization workflows are compromised, forcing reliance on aggregate placement data.
• — Hourly bid adjustments and dayparting strategies cannot be validated against fresh delivery signals.
• — Frequency-cap enforcement becomes guesswork, increasing the risk of oversaturation and wasted spend.
• — Automated reporting pipelines may silently propagate incorrect datasets, skewing month-end performance summaries.

Root Cause Transparency

Meta has not disclosed the rationale behind the deprecation. The root cause remains undisclosed, and no official documentation has been updated to reflect the removal. The silent rollout underscores the need for independent anomaly detection and per-account audits before reporting cycles.

Sources

Primary confirmation via Mintec Blog [https://metastatus.com/] and corroborated by community reports on StatusGator and Reddit.