Meta Developer Policy 10.5: What Agencies and Ad Platforms Must Do Before February 2027

Meta Developer Policy 10.5: What Agencies and Ad Platforms Must Do Before February 2027

Meta updated Developer Policy 10.5 and the related 10.6a, effective February 3, 2027, mandating that all ad-buying solutions -- agencies, platforms, and resellers -- disclose complete spending and campaign data directly to the end advertiser. The policy closes a long-standing data opacity gap in agency-client relationships where intermediaries controlled access to raw spend data, making it difficult for advertisers to independently verify what was actually spent on their behalf and on which campaigns. For agencies and ad tech platforms building on top of Meta's APIs, this is a compliance requirement with enforcement implications -- not an optional transparency upgrade.

Key takeaways

1. Meta Developer Policy 10.5 and 10.6a are effective February 3, 2027, requiring all entities that purchase Meta ads on behalf of another advertiser to provide that advertiser with access to complete spend and campaign data.
2. The policy applies to agencies, ad tech platforms, resellers, and any third party that operates as an intermediary between Meta's advertising systems and the end advertiser client.
3. Internally managed ad accounts -- where the brand itself manages its own Meta Business Manager without an agency or third-party platform in the purchasing chain -- are unaffected by this policy.
4. Non-compliance with Policy 10.5 risks account restriction or platform access revocation for the non-compliant ad-buying solution, not necessarily the end advertiser -- the enforcement target is the intermediary.
5. The required disclosure scope covers complete spend amounts, campaign-level breakdown, and ad account data -- not summarized or aggregated reporting that obscures line-item spend details.

What Policy 10.5 actually requires

Meta Developer Policy 10.5: the section of Meta's Platform Policy governing transparency obligations for ad-buying solutions. As of the February 3, 2027 effective date, it requires any entity purchasing Meta ads on behalf of another advertiser to disclose complete spending and campaign data directly to the end advertiser, providing the advertiser with the ability to independently verify their actual ad spend and campaign activity.

Policy 10.6a: the companion provision that defines the specific data scope required for disclosure. This covers ad account spend data, campaign-level performance data, and access sufficient for the advertiser to reconcile what was spent against what was delivered.

The policy shift addresses a specific market problem: in agency and reseller relationships, it has been common practice for intermediaries to control access to the underlying ad account data. Advertisers might receive a summarized report -- "we spent $50,000 on Meta ads this month" -- without access to the campaign-level breakdown, individual ad account IDs, or the ability to cross-check those numbers against Meta's own data independently. Policy 10.5 mandates that the advertiser have access to this data directly, bypassing the intermediary's summarization.

Who is affected by Meta Policy 10.5

Affected: any entity that purchases Meta ads on behalf of a client advertiser using Meta's APIs or Business Manager tools. This includes:

• Marketing agencies that manage Meta ad accounts for client brands
• White-label ad platforms that resell Meta advertising under a branded interface
• Managed service providers that operate Meta campaigns on behalf of enterprise clients
• Performance marketing agencies where client spend flows through an agency-controlled ad account

Not affected: brands and businesses that manage their own Meta Business Manager accounts and ad spending directly, without an intermediary purchasing on their behalf. If the brand's team logs into Meta Ads Manager directly and controls the account, Policy 10.5 does not create new obligations.

Edge cases requiring review:

Agencies that manage accounts within a client's own Business Manager (where the client retains Business Manager admin access) may already satisfy the disclosure requirement, since the advertiser technically has access to account data. However, agencies should verify that client access levels in Business Manager are set to provide full data visibility, not just campaign-manager-level access that restricts spend data.

Prooflytics

Stop stitching platform exports together

Every channel in one brief — plus the memory of what each one actually drove.

Start free trialSee pricing

14 days free · no credit card

What the ICP problem is for in-house marketing teams

The ICP problem this creates for in-house performance marketing teams: if your brand's Meta advertising runs through an agency or managed service, you may currently lack independent access to verify your spend data. You see what the agency reports, but you cannot pull the same numbers from Meta directly to confirm them. This creates a blind spot in your marketing analytics -- you cannot independently validate that reported ROAS figures match actual account-level spend, or that the campaign breakdown the agency provides is complete.

By the Meta Policy 10.5 framework, the practical implication for advertisers is that after February 3, 2027, any ad-buying solution must provide you with a mechanism to access your complete spend data directly. If your current agency relationship does not give you this access, the agency is required to provide it by the policy deadline -- not as a courtesy, but as a Platform Policy compliance requirement.

Prooflytics surfaces this in the context of Meta Ads data connections: if your Meta Ads connection is managed through a third-party platform or agency account structure, the daily briefing flags whether spend data visibility is direct (advertiser-level access) or intermediated, and alerts you to verify your buying partner's Policy 10.5 compliance status before the February 2027 enforcement date.

Compliance steps for agencies before February 3, 2027

Step 1: Audit your current account structures

For each client, determine: is the ad account within the client's own Business Manager, or is it within your agency's Business Manager? For accounts within your Business Manager, the client currently has no independent Meta access to verify spend data. These are the accounts that require action before February 2027.

Step 2: Decide between two compliance paths

Option A: Transfer accounts to client Business Manager. Move the ad account from your agency Business Manager to the client's Business Manager, with your agency maintaining access as a partner. This gives the client direct, independent access to their ad account data in Meta Ads Manager.

Option B: Grant client admin access to your Business Manager. Add the client as an admin user to your Business Manager with explicit access to their ad account data. This maintains the current account structure while giving the client direct data access.

Option A is generally cleaner for long-term client relationships because it removes the agency as a data access dependency. Option B works for existing relationships where a full account transfer is operationally complex.

Step 3: Update client access levels

For clients already within your Business Manager structure, audit their current access level. Campaign Manager access does not provide spend visibility. Account Admin access does. For Policy 10.5 compliance, clients need at minimum Advertiser access on their own ad account within your Business Manager.

Step 4: Update reporting agreements

Update client contracts and reporting SLAs to reflect that clients now have direct data access and will receive complete spend data. This is also an opportunity to align on how agency reports and Meta's direct data should be reconciled -- for example, agreeing that campaign performance reports will include account-level spend figures that the client can independently verify in Ads Manager.

Step 5: Verify your developer application status

If your agency or platform accesses Meta APIs through a registered developer application (Meta App), verify that your app is in compliance with the current Platform Policies before February 2027. Non-compliant apps risk access restrictions. Review your app's use of spend and campaign data against the updated Policy 10.5 language in Meta's Developer Documentation.

Bottom line

• Meta Developer Policy 10.5 effective February 3, 2027 requires all ad-buying intermediaries to give end advertisers direct access to complete spend and campaign data -- summarized reporting alone no longer satisfies the requirement.
• Agencies must audit their account structures and either transfer client ad accounts to client-owned Business Managers or grant clients direct data access before the deadline.
• In-house marketing teams should verify they have independent Meta Ads Manager access to their own account data before February 2027, and not wait for the agency to proactively offer it.
• Non-compliance risk sits with the intermediary (agency or platform), but disruption from enforcement actions can affect ongoing campaign delivery.
• For related context on Meta API compliance and conversion tracking setup, see Meta Conversions API setup guide and Meta Ads flexible format changes 2026.
• You can read independent reviews of Prooflytics on G2 and compare it to alternatives in the marketing analytics category.