- Supported Ad Formats
- Download and Integration
- Set up Facebook Audience Network on the MoPub dashboard
- Migrate Facebook Audience Network from Custom Native Setup
- Facebook Token for Auto CPM
- Test Ad
- Additional Support
This guide is intended for publishers who want to use the MoPub SDK to load and display ads from Facebook Audience Network via mediation. Below, you will find information about the ad network, integration/setup instructions, and more. For more information about how MoPub mediation works, visit this guide.
Supported Ad Formats
The following ad formats are currently supported by Facebook Audience Network. For the latest support, visit the Facebook Audience Network homepage.
- Rewarded Video
Download and Integration
To download the Facebook Audience Network adapters, navigate to the Mediation Integration Tool. You will also need to download the Facebook Audience Network SDK, which can be found below.
For the latest download and integration instructions, ensure that you have consulted Facebook Audience Network’s tutorials before you integrate the SDK and adapters.
Note: Facebook uses the device’s localhost (127.0.0.1) to cache ad media files. Since Android 9 blocks cleartext traffic by default, publishers must add the following XML configuration to their app’s Manifest to whitelist unsecure traffic (click here for additional information):
<domain-config cleartextTrafficPermitted="true"> <domain includeSubdomains="true">127.0.0.1</domain> </domain-config>
- Android Integration Help: Facebook Audience Network adapters are released as an Android Archive (AAR) file starting from version 220.127.116.11. The AAR includes the required Manifest data for FAN. As a result, publishers no longer have to update their Manifest manually.
Set up Facebook Audience Network on the MoPub dashboard
Placement IDis required.
Migrate Facebook Audience Network from Custom Native Setup
Placement ID(if applicable) from the old custom native connection to the supported Facebook Audience Network instance.
- MoPub will initiate the following Facebook Audience Network custom event class names to render the ads:
Note: If you are manually entering the above-mentioned class names, migrate to the new network setup and pause the “custom native network”. If you are using your own custom event class names, you should have both the old custom native network setup & the new Facebook Audience Network network UI setup for backward compatibility.
Note: During migration, please make sure the custom native network and the Facebook Audience Network network are not live at the same time as this may cause revenue-impacting issues.
Facebook Token for Auto CPM
Here is the Facebook help article which provides instructions on how to generate a reporting token to use in the MoPub UI.
This setup is required to take advantage of Auto CPM.
- Have you associated the system user for which you generated the token to the right property?
- Did you assign the correct apps to the correct property?
Here is the Facebook help article on how to create apps within properties: https://www.facebook.com/help/publisher/709041312624617?helpref=page_content
- Still stuck? Reach out to your Facebook team for help and provide them with the app and property ids.
Why are some of my apps not updating for Facebook?
Confirm that all the apps that are connected to your Facebook token ID are correctly permissioned in Facebook Business Manager so that MoPub can collect the data for the placement IDs.
Follow the instructions here: https://developers.facebook.com/docs/audience-network/reporting-api/systemuser
While testing your SDK integrations and network setups, it is recommended that you leverage test ad placements for a consistent fill rate. To set up test mode, please reference Facebook’s test ad article for instructions.
For details about available error codes as well as potential resolutions, reference Facebook’s documentation.
For inquiries and support, please visit Facebook Audience Network’s support center.
Last updated April 01, 2019
TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.
© 2019 MoPub (a division of Twitter, Inc.)