- Supported Ad Formats
- Download and Integration
- Set Up Flurry on the MoPub Dashboard
- Network Reporting and Auto CPM
- Migrate Flurry from Custom Native Setup
- Set Up Reporting for Flurry
- Test Ad
- Yahoo! Gemini Custom Properties
- Additional Support
Flurry adapters are not certified for MoPub SDK 5.13.0+. Previously certified adapters, SDK and UI connection will not work for publishers upgrading to MoPub SDK 5.13.0+. As such, publishers mediating Flurry have to migrate to the Verizon Media supported connection prior to upgrading to MoPub SDK 5.13.0+. Please find Verizon adapters here and Verizon integration instructions here. We are also removing Flurry UI connection for all new accounts and publishers that are not currently mediating Flurry. Note: Previously certified MoPub and Flurry SDK and adapter combinations will continue to work but only with MoPub SDK v5.12.0 or older.
This guide is intended for publishers who want to use the MoPub SDK to load and display ads from Flurry 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 Flurry. For the latest support, visit the Flurry home page.
Download and Integration
To download the Flurry adapters, navigate to the Mediation Integration Tool. You must also download the Flurry SDK:
For the latest download and integration instructions, consult Flurry’s tutorials before you integrate the SDK and adapters.
Android Integration Help
Flurry adapters are released as an Android Archive (AAR) file starting from version 184.108.40.206. The AAR includes the required Manifest data for Flurry. As a result, you no longer have to update your AndroidManifest manually for any generic data, such as permissions and Activities. Any other app-level placement configuration required by Flurry must be manually entered into the AndroidManifest.
Set Up Flurry on the MoPub Dashboard
Ad Unit Nameare required.
Ad Spaceis backwards-compatible with
Ad Unit Name.
Network Reporting and Auto CPM
To enable Flurry network reporting and Auto CPM, you must enter the Programmatic API Token.
To find the Programmatic API Token, from the Manage section, navigate to Users and create a new Programmatic User.
This setup is required to take advantage of Auto CPM.
Migrate Flurry from Custom Native Setup
API Key(if applicable) from the old custom native connection to the supported Flurry instance.
MoPub will initiate the following Flurry mediation adapter class names to render the ads:
If you are manually entering these class names, migrate to the new network setup and pause the “Custom Native Network.” If you are using your own mediation adapter class names, have both the old custom native network and the new Flurry network UI set up for backward compatibility.
Important: During migration, make sure the custom native network and the Flurry network are not both live at the same time, because this may impact your revenue.
Set Up Reporting for Flurry
For more information about accessing your Programmatic API token, click here.
While testing your SDK integrations and network setups, we recommend that you leverage test ad placements for a consistent fill rate. To set up test mode, follow the instructions in Flurry’s test ad article.
Yahoo! Gemini Custom Properties
For inquiries and support, email Flurry support.
Last updated June 23, 2020
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.
© 2020 MoPub (a division of Twitter, Inc.)