Audience Network FAQ
Visit the Audience Network Help Center for more guidance and instructions on working with Audience Network.
Before releasing your app to the store, it’s highly important that you test the integration is working properly. Please read through our guide on how you can test your implementation. You can also follow our Getting Started guide if you need help on your integration. Once we review your app, you will be able to serve real ads automatically.
For each ad request, the SDK will pass the device identifier (IDFA on iOS and Advertising ID on Android) to Facebook so that we can determine the proper ad to serve. No information about the person will be passed back to the publisher along with the ad.
On iOS, the Audience Network can be integrated with apps that target iOS 5 and above. That said, ads will only show on devices that run iOS 6 and above. Requesting an ad on iOS 5 based devices will fail gracefully without negatively affecting the user experience.
On Android, the Audience Network can be integrated with apps that target API Version 11 of the Android SDK and above.
Yes, you can implement ads from a non-Activity class as long as the class has a reference to the holding Activity. You'll need to pass this Activity in as a parameter when creating instances of the ads.
Most mediation services have an option to integrate with 3rd party networks using adapters. The following describes the steps needed to setup such integrations:
- Add our SDK to your app
- Create a Placement ID on the Facebook app settings page. If you use a banner, make sure to select "None" as the refresh interval. The mediation layer will control the automatic refresh.
- Add or code the adapter according to your mediation service instructions. These can be either pre-built adapters (see below for Mopub, Admob and DFP) or a custom adapter that you will need to develop.
- Configure the adapter name and placement ID in your mediation server UI and allocate impressions to it
See tips for how to get more fill and revenue when using mediation.
Here are instructions for integrating with the following mediation services:
AdMob / DFP:
- High-Level Instructions
- AdMob iOS Technical Details
- AdMob Android Technical Details
- DFP iOS Technical Details
- DFP Android Technical Details
- High-Level Instructions
- Heyzap Android Technical Details
- Heyzap iOS Technical Details
- Heyzap Unity Technical Details - iOS and Android
- Heyzap Adobe AIR Technical Details - iOS and Android
This means we are not able to serve ads to this person. This could occur because:
- The person testing has not logged into the native Facebook app on their mobile device
- The person testing has enabled "Limit Ad Tracking" (iOS only) or has selected "Opt out of interest-based ads" (Android only) in their device settings.
- We don't have ad inventory to show for that person
Note that if you can see test ads, your implementation works correctly and people will be able to see ads in your app once it's live.
- Title: 30 characters maximum
- Cover Image: 1200x627px
- Icon: 128px square
- Social context: 30 characters
- Title for button (call to action): less than 20 characters
- Body text: 90 characters
- Rating Scale: 5
- Rating Min/Max: 1/5
Yes—ad metadata can be cached and re-used for up to 1 hour. If you plan to use the metadata after this time period, make a call to load a new ad. After this time passes, if the person has not clicked the ad, you must request a new ad.
After integrating our SDK into your iOS app, you will need to submit your app to Apple for review. As part of this review process, you will be asked if your app uses the Advertising Identifier (IDFA). Please check "Yes". You will then be asked how your app makes use of it. The question will take this form:
This app uses the Advertising Identifier to (select all that apply)?
- Serve advertisements within the app
- Attribute this app installation to a previously served advertisement
- Attribute an action taken within this app to a previously served advertisement
If you will be using the Audience Network framework, you must select the first option. If you are using our core framework to track install attribution and app events, please select the second and third options. If you are using both, select all three.
You will also be asked to check a box to confirm that your app honors a user's Limit Ad Tracking setting in iOS. The Facebook SDK honors the iOS Limited Ad Tracking Setting. When a person enables Limited Ad Tracking, Facebook only uses data obtained through the use of the Advertising Identifier for “Limited Advertising Purposes” as defined by the iOS Developer Program License Agreement. Please make sure check this box when prompted.
Marking these questions in this way will help ensure a smooth review process.
Yes, the Audience Network SDK for Android uses the Advertising ID and respects its limit tracking option in accordance with Google Play's terms and conditions. We recommend, but do not require, that you set up your project with Google Play Services. Setting up your app in this way will result in better technical performance when using the Audience Network.
To ensure the best possible experience for your app's users, follow our Audience Network Policies when integrating your ads.
We reserve the right to reject, approve or remove any publisher for any reason, in our sole discretion, including publishers that negatively affect our relationship with our people or that promote content, services, or activities, contrary to our competitive position, interests, or advertising philosophy. These guidelines are subject to change at any time.
In order to ensure that our publishers are offering a high quality advertising experience, we require that all apps serving Facebook ads are in compliance with our Audience Network policies.
All apps in our network will be reviewed by automated systems as well as manually checked for quality and compliance. We will have on-going quality review to ensure continued adherence to our policies and native ad design guidelines.
Learn how to submit your app for review.
At Facebook, we believe that ads should contribute to and be consistent with the overall user experience. We’re committed to meeting this goal, both on Facebook and in the Audience Network.
Every ad that runs in the Audience Network is also eligible to run on Facebook. This means they are subject to Facebook’s strict ads policies and pass through our rigorous proactive and reactive review process. In other words, Facebook is providing publisher partners with exactly same protections we use for our own site. Our ads policies are available here. These policies are designed to ensure that ads are high-quality, brand-safe, and in compliance with all applicable laws.
We recognize there may be instances in which you prefer a particular ad or type of ad not run in your app, regardless of whether it meets our policies. As an Audience Network publisher partner, you will have the ability to filter out specific advertisers or categories of advertisers (e.g., political ads) as you see fit.
Learn how to limit which advertisers can run ads on your app or site.
We will not serve ads to people that have advertising opt-outs enabled on their iOS and Android devices.
The ads will look very similar to our existing mobile ads on Facebook. Clicking on an ad will either take a user into an app store to download an app, open a webpage in the browser or launch an existing app on their phone. The ads will consist of banners, interstitials and native ads to match the ad placements in your app. The ads will contain the same elements as standard Facebook ads.
Learn more about what ads can run on Audience Network, and what happens when people interact with them.
It depends—performance will vary due to factors such as audience, ad placements, and the advertising campaigns that match your user base.
Your fill rate may change over time as our network is constantly evolving. Many factors like the demographics of your user base, their geography and advertiser demand can shift and impact the number of ads that could run in your app.
If you see sudden changes in your fill rate, please check to make sure that:
- Your implementation is correct
- You have not added additional filters
- You are using the latest SDK
- You are not submitting requests too frequently (for example, requesting an ad for the same placement ID multiple times within a 15 second interval)
If the issue persists, please contact support for additional help.
By default, the ad refresh rate for each placement ID will be set at 30 seconds. You can edit your refresh rate for each placement ID by going to the "Audience Network" section in your App Settings and select the Placements tab. Please note that refresh rate only affects banners.
Use the filtering option in the "Audience Network" section in your App Settings to exclude the apps whose ads you would like to prevent from showing in your app.
Facebook aims to deliver valuable ROI for advertisers on the Audience Network by ensuring that clicks are authentic and intentional. We have zero tolerance for click fraud committed by publishers and will ban publishers immediately when we detect fraud. We carefully monitor all clicks and impressions served on the Audience Network to detect patterns of click fraud. We will not charge advertisers or pay publishers for clicks we determine to be invalid.
Fill rate is calculated based on total filled ads over total eligible requests. Scenarios where a request will not be counted include:
- Request for an ad is too frequent. For example, if you request an ad with the same placement ID in less than 15 second intervals
- IDFA (iOS) or Advertising ID (Android) is not available or can not be used for ad delivery
- Facebook has not been installed on the requesting app or the user has not logged in recently
Add your team members are admins or as Insights users to give them access to reporting. To add or change a role assignment, visit your Facebook app settings and choose the "Roles" section.
You can find reports by going to the "Audience Network" section in your App Settings and selecting the Performance tab. Reports show an overview of your performance as well as performance details for a specific time frame. You can further analyze your performance by country and by Placement ID.
For your payments history and payout details, go to the "Audience Network" section and select the Payout tab.
We won't disclose specific advertiser information in your reports. If you would like to filter a specific advertiser or category of advertisers, go to the "Audience Network" section in App Settings and select the Filter tab.
You can set up payments by completing the publisher payout forms. The forms are located under the payout tab in the "Audience Network" section in your app settings page. We require your bank name, SSN/TIN and tax information in order to process your payouts.
Note: If your account balance hits $100 without submitting this information, then your ads will stop running until we receive the necessary information.
Contact us if you have problems completing the information.
Payments are extracted when you accumulate at least $100 in revenue. You'll receive payments on the 21st of each month for the previous month's balance.
If you'd like to change any of your payment information, go to the "Audience Network" section in App Settings and select the Payout tab.
We believe that the Audience Network provides a mobile advertising experience that will better help publishers and developers monetize their apps, but we cannot commit to a specific revenue share at this point. Real-time reporting and expected payout are available in the "Audience Network" section in your app settings page.
Managing your apps
To add someone to an administrator or developer role on an existing Facebook app, navigate to the Roles tab of the App Dashboard and select "Add Administrators" or "Add Developers".
Audience Network for Mobile Web
Audience Network is now available for mobile web, bringing the value of native ad formats and people-based marketing to a new set of publishers, and enabling 2.5 million Facebook advertisers to reach more of the people they care about on mobile devices.
Mobile Web Formats