After studying and analyzing the different changes in the privacy policies of the Facebook App, we decided to update our Addon to continue working with all the availability of Facebook.
You can access data from pages of the creator of the app, and among the most important improvements and changes we can highlight that a new page of configurations is added where you must set the app ID and authenticate it. If the APP is not authenticated we have added a notification message to notify you in the edition of the campaign, we have also added an option to select between pages or groups and so you have more control of the content you want to publish.
New Facebook Platform Product Changes and Policy Updates
The publish_actions permission will be deprecated. This permission granted apps access to publish posts to Facebook as the logged in user. Apps created from today onwards will not have access to this permission. Apps created before today that have been previously approved to request publish_actions can continue to do so until August 1, 2018. No further apps will be approved to use publish_actions via app review. Developers currently utilizing publish_actions are encouraged to switch to Facebook’s Share dialogs for web, iOS and Android.
Call limits set to 200/page/app/hour for apps in development mode. View the charts for your app’s rate limit activity on your app dashboard.
Pages API will migrate to page-scoped ID (PSID) instead of app-scoped ID (ASID). Developers will have six months to migrate once app review resumes.
- The manage_page permissions will be required for the Page/tagged endpoint.
Apps in development mode will only have access to information for users who have admin, developer or test roles on the app.
The page/photos?type=tagged endpoint, which shares photos a Page was tagged in from a person’s timeline, will no longer be available.
Organic targeting (post-level-restrictions) based on gender and language will be deprecated on August 1, 2018 for posts created through third-party apps. Age gating will be available in a limited form, i.e. specifying age_max will be deprecated, and age_min can only be set to 13, 17, 18, 19 or 21.