Custom Open Graph Deprecation Guide

On October 5, 2016, we announced the beginning of the deprecation of Custom Open Graph and Custom App Collections. We consistently received feedback from developers that creating your own Custom Open Graph actions and objects is time-consuming and overly complex. We are now working on other ways for people and developers to add context to what they're sharing, and to have people discover new apps that they might find interesting.

Details

  • If your app has a minimum Graph API version v2.8 or higher, you will not be able to create new Custom Open Graph action types or object types, or publish Open Graph stories that use custom action or object types. You will not see the Open Graph product in your App Dashboard.
  • At the time of this release, two new common action types are available to developers in all versions of the API: games.plays and books.rates
  • In approximately 90 days after October 5, 2016, previous versions of the API (2.7 and below) will not allow the creation of new Custom Open Graph action or object types. Additionally at that time, all custom App Collections will be removed from people's profiles. The Open Graph product section of the App Dashboard will become read-only.
  • In approximately 1 year from October 5, 2016, no version of Graph API will allow publishing stories that use Custom Open Graph action types or object types.
  • Graph API v2.8 does not require Open Graph Review for using built-in action types; all the capabilities associated with publishing Open Graph stories via the API will instead be covered in Login Review when requesting publish_actions permission. Graph API v2.7 and below will stop requiring Open Graph Review for using built-in action types in approximately 90 days from October 5, 2016.

Because all non-Open Graph API shares are required to be explicitly shared, implicit shares of Custom Open Graph stories aren't possible.

Action Required

While existing implementations will see no effects for 90 days from October 5, 2016, we recommend that you immediately begin transitioning your Custom Open Graph stories another format, because in approximately 1 year, attempts to publish these stories to Facebook will fail. There are two options to replace Custom Open Graph stories:

  1. Built-in Open Graph actions, including the new games.plays and books.rates options, or
  2. Standard link, quote, photo, video, or multi-media share.

Below are examples of what it would look like for our sample app, Friend Smash, to stop using Custom Open Graph action types and object types and switch to another sharing type.

First, here is an example of Custom Open Graph sharing as it behaves currently. There is the custom action type “Smash” with two potential custom object types, “celebrity” or “profile.” In this example, the specific object being shared is “a person.”

If we were to switch to using the Built-in Open Graph action type, games.plays, the header of the story would change — and your app name would become the “object” being shared. We also recommend, though it isn't required, that you consider changing the link's title and description at the same time with Open Graph metatags to provide as much context and information as you'd like to include for the shared story. For example:

The other option is to forego Open Graph stories entirely, and create a standard link share. We also recommend, though it isn't required, that you consider changing the link's title and description at the same time with Open Graph metatags to provide as much context and information as you'd like to include for the shared story. For example:

For More Information