Connect with us

FACEBOOK

Introducing Graph v8.0 and Marketing API v8.0

Published

on

Today, we’re releasing Graph API v8.0 and Marketing API v8.0. Some updates may require developer action, while others are shared with the purpose of keeping you informed. In this update, we’re also sharing upcoming deprecations. Visit the Platform Initiatives Hub to stay informed of other planned improvements.

If you are an iOS developer, stay tuned for further SDK announcements regarding Apple’s pending iOS14 launch.

Developer Action Required

Changes to tokenless access for User Picture and FB/IG OEmbed endpoints: By October 24, 2020, developers must leverage a user, app, or client token when querying Graph API for user profile pictures via UID, FB OEmbeds and IG OEmbeds. Developers should provide a user or app token when querying for profile pictures via a UID or ASID, though client tokens are supported as well. Please visit our changelog for User Picture, Facebook OEmbed and Instagram OEmbed for details on how to start calling these Graph API endpoints today.

Business Management Permission Updates: For an app to access the business field on ad accounts, we now require the app to have been granted granular permissions to the specific business object being accessed. By November 2, 2020, apps will need to request granular business_management permissions on the business that owns the ad accounts. For more information about granular permissions, check out our permission documentation.

Decoupling catalog_management from ads_management permissions: In response to developer’s interest to access these separately, we are decoupling these permissions. Detailed instructions are included in our v8.0 changelog. By January 31, 2021, developers who already have access to catalog_management will maintain access but will need to prompt their users to grant access via the FB Login Dialog.

Deprecations In This Update

As part of our ongoing commitments to privacy and security, we continue to make updates to our platform, including removing access to a number of APIs, as well as certain features. Timelines for each of these changes are detailed in their corresponding sections of the v8.0 changelog.

API endpoints: A list of API endpoints that will be removed from the platform are listed in the v8.0 Changelog, within their product or node sections. Please review this list to see if your app is impacted.

Sharing for Devices: We will be removing access to the “Sharing for Devices” feature, which allows users to share content from iOT devices to Facebook via a share dialog. Developers will lose access to this feature on November 2, 2020.

Version deprecations:

  • September 28, 2020 – v5.0 and v6.0 of the Marketing API will no longer be available
  • October 27, 2020 – v3.1 of the Graph API will no longer be available

No Action Required, For Your Information Only

The following announcements do not require action today, and rather are meant to keep you informed about other changes on our platform.

App Review Improvements for Business Developers: For developers with business apps, we’re customizing and streamlining app onboarding and integration based on the different ways that developers and businesses use the Facebook platform. We’re also introducing a new reviewable feature called Business Asset User Profile Access for business apps accessing user profile data through business assets. Please read more about this update in our App Review Improvements for Business Developers Blog.

Target Cost Bidding: Starting October 1, 2020, target cost bidding will no longer be available to select from the available bidding options in the UI. Note that target cost will be deprecated in v8.0 of the Marketing API, but accessible in v7.0. For developers who would like to continue controlling cost, we recommend using the cost cap bid strategy, which offers the ability to cap your campaign’s average CPA, and get as many optimization events as you can for your budget without exceeding the cap. Compared to target cost, you can expect more optimization events and more spend when using cost cap.

Action Item Calendar

Marketing API Version Deprecations

  • Be aware that v5.0 and v6.0 of the Marketing API will be removed from the platform. | 09/28/2020 | N/A

Changes to tokenless access for User Picture and FB/IG OEmbed endpoints

  • Update token usage for access to User Picture. | 10/24/2020 | User Picture
  • Update token usage for access to FB OEmbed endpoints. | 10/24/2020 | FB OEmbed
  • Update token usage for access to IG OEmbed endpoints. | 10/24/2020 | IG OEmbed

Graph API Version Deprecation

  • Be aware that v3.1 of the Graph API will be removed from the platform. | 10/27/2020 | N/A

Business Management Permission Updates

  • Apps will need to request granular business_management permissions on the business that own the ad accounts | 11/02/2020 | Permission Documentation

API Endpoints

  • Be aware of upcoming removal of API endpoints from the platform. | 11/02/2020 or 08/04/2022 (specified in the changelog) | Changelog

Sharing for Devices

  • Be aware of upcoming removal of the “Sharing for Devices” feature. | 11/02/2020 | N/A

Decoupling catalog_management from ads_management permissions

  • Developers with access to catalog_management will need to prompt their users to grant access via the FB Login Dialog. | 01/31/2021 | v8.0 changelog

Facebook Developers

Continue Reading

FACEBOOK

Data Use Checkup Rolling Out Broadly to Facebook Platform Developers

Published

on

Maintaining a safe, thriving developer ecosystem is critical to our mission of giving people the power to build community and bringing the world closer together. Recently, we have made changes to simplify our Platform Terms and Developer Policies so businesses and developers clearly understand their shared responsibility to safeguard data and respect people’s privacy when using our platform and tools.

These changes represent our strengthened commitment to protect people’s privacy and ensure developers have the tools and information they need to continue to use our platform responsibly.

Today, we’re announcing the broad launch of Data Use Checkup, a new annual workflow for Facebook platform developers that we began testing in April. Through Data Use Checkup, developers will be asked to review the permissions they have access to and commit that their API access and data use comply with the Facebook Platform Terms and Developer Policies within 60 days or risk losing their API access.

We are gradually rolling out Data Use Checkup in waves over the coming months. When you are enrolled in Data Use Checkup, you will receive information via a developer alert, an email to the registered contact, and in your Task List within the App Dashboard.

Developers who manage many apps will have the option to complete Data Use Checkup for multiple apps at once. You can access this flow by going to your “My Apps” page in the App Dashboard. From there, you will see all apps for which you are an admin, be able to filter down to a subset, and complete Data Use Checkup in bulk. This process will still require you to review each app you manage and the permissions you have access to and commit that your platform use complies with the Facebook Platform Terms and Developer Policies.

If you are not yet enrolled in Data Use Checkup, these are steps to take to prepare for the process:

  • Ensure you can access your app(s) in the App Dashboard. If you are unable to and need to regain admin status, click here.
  • Update contact details and app administrator designation for each app within your organization to receive the most up-to-date notifications. Any app admin will be able to complete the Data Use Checkup, so they should be in a position of authority to act on behalf of your organization. You can designate an app administrator within App Dashboard > Roles and update contact information within App Dashboard > Settings > Advanced.
  • Audit your apps and remove those that are no longer needed. To remove an app, go to App Dashboard > Settings > Advanced. This will ensure you’re only receiving developer alerts and notifications for apps that you need.
  • Review the permissions and features your apps have access to and remove any that are no longer needed in App Dashboard > App Review > My Permissions and Features.

Data Use Checkup is required for developers using many of our products and platforms across the Facebook Family of Apps. If you are developing on Oculus, here are specifics to consider and here is an update for businesses.

We know user privacy is just as important to our developer community as it is to us. Thank you for continuing to partner with us as we build a safer, more sustainable platform.

Facebook Developers

Continue Reading

FACEBOOK

Welcome to our 2020 Developer Circles Community Challenge

Published

on

It’s often said that the best way to learn is to become the teacher; that a great way to reinforce a skill or achievement is by sharing it with others.

It’s with this philosophy in mind that I’m pleased to welcome you to this year’s Community Challenge, our annual online hackathon for Developer Circles members – which runs until Monday October 26.

This time around, we’re inviting participants to go a step beyond building software solutions by creating tutorials about the code they’ve created. Winners are eligible to receive up to US$133,000 in cash prizes, Oculus VR headsets and fully credited amplification of their tutorials to millions of other developers across Facebook’s ecosystem.

We’re also broadening the products that competing innovators can build with, now spanning Open Source technologies including Docusaurus, Hack, Pytorch, React and React Native, as well as Messenger, Spark AR and Wit.ai.

Within each of these products, we see enormous opportunity for you and your teammates to connect, learn and build together, all while sharing your journey step-by-step through immersive tutorials for fellow tech enthusiasts.

I invite you to check out all of the guidelines for taking part, and I thought it would also be useful to share some examples that might help bring the challenge to life.

To get you started with a template for crafting impactful tutorials, here’s a framework providing an overview of recommended sections that will be helpful to readers, including some tips and tricks.

To provide general guidance on what a published tutorial looks like, here’s an example I wrote a couple of years ago about a product called Yoga – Facebook’s cross-platform layout engine that helps developers write more layout code. Please note that this particular tutorial is on the lengthier side – remember that your submission only needs to be between 1,000-4,000 words.

To demonstrate a useful step-by-step breakdown of a project, here’s a great tutorial on a smart bookmarking tool, Rust Rocket.

To understand the potential for using video to help bring your submission to life, check out this informative Docusaurus tutorial video and this engaging React Native tutorial video.

Remember, this is a team challenge, so we recommend dividing and conquering to create your tutorial most efficiently. If you have any tutorial ideas to share with potential teammates, or if you need support with troubleshooting or any questions about the challenge, please post in our Facebook group here.

What makes our Community Challenge so special every year is the many stories of collaboration and innovation we see from all around the world. We can’t wait to discover your story and for our global community to be inspired by your submission.

Good luck – and let’s get building!

#DevCCommunityChallenge #BuildwithFacebook

Facebook Developers

Continue Reading

FACEBOOK

Preparing Our Partners for iOS 14

Published

on

In June, Apple announced iOS 14 updates that, among other changes, require apps to ask users for permission to collect and share data using Apple’s device identifier.

Given the impact the policy will have on businesses’ ability to market themselves and monetize through ads, we’re sharing how we’re addressing iOS 14 changes and providing recommendations to help our partners prepare, while developers await more details on this policy.

First, we will not collect the identifier for advertisers (IDFA) on our own apps on iOS 14 devices. We believe this approach provides as much certainty and stability that we can provide our partners at this time. We may revisit this decision as Apple offers more guidance.

Additionally, we will remind users that they have a choice about how their information is used on Facebook and about our Off-Facebook Activity feature, which allows them to see a summary of the off-Facebook app and website activity businesses send to Facebook and disconnect it from their accounts.

There are a few things our partners should know to prepare for iOS 14. First, we will release an updated version of the Facebook SDK to support iOS 14. The new version of the Facebook SDK will provide support for Apple’s SKAdNetwork API, which limits the data available to businesses for running and measuring campaigns. In light of these limitations, and in an effort to mitigate the impact on the efficacy of app install campaign measurement, we will also ask businesses to create a new ad account dedicated to running app install ad campaigns for iOS 14 users.

We expect these changes will disproportionately affect Audience Network given its heavy dependence on app advertising. Like all ad networks on iOS 14, advertiser ability to accurately target and measure their campaigns on Audience Network will be impacted, and as a result publishers should expect their ability to effectively monetize on Audience Network to decrease. Ultimately, despite our best efforts, Apple’s updates may render Audience Network so ineffective on iOS 14 that it may not make sense to offer it on iOS 14. We expect less impact to our own advertising business, and we’re committed to supporting advertisers and publishers through these updates. Learn more about the impact to Audience Network here.

We believe that industry consultation is critical for changes to platform policies, as these updates have a far-reaching impact on the developer ecosystem. We’re encouraged by conversations and efforts already taking place in the industry – including within the World Wide Web Consortium (W3C) and the recently announced Partnership for Responsible Addressable Media (PRAM). We look forward to continuing to engage with these industry groups to get this right for people and small businesses.

Facebook Developers

Continue Reading

Trending