Your best Facebook audiences may stop working next quarter – and your marketing team won’t know why. Since June 8, Meta blocks any audience that carries health or financial data. Adobe Experience Platform now enforces this automatically: if a customer list touches a loan, a policy, a diagnosis or a prescription, it gets flagged and quietly switched off. No campaign, no delivery, no error that anyone notices.
What shipped, exactly
- June 4, 2026: AEP upgraded its Facebook destination to Meta Advertiser API v25. The restriction itself arrived with v24 and applies to every version from v24 onward – it is not optional and no longer version-specific.
- The rule: audiences carrying regulated data (financial status, health) are blocked from activation to Meta.
The architecture behind it
Enforcement runs on Data Usage Labels. If an audience carries a governance label tied to financial status or health and is activated to the Facebook destination, AEP flags it – and Facebook blocks it from receiving data. There is no configuration path around it. The only two fixes Adobe documents: remove the restricted data from the audience, or contact Facebook directly.
The architectural takeaway is bigger than one channel: consent and data-governance labels are no longer internal hygiene. Downstream partners now enforce them for you. If your labels are sloppy, you find out at the destination – in production.
The fine print
- This is Meta’s own rulebook, wired into the activation pipe – not an Adobe policy decision.
- For a bank retargeting investment products or a pharma brand running a patient program, the core paid-social engine goes dark without an error message anyone watches.
- The data that makes these audiences valuable is exactly the data Meta now refuses.
Questions to settle
- Which of your active Meta audiences carry financial or health labels today – and who gets alerted when activation stops?
- Are your Data Usage Labels actually complete, or would a correct labeling pass switch off more audiences than expected?
- Where does the reallocated budget go – first-party journeys you own, or the next walled garden with the same risk?
- Who owns the channel-strategy decision this forces: marketing, data governance, or both?
The fix isn’t technical. It’s strategic: rethinking which channels you trust with regulated data, and building first-party journeys you actually own. The teams that saw this coming keep their reach – the rest reallocate budget in a panic while the CFO asks why last quarter’s numbers slipped.
Also on labels and consent in a pharma stack: HCP portal, part 2 – the HCP sees one seamless portal, the data walks a permission chain.
Frequently asked questions
Why do Meta audiences carrying health or financial data stop working?
Since 8 June, Meta blocks any audience that carries health or financial data. The restriction arrived with the Meta Advertiser API v24 and applies to every version from v24 onward, so it is neither optional nor version-specific. Adobe Experience Platform upgraded its Facebook destination to v25 on 4 June 2026.
How does Adobe Experience Platform enforce the Meta restriction?
Through Data Usage Labels. If an audience carries a governance label tied to financial status or health and is activated to the Facebook destination, AEP flags it and Facebook blocks it from receiving data. There is no configuration path around it: the only two fixes Adobe documents are removing the restricted data from the audience, or contacting Facebook directly.
What does this mean for data governance labels in general?
That labels are no longer internal hygiene. Downstream partners now enforce them on your behalf, which means incomplete or sloppy labelling is discovered at the destination and in production rather than during an internal review.
Automatic enforcement is good news, and it also means an audience you relied on may stop activating without warning. Worth knowing which of yours are affected before a campaign finds out for you.
Get in touch →Sources: Adobe Experience Platform release notes (June 2026) and the Facebook destination documentation (restricted data handling) on Adobe Experience League. Adobe and Adobe Experience Platform are trademarks of Adobe Inc.; Meta and Facebook are trademarks of Meta Platforms, Inc. This is an independent analysis; no partnership with or endorsement by either company. First published as part of my LinkedIn series, July 2026.
