Facebook Audience SDK integration for React Native, available on iOS and Android. Features native, interstitial and banner ads.

• Prerequisites
• Installation
• Linking
• Expo Installation
• Usage
  • Interstitial Ads
  • Native Ads
  • Banner View
• API
  • NativeAdsManager
  • AdSettings
• Running the example
  • Install dependencies
  • Start packager
  • Run it on iOS / Android
• Credits

You must have Facebook developer account in order to start integrating your app with this library. If you don't have one sign up here.

Follow the instructions on react-native-fbsdk-next to integrate the Facebook SDK into your project.

Follow Facebook's instructions to create placement IDs for your ads. In order to get test ads modify your placement ID as it shown here.

Follow Facebook's instructions to add test devices and add test users.

You can get AAID from the android device/emulator by going to Settings > Google > Ads.

You can get IDFA from the iOS device using a third party app from the App Store. For simulators IDFA can be obtained by running this command: xcrun simctl list 'devices' 'booted'.

Note: Simulator must be booted.

Add the package to your project using either yarn:

yarn add react-native-fbads

or npm:

npm install --save react-native-fbads

CLI autolink feature links the module while building the app.

Note: for iOS make sure to install Pods through CocoaPods by running this command in your project's root directory: cd ios && pod install

$ react-native link react-native-fbads

This package cannot be used in the "Expo Go" app because it requires custom native code.

First install the package with yarn, npm, or expo install.

expo install react-native-fbsdk-next react-native-fbads

After installing this npm package, add the config plugin to the plugins array of your app.json or app.config.js:

{
  "expo": {
    "plugins": [
      [
        "react-native-fbsdk-next",
        {
          "appID": "48127127xxxxxxxx",
          "clientToken": "c5078631e4065b60d7544a95xxxxxxxx",
          "displayName": "RN SDK Demo",
          "advertiserIDCollectionEnabled": false,
          "autoLogAppEventsEnabled": false,
          "isAutoInitEnabled": true,
          "iosUserTrackingPermission": "This identifier will be used to deliver personalized ads to you."
        }
      ],
      "react-native-fbads"
    ]
  }
}

Next, rebuild your app as described in the "Adding custom native code" guide.

An Interstitial Ad is a an ad that covers the whole screen with media content. It has a dismiss button as well as the clickable area that takes user outside of your app.

Interstitial ads are displayed over your root view with a single, imperative call.

On android, you'll need to add the following to your AndroidManifest.xml:

<activity
  android:name="com.facebook.ads.InterstitialAdActivity"
  android:configChanges="keyboardHidden|orientation" />

Usage:

import { InterstitialAdManager } from 'react-native-fbads';

InterstitialAdManager.showAd(placementId)
  .then((didClick) => {})
  .catch((error) => {});

The showAd method returns a promise that will be resolves once the ad has been either dismissed or clicked by the user. The promise will reject if an error occurs before displaying the ad, such as a network error.

If you want to preload the ad and show it later you can use this instead:

import { InterstitialAdManager } from 'react-native-fbads';

InterstitialAdManager.preloadAd(placementId)
  .then((didClick) => {})
  .catch((error) => {});

// Will show it if already loaded, or wait for it to load and show it.
InterstitialAdManager.showPreloadedAd(placementId);

Native Ads allow you to create custom ad layouts that match your app. Before proceeding, please review Facebook's documentation on Native Ads to get a better understanding of the requirements Native Ads impose.

import { NativeAdsManager } from 'react-native-fbads';

const adsManager = new NativeAdsManager(placementId, numberOfAdsToRequest);

The constructor accepts two parameters:

• placementId - which is an unique identifier describing your ad units,
• numberOfAdsToRequest - which is a number of ads to request by ads manager at a time, defaults to 10.

Your component will have access to the following properties, under the nativeAd prop:

• advertiserName - The name of the Facebook Page or mobile app that represents the business running each ad.
• headline - The headline that the advertiser entered when they created their ad. This is usually the ad's main title.
• linkDescription - Additional information that the advertiser may have entered.
• translation - The word 'ad', translated into the language based upon Facebook app language setting.
• promotedTranslation - The word 'promoted', translated into the language based upon Facebook app language setting.
• sponsoredTranslation - The word 'sponsored', translated into the language based upon Facebook app language setting.
• bodyText - Ad body
• callToActionText - Call to action phrase, e.g. - "Install Now"
• socialContext - social context for the Ad, for example "Over half a million users"

In addition, you'll have access to the following components:

• MediaView for displaying Media ads
• AdIconView for displaying the ad's icon
• AdChoicesView for displaying the Facebook AdChoices icon.
• TriggerableView for wrapping Text so it will respond to user clicks.

Please ensure you've reviewed Facebook's instructions to get a better understanding of each of these components and how you should use them.

import {
  AdIconView,
  MediaView,
  AdChoicesView,
  TriggerableView,
} from 'react-native-fbads';
class AdComponent extends React.Component {
  render() {
    return (
      <View>
        <AdChoicesView style={{ position: 'absolute', left: 0, top: 0 }} />
        <AdIconView style={{ width: 50, height: 50 }} />
        <MediaView style={{ width: 160, height: 90 }} />
        <TriggerableView>
          <Text>{this.props.nativeAd.description}</Text>
        </TriggerableView>
      </View>
    );
  }
}

export default withNativeAd(AdComponent);

Facebook's guidelines require every native ad to include the Ad Choices view, which contains a small clickable icon. You can use the included AdChoicesView component and style it to your liking.

import { AdChoicesView } from 'react-native-fbads';

<AdChoicesView style={{ position: 'absolute', left: 0, top: 0 }} />;

Finally, wrap your component with the withNativeAd HOC and pass it the adsManager you've previously created.

class MyAd {
 ...
}
export const AdComponent = withNativeAd(MyAd);

class MainApp extends React.Component {
  render() {
    return (
      <View>
        <AdComponent adsManager={adsManager} />
      </View>
    );
  }
}

BannerView is a component that allows you to display ads in a banner format (know as AdView).

Banners are available in 2 sizes:

• standard (BANNER_HEIGHT_50)
• large (BANNER_HEIGHT_90)

import { BannerView } from 'react-native-fbads';

function ViewWithBanner(props) {
  return (
    <View>
      <BannerView
        placementId="YOUR_BANNER_PLACEMENT_ID"
        type="standard"
        onPress={() => console.log('click')}
        onLoad={() => console.log('loaded')}
        onError={(err) => console.log('error', err)}
      />
    </View>
  );
}

Provides a mechanism to fetch a set of ads and then use them within your application. The native ads manager supports giving out as many ads as needed by cloning over the set of ads it got back from the server which can be useful for feed scenarios. It's a wrapper for FBNativeAdsManager

By default the native ads manager will refresh its ads periodically. This does not mean that any ads which are shown in the application's UI will be refreshed but simply that requesting next native ads to render may return new ads at different times. This method disables that functionality.

adsManager.disableAutoRefresh();

Sets the native ads manager caching policy. This controls which media from the native ads are cached before being displayed. The default is to not block on caching.

adsManager.setMediaCachePolicy('none' | 'icon' | 'image' | 'all');

Note: This method is a noop on Android

import { AdSettings } from 'react-native-fbads';

AdSettings contains global settings for all ad controls.

Constant which contains current device's hash id.

Registers given device to receive test ads. When running on a real device, call this method with the result of AdSettings.currentDeviceHash to get test ads. Do not call this method in production.

You should register test devices before displaying any ads or creating any ad managers.

AdSettings.addTestDevice('hash');

Clears all previously set test devices. If you want your ads to respect newly set config, you'll have to destroy and create an instance of AdsManager once again.

AdSettings.clearTestDevices();

Sets current SDK log level.

AdSettings.setLogLevel(
  'none' | 'debug' | 'verbose' | 'warning' | 'error' | 'notification'
);

Note: This method is a noop on Android.

Configures the ad control for treatment as child-directed.

AdSettings.setIsChildDirected(true | false);

If an ad provided service is mediating Audience Network in their sdk, it is required to set the name of the mediation service

AdSettings.setMediationService('foobar');

Sets the url prefix to use when making ad requests.

AdSettings.setUrlPrefix('...');

Note: This method should never be used in production

Gets the current Tracking API status. As of iOS 14, Apple requires apps to only enable tracking (advertiser ID collection) when the user has granted tracking permissions.

Requires iOS 14. On Android and iOS versions below 14, this will always return 'unavailable'.

const trackingStatus = await AdSettings.getTrackingStatus();
if (trackingStatus === 'authorized' || trackingStatus === 'unavailable') {
  AdSettings.setAdvertiserIDCollectionEnabled(true);
}

The tracking status can return one of the following values:

• 'unavailable': The tracking API is not available on the current device. That's the case on Android devices and iPhones below iOS 14.
• 'denied': The user has explicitly denied permission to track. You'd want to respect that and disable advertiser ID collection.
• 'authorized': The user has granted permission to track. You can now enable advertiser ID collection.
• 'restricted': The tracking permission alert cannot be shown, because the device is restricted. See ATTrackingManager.AuthorizationStatus.restricted for more information.
• 'not-determined': The user has not been asked to grant tracking permissions yet. Call requestTrackingPermission().

Requests permission to track the user. Requires an NSUserTrackingUsageDescription key in your Info.plist. (See iOS 14 Tracking API)

Requires iOS 14. On Android and iOS versions below 14, this will always return 'unavailable'.

const trackingStatus = await AdSettings.requestTrackingPermission();
if (trackingStatus === 'authorized' || trackingStatus === 'unavailable') {
  AdSettings.setAdvertiserIDCollectionEnabled(true);
  AdSettings.setAdvertiserTrackingEnabled(true);
}

Enables or disables personalized ads tracking on iOS 14+. See Facebook docs on Advertising Tracking Enabled For Audience Network

Requires iOS 14. On Android and iOS versions below 14, this will always be no-op. Important: FB won't display adds unless this is set to true.

AdSettings.setAdvertiserTrackingEnabled(true);

Enables or disables automatic advertiser ID collection. Since the iOS 14 API was introduced, you might want to disable advertiser ID collection per default (in Info.plist), and only enable it once the user has granted tracking permissions.

AdSettings.setAdvertiserIDCollectionEnabled(true);

In order to see ads you will have to create your own placementId and use it instead of the one provided in the examples. This is our internal set up that doesn't work for any developers outside of Callstack.io organisation. This is because of Facebook not showing test ads to outside collaborators in the development mode.

$ npm install

Because of the way example project is set up (custom packager arguments), you'll have to start it explicitly before any other command

$ cd ./example && npm start

$ cd ./example && npm run ios
$ cd ./example && npm run android

Some of the API explanations were borrowed from Facebook SDK documentation.