When Must Ad Agencies Disclose Spend to Advertisers Under Meta's New Policy?

Starting February 3, 2027, Meta's updated Developer Policy requires any ad-buying platform or agency managing Meta ad campaigns on an advertiser's behalf to disclose, on the advertiser's request, the actual amount spent on Meta advertising separate from any fees charged, the fee structure itself, and the campaign's configuration, settings, and reporting using Meta's own terminology.

The Core Obligation

Multiple outlets covering Meta's April 28, 2026 policy announcement describe the same requirement: when an end advertiser asks, the platform or agency buying ads on their behalf must break out real Meta ad spend from markups and management fees, explain how those fees are structured, and report campaign settings in terms that match Meta's own platform — not a repackaged or relabeled version that obscures what's actually running or how much of the budget reached Meta itself.

Why Meta Is Requiring This

The rule targets a long-standing opacity problem in agency and platform-managed ad buying, where an advertiser might be quoted a blended number that mixes media spend with hidden markup, making it hard to know what Meta itself is actually charging. Forcing disclosure in Meta's own terminology also prevents platforms from using custom labels that make direct comparison difficult across different vendors managing the same advertiser's budget.

There's a Carve-Out for Shared Account Structures

Businesses that manage a high volume of advertisers through a single consolidated ad account can continue operating that way, provided they implement vendor ID and/or brand fields in their integrations so individual advertiser spend and campaigns remain distinguishable within the shared structure, satisfying the disclosure requirement without restructuring their whole account setup.

A Caveat on the Exact Section Number

Coverage of this policy change isn't fully consistent on which Developer Policy section carries the spend-disclosure duty — some reporting attributes it to section 10.6.a, while other coverage attributes it to section 10.5, with 10.6.a instead described as governing ad account structure for multiple end advertisers. The February 3, 2027 effective date is consistent across every source that reported it; agencies should confirm the exact section numbering against Meta's own developer policy documentation rather than relying on secondary summaries alone.

What Agencies and Platforms Should Do Before February 2027

Build the reporting capability now rather than waiting: confirm your systems can isolate true Meta media spend from your fees, map your account structure to support vendor ID or brand field tagging if you run multiple advertisers through one account, and prepare a standard disclosure format advertisers can request without a custom data pull every time.

Bottom Line

If you're an agency or SaaS platform buying Meta ads on behalf of clients, build spend-transparency reporting into your systems well before February 3, 2027 — and verify the exact policy section against Meta's developer documentation rather than assuming any one outlet's numbering is final.

Sources: PPC Land, "Meta Forces Ad Spend Disclosure to Advertisers Starting February 2027"; Social Samosa, "Meta Revises Transparency Policies for Advertising Partners"; Prooflytics compliance guide on Meta Developer Policy 10.5 and 10.6.a.