Connect with us


Preparing our Partners for iOS 14: Actions for App Advertisers and Developers



Today, January 19, we are providing an update to our earlier guidance to prepare you for the changes created by Apple’s iOS 14 requirements. We’re launching new experiences in our advertising tools that will guide you through some of these changes, including actions you will soon be able to take. While Apple has still not made it clear to the industry when they will enforce their AppTransparencyTracking prompt, we are taking advance steps to help prepare you and reduce disruption to your advertising and integrations across Facebook apps. Below you will find the following updates:

  • New experiences in Events Manager, including a dedicated resource center
  • Updates to Ads Measurement
  • New Limited Login Mode for Facebook Login

Please note if you use the Marketing API or Ads Insights API please review this blog in detail for changes that will impact your campaigns. If you use the Ads Insights API there will be an immediate change to measurement beginning today.

As a review, advertisers using our Facebook SDK, Audience Network SDK, or and/or a Mobile Measurement Partner SDK need to be aware of the following version requirements:


  • Advertisers who have already upgraded to Facebook SDK v8.1 or above will be able to configure their SKAdNetwork for App install ads via standard or customizable methods.
  • Advertisers who have not already upgraded should upgrade to Facebook SDK v9.0 which was released today.


  • All publishers will need to use Audience Network SDK v6.2.1 in order to monetize with iOS 14 users when Apple introduces their new requirements. Audience Network SDK v6.2.1 was released on January 11, 2021.
See also  India Second Only to the US in Requesting Facebook for Users Data


  • If you work with an MMP and do not use the Facebook SDK, check with your MMP for more information regarding their completion of integrating with Facebook to support SKAdNetwork. If completed, the MMP will be able to provide you with a unique URL to paste into Events Manager to be able to run AEO and VO campaigns.
  • If you work with an MMP and use the Facebook SDK:
    • When optimizing for Installs (MAI): App should have the latest version of the Facebook SDK (v8.1 or above) or equivalent version of MMP SDK. This requires MMPs to have completed integration with Facebook to support interoperability of SKAdNetwork. Please check with your respective MMP for more information on where they stand on completion of integration with Facebook to support MAI using SKAdNetwork.
    • For optimizing app events, value, or mobile app installs + events, you will need to select one method to set measurement goals/conversion bits:
      • If events are sent from Facebook SDK, use Events Manager to set configure conversion schema.
      • If events are sent from MMP, the MMP interface needs to be used to configure the conversion schema.


  • Starting January 19, 2021, ahead of Apple’s prompt enforcement, advertisers will be able to configure the SKAdNetwork conversion schema in Events Manager to measure and optimize for App Events (AEO), Value (VO), or App Installs + App Events (MAI+events).


  • Starting January 19, 2021, ahead of Apple’s prompt enforcement, we will begin rolling out the ability for advertisers to set up and test SKAdNetwork-based app install campaigns in Ads Manager and via API.
  • Starting January 19, 2021, advertisers will see a toggle at the campaign level to indicate that they want to run an app install campaign targeting iOS 14 users.
See also  Meet the swans winning the hearts of thousands on Facebook with their unlucky lives


  • We will be replacing the account level attribution window with a new attribution setting accessible during campaign creation at the ad set level. For active and new ad sets, the setting will default to 7-day click and 1-day view, which may result in a decrease in the number of reported conversions. Due to limitations around view-through signal, the attribution setting for newly created campaigns after prompt enforcement will default to 7-day click instead of 7-day click and 1-day view. Today, you can prepare for attribution window changes by using the Comparing Windows feature in Ads Manager to see performance across all existing windows.


  • If you use App Events API and do not use Facebook SDK to support SKAdNetwork API, confirm that you have properly implemented SKAdNetwork through Events Manager to access the SKAdNetwork configuration experience.
  • Once confirmed, you will be able to configure your conversion schema to run AEO and VO campaigns


We are launching Resource Center, a dedicated tab in Ads Manager with a customized checklist of tasks to guide you through actions you can take to ensure your advertising is set up optimally and prepare for the upcoming impact of iOS 14 requirements. The Resource Center will provide a list of relevant updates summarizing how iOS 14 requirements may impact your specific ad account. Most tasks and updates will link to Help Center articles to further support you through these changes.


  • Facebook Login will now have a Limited Login mode that implements safeguards that allow advertisers to choose whether Facebook can use the fact that a person used Facebook to log into an advertiser’s iOS app to target advertising or measure advertising effectiveness. To implement this new version of Facebook Login, advertisers must update to version 9.0+ of the Facebook iOS SDK or Facebook SDK for Unity.
  • For more information on this new version of Facebook Login, including implementation documentation and FAQs, we encourage you to visit our Developers page.
See also  Clegg on its face: Facebook turns to former UK deputy PM to fend off damaging headlines ...

Facebook Developers

Continue Reading
Advertisement free widgets for website


Messenger Private Reply Updates for the Developer Community





Private Replies allows a business’ Facebook Page to send a single message to a person who published a post, who commented on a post or commented on the Page.

Support for Private Reply for Groups

In September, we extended this support for Facebook Groups, allowing businesses to be able to send private replies to a person who commented on their Page’s post in Facebook Groups.

How it Works

To send a private reply to a post or comment, send a POST request to the /PAGE-ID/messages endpoint with the recipient parameter set to the post_id or comment_id and the message parameter set to the message you wish to send.

The following example shows a reply to a post published on your Page by a customer:

Hi, I want to buy a gift for my nephew. Do you have any suggestions?

free widgets for website
  curl -X POST -H "Content-Type: application/json" -d '{     "recipient": {         "post_id": "PAGE-POST-ID"     },          "message": {       "attachment":{         "type":"template",         "payload":{           "template_type":"button",           "text":"Of course, what is your budget for the gift?",           "buttons":[               {                   "type": "postback",                   "title": "LESS THAN $20",                   "payload": "GIFT_BUDGET_20_PAYLOAD"               },               {                   "type": "postback",                   "title": "$20 TO $50",                   "payload": "GIFT_BUDGET_20_TO_50_PAYLOAD"               },               {                   "type": "postback",                   "title": "MORE THAN $50",                   "payload": "GIFT_BUDGET_50_PAYLOAD"               }           ]         }       }     } }' ""

Triggers a Private Reply flow like this.

For more information, please review the below documents:

First seen at

See also  Facebook takes aim at TikTok by letting users earn money off minute-long videos
Continue Reading


Enabling developers to create innovative AIs on Messenger and WhatsApp





Every week over 1 billion people connect with businesses on our messaging apps. Many of these conversations are made possible by the thousands of developers who build innovative and engaging experiences on Messenger, Instagram and WhatsApp.

Since opening access to our Llama family of large language models, we’ve seen lots of momentum and innovation with more than 30 million downloads to date. As our messaging services continue to evolve, we believe the technology from Llama and other generative AI models have the potential to enhance business messaging through more natural, conversational experiences.

At Connect Meta announced that developers will be able to build third-party AIs – a term we use to refer to our generative AI-powered assistants – for our messaging services.

We’re making it easy for any developer to get started, so we’re simplifying the developer onboarding process and providing access to APIs for AIs that make it possible to build new conversational experiences within our messaging apps.

All developers will be able to access the new onboarding experience and features on Messenger in the coming weeks. For WhatsApp, we’ll be opening a Beta program in November – if you’re interested in participating please sign up to the waitlist here to learn more.

free widgets for website

We’ll keep everyone updated as we make these tools available to more developers later this year. We look forward to your feedback and seeing what you create.

First seen at

See also  Welcoming Beat Games to Facebook
Continue Reading


Introducing Facebook Graph API v18.0 and Marketing API v18.0





Today, we are releasing Facebook Graph API v18.0 and Marketing API v18.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.

General Updates

Consolidation of Audience Location Status Options for Location Targeting

As previously announced in May 2023, we have consolidated Audience Location Status to our current default option of “People living in or recently in this location” when choosing the type of audience to reach within their Location Targeting selections. This update reflects a consolidation of other previously available options and removal of our “People traveling in this location” option.

We are making this change as part of our ongoing efforts to deliver more value to businesses, simplify our ads system, and streamline our targeting options in order to increase performance efficiency and remove options that have low usage.

This update will apply to new or duplicated campaigns. Existing campaigns created prior to launch will not be entered in this new experience unless they are in draft mode or duplicated.

free widgets for website

Add “add_security_recommendation” and “code_expiration_minutes” to WA Message Templates API

Earlier this year, we released WhatsApp’s authentication solution which enabled creating and sending authentication templates with native buttons and preset authentication messages. With the release of Graph API v18, we’re making improvements to the retrieval of authentication templates, making the end-to-end authentication template process easier for BSPs and businesses.

With Graph API v18, BSPs and businesses can have better visibility into preset authentication message template content after creation. Specifically, payloads will return preset content configuration options, in addition to the text used by WhatsApp. This improvement can enable BSPs and businesses to build “edit” UIs for authentication templates that can be constructed on top of the API.

See also  Facebook takes aim at TikTok by letting users earn money off minute-long videos

Note that errors may occur when upgrading to Graph API v18 if BSPs or businesses are taking the entire response from the GET request and providing it back to the POST request to update templates. To resolve, the body/header/footer text fields should be dropped before passing back into the API.

Re-launching dev docs and changelogs for creating Call Ads

  • Facebook Reels Placement for Call Ads

    Meta is releasing the ability to deliver Call Ads through the Facebook Reels platform. Call ads allow users to call businesses in the moment of consideration when they view an ad, and help businesses drive more complex discussions with interested users. This is an opportunity for businesses to advertise with call ads based on peoples’ real-time behavior on Facebook. Under the Ad set Level within Ads Manager, businesses can choose to add “Facebook Reels” Under the Placements section.
  • Re-Launching Call Ads via API

    On September 12, 2023, we’re providing updated guidance on how to create Call Ads via the API. We are introducing documentation solely for Call Ads, so that 3P developers can more easily create Call Ads’ campaigns and know how to view insights about their ongoing call ad campaigns, including call-related metrics. In the future, we also plan to support Call Add-ons via our API platform. Developers should have access to the general permissions necessary to create general ads in order to create Call Ads via the API platform.

    Please refer to developer documentation for additional information.

Deprecations & Breaking Changes

Graph API changes for user granular permission feature

We are updating two graph API endpoints for WhatsAppBusinessAccount. These endpoints are as follows:

  • Retrieve message templates associated with WhatsAppBusiness Account
  • Retrieve phone numbers associated with WhatsAppBusiness Account

With v18, we are rolling out a new feature “user granular permission”. All existing users who are already added to WhatsAppBusinessAccount will be backfilled and will continue to have access (no impact).

The admin has the flexibility to change these permissions. If the admin changes the permission and removes access to view message templates or phone numbers for one of their users, that specific user will start getting an error message saying you do not have permission to view message templates or phone numbers on all versions v18 and older.

free widgets for website

Deprecate legacy metrics naming for IG Media and User Insights

Starting on September 12, Instagram will remove duplicative and legacy, insights metrics from the Instagram Graph API in order to share a single source of metrics to our developers.

This new upgrade reduces any confusion as well as increases the reliability and quality of our reporting.

After 90 days of this launch (i.e. December 11, 2023), we will remove all these duplicative and legacy insights metrics from the Instagram Graph API on all versions in order to be more consistent with the Instagram app.

We appreciate all the feedback that we’ve received from our developer community, and look forward to continuing to work together.

Please review the media insights and user insights developer documentation to learn more.

free widgets for website

Deprecate all Facebook Wi-Fi v1 and Facebook Wi-Fi v2 endpoints

Facebook Wi-Fi was designed to improve the experience of connecting to Wi-Fi hotspots at businesses. It allowed a merchant’s customers to get free Wi-Fi simply by checking in on Facebook. It also allowed merchants to control who could use their Wi-Fi and for how long, and integrated with ads to enable targeting to customers who had used the merchant’s Wi-Fi. This product was deprecated on June 12, 2023. As the partner notice period has ended, all endpoints used by Facebook Wi-Fi v1 and Facebook Wi-Fi v2 have been deprecated and removed.

API Version Deprecations:

As part of Facebook’s versioning schedule for Graph API and Marketing API, please note the upcoming deprecations:

Graph API

  • September 14, 2023: Graph API v11.0 will be deprecated and removed from the platform
  • February 8, 2024: Graph API v12.0 will be deprecated and removed from the platform
  • May 28, 2024: Graph API v13.0 will be deprecated and removed from the platform

Marketing API

  • September 20, 2023: Marketing API v14.0 will be deprecated and removed from the platform
  • September 20, 2023: Marketing API v15.0 will be deprecated and removed from the platform
  • February 06, 2024: Marketing API v16.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.

Facebook Platform SDK

As part of our 2-year deprecation schedule for Platform SDKs, please note the upcoming deprecations and sunsets:

  • October 2023: Facebook Platform SDK v11.0 or below will be sunset
  • February 2024: Facebook Platform SDK v12.0 or below will be sunset

First seen at

See also  Meet the swans winning the hearts of thousands on Facebook with their unlucky lives
Continue Reading