Meta forces ad spend disclosure to advertisers starting February 2027
Meta updates Developer Policy 10.5 and 10.6a, requiring ad-buying solutions to disclose spending and campaign data to end advertisers from February 3, 2027.
Social
Meta today published an update to its Developer Policies governing ad-buying solutions, introducing a formal obligation for third-party platforms and agencies to disclose advertising spend and campaign configuration data to end advertisers upon request. The announcement, dated April 28, 2026, was authored by Nicholas Medina and published on the Meta for Developers blog. The transparency requirement under section 10.6.a takes effect on February 3, 2027.
The changes cover two numbered provisions in Meta's Developer Policy framework. Section 10.5 governs how ad accounts must be structured when multiple end advertisers are managed by a single developer or platform. Section 10.6.a, which is entirely new in its current form, introduces the disclosure obligation. Both sections carry compliance weight for the broad ecosystem of agencies, reseller tools, and ad-tech platforms that buy advertising on Meta on behalf of clients.
What section 10.5 now requires - and the technical alternative
Developer Policy 10.5 has existed in prior form for some time, but the April 28 update clarifies both its requirements and the conditions under which developers can avoid maintaining separate ad accounts altogether.
According to the updated documentation, the rule reads: "Don't combine multiple end advertisers or their Meta business assets in the same ad account, unless you meet the requirements described here or as otherwise approved by Meta in writing." Meta's stated rationale is direct: keeping end advertisers separated makes it easier to track ownership and accountability for ad content, spend, and data, and limits enforcement disruptions when one advertiser's account requires action.
The practical problem this provision solves is contamination - when a violation by one advertiser within a shared account triggers enforcement that affects every other advertiser in that account. Separate accounts confine risk.
However, Meta simultaneously formalizes a technical alternative for businesses managing high volumes of end advertisers. According to the Separate Ad Accounts Policy documentation, developers that implement a vendor_id and/or brand field in their Product Catalog, and/or in their Meta Pixel and Conversions API (CAPI) integrations, will be considered compliant with Developer Policy 10.5 - provided they properly implement such fields and remain compliant with all Meta terms and conditions. Meta explicitly reserves the right to revoke this alternative at any time, at its sole discretion, if doing so is deemed necessary to protect Meta, its users, or the integrity of its products.
The required signals are vendor_id and/or brand. Developers must include the chosen signal in at least one of the following surfaces: Product Catalog data, or Meta Pixel/CAPI event data. The flexibility here matters for large-scale operators. A platform managing tens of thousands of merchant advertisers - common in retail and performance marketing verticals - faces genuine operational difficulty in creating a distinct ad account for every end advertiser. The vendor_id/brand path allows such platforms to preserve a consolidated account structure while still providing Meta with the attribution data needed to isolate each advertiser's activity.
The Conversions API infrastructure has been a growing focus for Meta across 2025 and into 2026. The IAB documented in October 2025 that two-thirds of advertisers reported improved return on ad spend after CAPI implementation, a figure Meta has cited in its own product communications.
The new transparency obligation under section 10.6.a
Section 10.6.a is the more consequential change for agencies and managed service providers. The full policy text, effective February 3, 2027, states:
"If requested by an end advertiser, you must disclose to such end advertiser (i) the amount that you spent on Meta advertising on behalf of such end advertiser, separate from your fees, and the associated fee structure you charge, and (ii) the campaign configuration, campaign settings, and/or post-campaign reporting for the end advertiser's Meta ad campaign, using Meta terminology."
The policy then adds a significant operational caveat: "Unless required by law, we do not disclose this information proactively." Meta clarifies that if the company identifies or suspects a violation of this policy, it may, upon the end advertiser's request, provide the disclosures outlined in points (i) and (ii). Meta states it may - but is not obligated to - notify the developer or platform if such a disclosure occurs.
Three structural elements of this provision deserve attention. First, it is reactive, not proactive. Advertisers must actively request the information; there is no obligation to surface it automatically. Second, the spend figure must be disclosed separately from the fees the ad-buying platform charges - meaning the raw media cost, before any markup or margin, must be made available on request. Third, campaign reporting must use Meta terminology specifically, not proprietary metrics or platform-specific labels that could obscure performance.
The requirement to use Meta terminology is precise. An agency that reports campaign results using its own dashboard labels, without reference to Meta's native metric names, would not satisfy the policy if an advertiser requested the official Meta campaign data. Advertisers asking for reporting will receive information framed in the vocabulary of Meta Ads Manager.
Why the timing matters
The February 3, 2027 effective date gives developers and ad-buying platforms roughly nine months from the date of announcement to modify their systems, client agreements, and reporting workflows. That is a meaningful window given that compliance requires both technical changes - ensuring spend data is retrievable at the advertiser level - and commercial changes, such as updating contracts to reflect the new disclosure obligations.
The April 28 announcement explicitly frames these updates as a response to feedback from the advertiser community. Meta states the changes are "intended to clarify expectations and maintain alignment with industry best practices." That framing suggests the obligation existed informally in practice - clients have long asked agencies for spend transparency - but the formal policy codification gives advertisers a direct policy basis for demanding it.
The context is not trivial. Meta's advertising business generated $58.1 billion in revenue during the fourth quarter of 2025 alone, with full-year 2025 advertising revenue reaching $196.2 billion. Much of that revenue flows through third-party intermediaries - agencies, resellers, and software platforms - that manage campaigns on behalf of end advertisers. The scale of intermediated spend makes spend transparency a structural issue rather than an edge case.
There is additional backdrop. A class action lawsuit filed on April 21, 2026, by the Consumer Federation of America alleged that Meta has systematically profited from fraudulent advertising. The complaint separately described a system of Chinese advertising resellers that receive approximately 10% commissions from Meta and benefit from delayed enforcement reviews. While section 10.6.a does not directly address fraud, greater spend visibility for end advertisers creates conditions under which anomalous billing or inflated reporting would be harder to sustain undetected.
Former Meta employee Samujjal Purkayastha filed a whistleblower complaint in August 2025 alleging that Shops ads return on ad spend metrics had been inflated between 17% and 19% due to Meta counting shipping fees and taxes as revenue in its calculations. That allegation, combined with the CFA lawsuit, forms a broader context in which Meta's decision to codify spend disclosure obligations takes on additional significance for the marketing community.
The account structure requirement in practice
The underlying logic of the 10.5 account structure requirement is about audit trails. When enforcement action is required against one end advertiser - for policy violations, fraud, or other issues - a shared account creates collateral damage for every other advertiser in that account. The separation requirement, whether achieved through distinct accounts or through the vendor_id/brand signal implementation, creates a technical record that allows Meta to attribute activity to specific advertisers rather than to the broader account.
For developers building ad-buying solutions, the compliance path now has two distinct tracks. Track one is structural separation: each end advertiser gets its own Meta ad account, which provides clean attribution by default. Track two is signal implementation: a single account can hold multiple end advertisers, but the vendor_id or brand fields must be populated in either Product Catalog data or Pixel/CAPI event data to provide the same attribution at the data level.
The signal-based approach requires careful implementation. According to the documentation, proper implementation of the fields is a condition of compliance - not just the presence of the fields, but their correct use. Meta does not detail in the public documentation what constitutes improper implementation, though it retains discretion to assess compliance.
Meta's October 2024 Platform Terms update, which took effect February 3, 2025, had already introduced clearer requirements on transparency for ad-buying solutions. The April 28 changes go further by specifying exactly what must be disclosed, how spend must be disaggregated, and what terminology must be used in reporting.
What ad-buying solutions must prepare
Ad-buying platforms that manage campaigns for multiple end advertisers face a compliance checklist that spans technical infrastructure, data architecture, and client-facing reporting.
On the technical side, platforms must be able to retrieve the raw Meta spend for each end advertiser independently of any fee layers applied on top. This requires that spend data be tracked and stored at the advertiser level within the platform's own infrastructure, not just at the aggregate account level. For platforms using consolidated ad accounts under the vendor_id/brand path, this means the signal data must be mapped to spend records so that a per-advertiser spend figure can be generated on demand.
On the reporting side, platforms must be able to produce campaign configuration, settings, and post-campaign reporting in Meta terminology. That likely requires access to Meta's raw API data rather than derived or translated metrics. Developers who have built proprietary reporting layers will need to either expose the underlying Meta data on request or build a translation layer that maps their internal metrics back to Meta's native names.
The disclosure is reactive - triggered only when an end advertiser requests it. But platforms must be architected to fulfill that request accurately and promptly. There is no guidance in the published documentation about response time expectations.
The marketing community tracking these changes through PPC Land has noted a consistent pattern of Meta policy updates that narrow intermediary flexibility while increasing end-advertiser rights - a trajectory that also includes the advertiser verification requirements for Thailand announced in October 2025 and the SEBI verification requirements for India introduced ahead of July 2025.
The transparency requirements for ad-buying solutions fit that pattern. End advertisers gain a formal right to see what was spent on their behalf and how their campaigns were configured. Intermediaries must be prepared to provide that information, disaggregated and in Meta's own vocabulary, when asked.
Industry context: the push for spend transparency
The debate over spend transparency between agencies and clients is not new. In traditional media buying, markups and undisclosed rebates have been the subject of industry audits and legal proceedings for decades. Digital advertising introduced new layers of opacity - trading desks, programmatic intermediaries, and consolidated platform accounts - that made it harder for advertisers to verify what share of their budget reached actual media.
Meta's section 10.6.a addresses the narrow question of Meta-specific spend. It does not address markups on other platforms, cross-platform fee structures, or the broader question of whether the reported results accurately reflect the value delivered. But by requiring that the raw Meta spend figure be separable from fees, it gives advertisers a floor - at minimum, they can determine what was actually paid to Meta versus what they paid to the agency or platform in total.
Google introduced its own transparency update in 2025 requiring the display of payer names for verified advertisers in the Ads Transparency Center and My Ad Center. Meta's approach operates at the developer policy level rather than through public-facing disclosure tools, making it a behind-the-scenes obligation rather than a visible badge on the ad unit itself.
The Media Rating Council's draft Digital Advertising Auction Transparency Standards, released in September 2025, identified transparency, disclosure, and reporting as central concerns across display, video, social, and retail media. Meta's 10.6.a aligns with that directional pressure, though it operates through contractual developer policy rather than industry standard-setting.
Timeline
- October 15, 2024 - Meta unveils comprehensive updates to Platform Terms and Developer Policies, covering ad-buying solutions transparency; effective February 3, 2025. PPC Land coverage
- November 15, 2024 - Meta announces mandatory user data deletion protocol under Platform Terms Section 3(d)(i). PPC Land coverage
- February 3, 2025 - Updated Meta Platform Terms and Developer Policies take effect
- August 20, 2025 - Former Meta product manager files whistleblower complaint alleging Shops ads ROAS inflated 17-19% through inclusion of shipping fees and taxes. PPC Land coverage
- September 2025 - Media Rating Council publishes draft Digital Advertising Auction Transparency Standards covering social, display, video, and retail media. PPC Land coverage
- October 27, 2025 - Meta expands advertiser verification requirements for campaigns targeting Thailand. PPC Land coverage
- November 6, 2025 - Reuters reports Meta internally projected 10% of 2024 revenue from scam ads; Meta charged suspected fraudsters through penalty bids. PPC Land coverage
- January 28, 2026 - Meta reports Q4 2025 advertising revenue of $58.1 billion, full-year 2025 total reaches $196.2 billion. PPC Land coverage
- April 15, 2026 - Meta announces AI-powered Meta Pixel updates and one-click Conversions API setup, directly relevant to the vendor_id/brand compliance path under 10.5. PPC Land coverage
- April 21, 2026 - Consumer Federation of America files class action against Meta over scam advertising, citing agency account structures and commissions. PPC Land coverage
- April 28, 2026 - Meta publishes Developer Policy update introducing section 10.6.a transparency obligation and formalizing the vendor_id/brand alternative to separate ad accounts under 10.5
- February 3, 2027 - Section 10.6.a transparency requirement takes effect; ad-buying solutions must disclose raw Meta spend, fee structure, and campaign data to end advertisers upon request
Summary
Who - Meta Platforms, through its developer relations team, is the issuing party. The policies apply to all developers and companies that build ad-buying solutions using Meta's advertising infrastructure, including agencies, resellers, software platforms, and managed service providers that purchase Meta advertising on behalf of end advertisers.
What - Meta updated two Developer Policy sections. Section 10.5 continues the requirement to keep end advertisers in separate ad accounts or, alternatively, to implement vendor_id and/or brand signals in Product Catalog data or Meta Pixel/CAPI event data. Section 10.6.a, new and effective February 3, 2027, requires ad-buying platforms to disclose - upon request - the raw Meta spend on behalf of each end advertiser (separate from fees), the associated fee structure, and campaign configuration and reporting using Meta terminology.
When - The announcement was published on April 28, 2026. Section 10.5 is in effect. Section 10.6.a takes effect on February 3, 2027, giving developers approximately nine months from the announcement date to prepare.
Where - The policies apply globally to all developers building on Meta's platform. The disclosures they require operate between the ad-buying platform and the end advertiser, not as public-facing information. Enforcement operates through Meta's Developer Policy framework.
Why - Meta states the updates reflect feedback from the advertiser community and are intended to clarify expectations and align with industry best practices. The broader context includes sustained pressure on advertising transparency - from regulatory bodies, industry standards groups, and civil litigation - as well as concerns about how intermediated ad spending is reported to the brands and businesses that ultimately fund it.