Meta Ads · Status at source date: Newsletter archive
Meta updates transparency requirements for ad-buying solutions
Meta has updated its developer policies covering separate ad accounts and transparency for ad-buying solutions, with the transparency provisions taking effect on 3 February 2027. The updated Separate Ad Accounts policy continues to require that end advertisers be kept in distinct ad accounts, with an exception: ad-buying solutions implementing vendor_id and/or brand fields in their Product Catalogue and/or Pixel and CAPI integrations are exempt from the separate-account requirement, provided the fields are properly implemented, and other terms are met.
What changed
The Transparency provision moves to a reactive disclosure model. Ad-buying solutions must, upon the end advertiser's request, disclose the amount spent on Meta advertising on the advertiser's behalf: separate from fees: and the campaign configuration, settings, and post-campaign reporting using Meta terminology. Meta will not proactively provide this information unless required by law or unless a policy violation is identified.
Why it matters for advertisers
For you, this means agencies and ad-buying platforms operating consolidated client accounts must plan a 2026 review of vendor_id and brand field implementation, and prepare disclosure templates for the reactive transparency requirement. Particularly relevant for white-label and managed-service offerings, where end advertisers may not currently have visibility into platform-level reporting.
Perspective from the original PMC newsletter.Sources & contributor credit
- Newsletter coverage · Paid Media Collective newsletter
Original newsletter text, contributor labels and media for this update.
- Source referenced in newsletterMeta for Developers
Linked from the original newsletter. The source publication date has not been independently confirmed.
Original creator unverified
The original creator has not yet been verified. Newsletter curation and publication do not establish original authorship.
Attribution evidence and limitations
Full attribution review pending.
A source link alone does not establish original authorship.
Original image and video creators have not yet been verified.
- Published on this site
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.
Original newsletter text and archive evidence
Meta updates transparency requirements for ad-buying solutions
Meta has updated its developer policies covering separate ad accounts and transparency for ad-buying solutions, with the transparency provisions taking effect on 3 February 2027. The updated Separate Ad Accounts policy continues to require that end advertisers be kept in distinct ad accounts, with an exception: ad-buying solutions implementing vendor_id and/or brand fields in their Product Catalogue and/or Pixel and CAPI integrations are exempt from the separate-account requirement, provided the fields are properly implemented, and other terms are met.
The Transparency provision moves to a reactive disclosure model. Ad-buying solutions must, upon the end advertiser's request, disclose the amount spent on Meta advertising on the advertiser's behalf: separate from fees: and the campaign configuration, settings, and post-campaign reporting using Meta terminology. Meta will not proactively provide this information unless required by law or unless a policy violation is identified.
For you, this means agencies and ad-buying platforms operating consolidated client accounts must plan a 2026 review of vendor_id and brand field implementation, and prepare disclosure templates for the reactive transparency requirement. Particularly relevant for white-label and managed-service offerings, where end advertisers may not currently have visibility into platform-level reporting.
Source captured . No explicit first-contributor label was provided for this update.
