The update to the Developer Policies for ad-buying solutions focuses on enhancing Ads transparency and account structure to better align with industry best practices and advertiser feedback. The key changes emphasize clearer expectations for advertisers and developers.
Separate Ad Accounts (Section 10.5)
Advertisers must not combine multiple end advertisers or their Meta business assets within the same ad account unless they meet specific requirements or have written approval from Meta. This policy ensures clear advertiser attribution, protects data integrity, and simplifies policy compliance reviews. However, businesses managing many end advertisers in one account can avoid separate accounts if they implement the vendor_id and/or brand fields correctly in their Product Catalog, Pixel, or CAPI integrations, and comply with Meta’s terms.
Transparency (Section 10.6.a, Effective February 3, 2027)
Advertisers must disclose to end advertisers, upon request, the amount spent on Meta advertising on their behalf (separate from fees), the fee structure, and detailed campaign information including configuration, settings, and post-campaign reporting using Meta terminology. Meta will not proactively disclose this information unless required by law or if a policy violation is suspected. In such cases, Meta may provide disclosures upon the end advertiser’s request and may notify the advertiser but is not obligated to do so.
Commitment to Policy Updates
Meta commits to regularly reviewing and updating these policies to keep pace with evolving industry standards and best practices, ensuring clarity and transparency for all parties involved in ad-buying solutions.
