Introducing Facebook Graph API v12.0 and Marketing API v12.0
Today, we are releasing Facebook Graph API v12.0 and Marketing API v12.0. Below, we’ve highlighted changes that will impact parts of our developer community. These changes include announcements and product updates, reminders from prior launches, and notifications on large-scale deprecations that may affect your application(s)’ integration with our platform.
For a complete list of all changes and their details, please visit our changelog.
General Announcements and Updates
Conversions API: Expanding minimum callable version
Graph API Backwards Compatibility for Apps Created with One-Click Access Tokens Beginning with v12.0, newly created access tokens generated under the Conversions API settings tab in Events Manager are now supported by all available Graph API versions (see the supported versions here).
Please note that calls made with these tokens to a deprecated Graph API version will automatically resolve to the oldest available version. This behavior only applies to Graph API endpoints. Marketing API endpoints, including the Conversions API, do not support auto-upgrade behavior and will throw an exception.
User Profile API for Instagram Messaging: New fields
We are making enhancements to the User Profile API for Instagram messaging. Previously, User Profile API for Instagram supported two fields: 1) Name and 2) URL of the profile picture. In order to allow businesses to better personalize and prioritize messages based on publicly available user information, we have updated the API to also include following information:
1. Follower count
2. Verified Badge
3. Business follows User account [Yes/No]4. User account follows Business account [Yes/No]
Please refer to the developer documentation for details.
Detailed Targeting New Opportunities
To help advertisers find additional opportunities that weren’t originally available to them, when advertisers leverage Detailed Targeting and optimize for conversions, value or app events using the conversions objective they will be automatically included into Targeting Expansion. For more information please refer to the Detailed Targeting Expansion Help Center article.
Video API: New fields
We have added two new fields, views and post_views, to the [Video] node. Please view the Video API developer documentation to learn more.
Deprecations & Breaking Changes
Error Transparency
The Graph API and Marketing API default behavior is to throw an error when an app requests a field or edge on a node that returns an associated node or nodes, but lacks the appropriate permissions required by the associated nodes. However, a number of these fields and edges did not follow this protocol and instead were simply omitted from API responses if the calling app lacked appropriate permissions.
Starting with v12.0 these fields and edges will conform to the default behavior. This change will apply to all versions on December 13, 2021.
System users and app roles
We are deprecating the ability for system users to be granted roles on apps unless the users and the apps both belong to the same businesses. In order to prevent disruption to your app and business, we recommend that these system users be removed from your app and use the Business On Behalf Of API instead. This breaking change will go into effect on December 13, 2021.
Scheduled Live
We are deprecating the planned_start_time parameter within the Scheduling capability in the Live API and the breaking change will go into effect on December 13, 2021. A new parameter will be announced at a future date.
Messenger Platform: Conversation API
We are deprecating the user_id field from the thread metadata in Conversation API. All developers will need to migrate any references to user_id (IGID) and fully rely on IGSID as a primary identifier of a thread between the user and business.
This breaking change will go into effect on prior Graph API versions on December 13, 2021. Please view the Conversation API developer documentation to learn more.
Messenger Platform: Instagram Webhooks
We are making an update to our Messenger API for IG reaction webhook in order to better support emoji reactions. The current version returns the emoji field as a string – with this update, reaction webhooks will return a new unicode format. Note that the “reaction” field will only support the default emojis. For all other emojis the reaction field will return “other,” the same as MSGR.
This breaking change will go into effect on prior Graph API versions beginning December 13, 2021. In order to continue to support emoji reactions, all developers need to migrate to the new unicode we are returning by December 13, 2021. Please refer to the Webhook developer documentation for details.
API Version Deprecations:
As part of Facebook’s versioning schedule for Graph API and Marketing API, please note the upcoming deprecations:
Graph API
- November 2, 2021: Graph API v4.0 will be deprecated and removed from the platform
- February 3, 2022: Graph API v5.0 will be deprecated and removed from the platform
- May 22, 2022: Graph API v6.0 will be deprecated and removed from the platform
To avoid disruption to your business, we recommend migrating all calls to the latest API version that launched today.
Marketing API
- Marketing API v10.0 will deprecate on 10/04/2021
- Marketing API v11.0 will deprecate on 02/23/2022
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).
Facebook Platform SDK
General Deprecations
Native Offers Endpoint Deprecation
On June 8, 2021, we announced the deprecation of Offers Ads API. This will go into effect immediately with the release of Graph API v12.0.
Messenger Platform – Airline Templates
On June 8, 2021, we announced the deprecation of airline templates. This will go into effect on December 6, 2021.
Updating Special Ad Audiences for housing, employment, and credit advertisers

On June 21, 2022 we announced an important settlement with the US Department of Housing and Urban Development (HUD) that will change the way we deliver housing ads to people residing in the US. Specifically, we are building into our ads system a method designed to make sure the audience that ends up seeing a housing ad more closely reflects the eligible targeted audience for that ad.
As part of this agreement, we will also be sunsetting Special Ad Audiences, a tool that lets advertisers expand their audiences for ad sets related to housing. We are choosing to sunset this for employment and credit ads as well. In 2019, in addition to eliminating certain targeting options for housing, employment and credit ads, we introduced Special Ad Audiences as an alternative to Lookalike Audiences. But the field of fairness in machine learning is a dynamic and evolving one, and Special Ad Audiences was an early way to address concerns. Now, our focus will move to new approaches to improve fairness, including the method previously announced.
What’s happening: We’re removing the ability to create Special Ad Audiences via Ads Manager beginning on August 25, 2022.
Beginning October 12th, 2022, we will pause any remaining ad sets that contain Special Ad Audiences. These ad sets may be restarted once advertisers have removed any and all Special Ad Audiences from those ad sets. We are providing a two month window between preventing new Special Ad Audiences and pausing existing Special Ad Audiences to enable advertisers the time to adjust budgets and strategies as needed.
For more details, please visit our Newsroom post.
Impact to Advertisers using Marketing API on September 13, 2022
For advertisers and partners using the API listed below, the blocking of new Special Ad Audience creation will present a breaking change on all versions. Beginning August 15, 2022, developers can start to implement the code changes, and will have until September 13, 2022, when the non-versioning change occurs and prior values are deprecated. Refer below to the list of impacted endpoints related to this deprecation:
For reading audience:
- endpoint gr:get:AdAccount/customaudiences
- field operation_status
For adset creation:
- endpoint gr:post:AdAccount/adsets
- field subtype
For adset editing:
- endpoint gr:post:AdCampaign
- field subtype
For custom audience creation:
- endpoint gr:post:AdAccount/customaudiences
- field subtype
For custom audience editing:
- endpoint gr:post:CustomAudience
Please refer to the developer documentation for further details to support code implementation.
First seen at developers.facebook.com
Introducing an Update to the Data Protection Assessment

Over the coming year, some apps with access to certain types of user data on our platforms will be required to complete the annual Data Protection Assessment. We have made a number of improvements to this process since our launch last year, when we introduced our first iteration of the assessment.
The updated Data Protection Assessment will include a new developer experience that is enhanced through streamlined communications, direct support, and clear status updates. Today, we’re sharing what you can expect from these new updates and how you can best prepare for completing this important privacy requirement if your app is within scope.
If your app is in scope for the Data Protection Assessment, and you’re an app admin, you’ll receive an email and a message in your app’s Alert Inbox when it’s time to complete the annual assessment. You and your team of experts will then have 60 calendar days to complete the assessment. We’ve built a new platform that enhances the user experience of completing the Data Protection Assessment. These updates to the platform are based on learnings over the past year from our partnership with the developer community. When completing the assessment, you can expect:
- Streamlined communication: All communications and required actions will be through the My Apps page. You’ll be notified of pending communications requiring your response via your Alerts Inbox, email, and notifications in the My Apps page.
Note: Other programs may still communicate with you through the App Contact Email.
- Available support: Ability to engage with Meta teams via the Support tool to seek clarification on the questions within the Data Protection Assessment prior to submission and help with any requests for more info, or to resolve violations.
Note: To access this feature, you will need to add the app and app admins to your Business Manager. Please refer to those links for step-by-step guides.
- Clear status updates: Easy to understand status and timeline indicators throughout the process in the App Dashboard, App Settings, and My Apps page.
- Straightforward reviewer follow-ups: Streamlined experience for any follow-ups from our reviewers, all via developers.facebook.com.
We’ve included a brief video that provides a walkthrough of the experience you’ll have with the Data Protection Assessment:
Something Went Wrong
We’re having trouble playing this video.
The Data Protection Assessment elevates the importance of data security and helps gain the trust of the billions of people who use our products and services around the world. That’s why we are committed to providing a seamless experience for our partners as you complete this important privacy requirement.
Here is what you can do now to prepare for the assessment:
- Make sure you are reachable: Update your developer or business account contact email and notification settings.
- Review the questions in the Data Protection Assessment and engage with your teams on how best to answer these questions. You may have to enlist the help of your legal and information security points of contact to answer some parts of the assessment.
- Review Meta Platform Terms and our Developer Policies.
We know that when people choose to share their data, we’re able to work with the developer community to safely deliver rich and relevant experiences that create value for people and businesses. It’s a privilege we share when people grant us access to their data, and it’s imperative that we protect that data in order to maintain and build upon their trust. This is why the Data Protection Assessment focuses on data use, data sharing and data security.
Data privacy is challenging and complex, and we’re dedicated to continuously improving the processes to safeguard user privacy on our platform. Thank you for partnering with us as we continue to build a safer, more sustainable platform.
First seen at developers.facebook.com
Resources for Completing App Store Data Practice Questionnaires for Apps That Include the Facebook or Audience Network SDK

Resources for Completing App Store Data Practice Questionnaires for Apps That Include the Facebook or Audience Network SDK
First seen at developers.facebook.com
-
OTHER2 weeks ago
Meta Said to Curtail Election Misinformation Efforts as US Midterm Vote Approaches: Details
-
OTHER2 weeks ago
Meta Announces First-Ever Bond Offering Amid Push to Invest in Virtual Reality Projects
-
OTHER1 week ago
Twitter Down? Company Responds as Thousands of Users Report Issues With Accessing Twitter
-
OTHER2 weeks ago
WhatsApp Working on Login Approval Feature to Improve Account Security: Report
-
OTHER1 week ago
Facebook Parent Meta Raises $10 Billion in Its First-Ever Bond Offering
-
Uncategorized1 week ago
What are KOLs in Marketing? (And How to Work With Them)
-
OTHER2 weeks ago
Elon Musk Could Struggle with Banks, His Twitter Deal Escape Hatch, Experts Say
-
OTHER1 week ago
WhatsApp Users to Get Ability to Control Online Presence, Leave Groups Silently, and More: All Details