Today, we are releasing Facebook Graph API v14.0 and Marketing API v14.0. As part of this release, we are highlighting changes below that we believe are relevant to parts of our developer community. These changes include announcements, product updates, and notifications on deprecations that we believe are relevant to your application(s)’ integration with our platform.
For a complete list of all changes and their details, please visit our changelog.
Meta collaborates with security and privacy experts to develop best practices in order to build people’s trust in how we safeguard their data, and we value the opportunity to partner with the developer community to achieve that goal. The Data Protection Assessment is required for developers who have apps that access certain types of user data on our platform.
We recommend that developers and their organizations familiarize themselves with the new questions and our Platform Terms, update app administrator and app contact information, and regularly monitor communications from the Developer Platform.
In line with our efforts to maintain a thriving developer ecosystem, we are introducing a new process known as access verification to help identify Tech Providers on our platform. This process will be required for both new and existing businesses with apps that require access to client business assets on Meta. The Access verification process will be gradually rolled out to businesses in monthly waves starting in June 2022 and businesses will be notified through developer alert and email when they need to complete the process.
Beginning with Graph API v14.0, we will support the setup and editing of Post Conversion Optimization to enable advertisers to optimize for events deeper in the conversion funnel than our current portfolio of optimizations. The product is currently in beta with a limited number of advertisers. Please follow announcements later this year as we plan to roll out broadly in the coming months.
We introduced a new feature in Business Manager called "Connected Apps" to give businesses more visibility into the Tech Provider app integrations they use for managing business assets on Meta's platform. Businesses are now able to access the Connected Apps feature to view and manage their Tech Provider apps within the system user tool. In the coming months, we are planning to expand the Connected Apps feature to give businesses additional functionality to control and manage their Tech Provider app integrations. Please follow announcements later this year as we plan to roll out more features in the coming months.
We are rolling out simplified categories for message template creation in the WhatsApp Business Management API and WhatsApp Manager UI. The new categories, Transactional, Marketing and One-time passwords, are also more inclusive of marketing-focused use cases now possible on the platform and will be supported by Graph API v14.0 or higher. Businesses will still be able to use the current template categories, such as Account Update or Shipping Update, on older versions of the Graph API until May 2024, when they will officially sunset. We recommend that businesses begin upgrading to v14.0 so they are able to use these new categories for new message templates. Please see developer documentation here for more detail.
We are adding the username field in the user profile API on Messenger API for Instagram with the Graph API v14.0 release. This will make it easier for creators and businesses on Instagram to debug conversation threads, and manage conversations between multiple apps like Instagram, Page Inbox, and other customer experience tools.
Starting today, permissible use cases will include parental access controls and monitoring apps that analyze user likes and user post content. These apps are used by parents and guardians to detect potential risk to the safety or wellbeing of people under 18 years of age. The apps are limited to youth social media analysis as presented in the app’s user interface.
Apps with access to these permissions that do not fall under the updated permissible use cases will be subject to enforcement action. If you're unsure whether your use case aligns with these updates, please proactively submit for App Review as soon as possible to avoid service disruption. Apps' whose use case aligns with the updated permissible use case(s) should not be impacted by this change.
As part of our ongoing efforts to simplify our targeting options, we’re removing Connections Targeting from all Meta advertising platforms on June 15, 2022. In advance of this date, we recommend developers convert their existing audiences that leverage Connections Targeting to the equivalent Engagement Custom Audience or Lookalike Audience. These alternatives also allow developers to target ads to users who are connected to their page, app and/or event. Additionally, developers using these alternatives will have access to several features that were not previously available with Connections Targeting, including the ability to share audiences with other businesses, create Lookalike Audiences for prospecting, and select different lookback periods.
We are announcing that the Facebook Analytics Mobile App Custom Audience ‘User by Segment’ feature is being deprecated and will no longer be supported as an event type for Mobile App Custom Audiences. The ability to use Facebook Analytics Mobile App Custom Audience 'User by Segment' will be fully removed by July 3, 2022. In-product notifications will be displayed in Audience Manager and Ads Manager to inform advertisers of this feature deprecation. We are sharing this update now to give advertisers advance notice of the upcoming deprecation of this feature. Once the ‘User by Segment’ feature is deprecated on July 3, 2022, campaign managers will be required to select a different event type and any existing campaigns that are still using this feature will be paused, as these audiences will be removed.
To avoid disruption to your business, we recommend migrating all calls to the latest API version that launched today.
To avoid disruption to your business, we recommend migrating all calls to the latest Marketing API version that launched today. (Visit the changelog for more details).
As part of our 2-year deprecation schedule for Platform SDKs, please note the upcoming deprecations and sunsets: