Facebook continues to prepare advertisers, developers and partners for iOS 14 updates

Facebook continued to prepare app advertisers, developers, mobile web advertisers and partners for the changes. iOS 14 operating system.

The social network on Tuesday released version 9.0 of the Facebook Platform SDK (SDK), which included additional features, as well as the actions required to ensure that apps remain integrated with the platform.

Developers using version 8.2 or lower of the Android, iOS, or Unity SDKs should start migrating to version 9.0, as these older SDKs will be obsolete.

Facebook has stated that in the future, all major new releases will target annual releases with the goal of aligning the SDK version number with the latest version of API Graph (application programming interface), although minor updates will continue to be released to improve the functionality of its SDKs.

The social network will also end the support React native wrapper around its Android and iOS SDKs, and it removes the auto-initialization feature for its SDKs.

Facebook introduced a limited login mode for Facebook ID in order to implement protective measures to prevent a person using Facebook to connect to an iOS application from being used to target advertisements to that person or to measure its effectiveness.

Limited sign-in allows app users to create new accounts or access existing accounts while only sharing their names, profile photos, and, optionally, email addresses.

Developers can choose between limited login or classic Facebook login uniformly for all users or conditionally, and the modes are interoperable.

Facebook has shared the following actions that must be taken by advertisers and app developers, which must move to Audience network SDK v6.2.1 in order to monetize with users of iOS 14 when this OS is updated:

  • Advertisers who work with mobile measurement partners and don’t use the SDK, check with these MMPs for more information on integrating with Facebook to support SKAdNetwork.
  • Those using the SDK should have the latest version so that they can optimize for app events, mobile app installs, and events or value.
  • Starting Tuesday, advertisers can configure the SKAdNetwork conversion scheme in Events Manager to measure and optimize these goals.
  • Advertisers can now configure and test SKAdNetwork-based app installation campaigns in Ads manager and via the API.
  • The account-level attribution window will be replaced with a new attribution parameter accessible when creating the campaign at the ad set level, with the parameters being set by default to one click over seven days and one click. day view, which can lead to a decrease in reported conversions.
  • Advertisers who use App Events API and do not use Facebook SDK to support SKAdNetwork API must properly implement SKAdNetwork through Events Manager.
  • The social network described its new resource center in a blog post: “We are launching the Resource Center, a dedicated tab in Ads Manager with a personalized checklist of tasks to guide you through the actions you can take to ensure your ad is optimally configured and prepare for the upcoming impact of the iOS 14 requirements. The Resource Center will provide a list of relevant updates summarizing the impact of the iOS 14 requirements on your specific advertising account. Most tasks and updates will be linked to Help Center articles to further help you through these changes. “

Facebook’s tasks for advertisers and mobile web partners are:

  • Advertisers can now view all of their events through the new Global Event Measurement and Pixel / Conversions API tabs in Event Manager. The former will provide information about events processed using the aggregate event metric, while the latter includes all other web events.
  • Advertisers must validate their domain names by Entrepreneur.
  • Advertisers should limit themselves to eight conversion events per domain.
  • The delivery value optimization will switch from the ad manager to the event manager, and value sets must be enabled. They will be automatically assigned based on historical data and activated in the event manager for advertisers who have already used value optimization. There are a maximum of eight sets of values.
  • Performance and audience sizes may decrease for dynamic ads for retargeting. Advertisers should verify product URL domains in their catalog feeds and avoid using URLs that redirect users to different domains. Only one pixel per catalog should be used to optimize priority conversion events on all items in the catalog.
  • The account-level attribution window will be replaced with a new ad set-level attribution setting accessible during campaign creation, ensuring that conversions measured by Facebook are the same as those advising campaign optimization, which allows for greater clarity when analyzing ad performance.
  • Statistical modeling will be used for certain attribution windows and / or metrics to take into account the lower availability of data from iOS 14 users.
  • Some attribution windows will have partial reporting, and the metrics will not include all events from iOS 14 users. The in-product annotation will communicate when a metric is partial. This will be launched in early 2021 after Apple applies its ATT prompt.
  • Delivery and action breakdowns will not be supported for offsite conversion events. Offsite conversion events will be reported based on the time conversions occur and not the time of ad impressions, which may cause slight fluctuations in cost statistics as the cost per conversion will reflect the expenses over a given period divided by the conversions that took place during the same period. period, whereas today the cost per conversion reflects the spend over a given period divided by the conversions generated by ad impressions that occurred during the same period.
  • Attribution window settings for existing and newly created automated rules will no longer be supported, and a default seven-day click-through window for non-iOS conversions and the SKAdNetwork window for iOS conversions will be implemented .
  • Advertisers should specify changes to their attribution window and take advantage of the Window Compare feature to see how the conversions attributed to ads compare between different attribution windows.

Leave a Reply

Your email address will not be published. Required fields are marked *