- Supported Ad Formats
- Download and Integrate
- Set Up Flurry on the MoPub Dashboard
- Network Reporting and Auto CPM
- Migrate Flurry from Custom Native Setup
- Set Up Reporting for Flurry
- Test an Ad
- Yahoo! Gemini Custom Properties
- Additional Support
Flurry adapters are not certified for MoPub SDK v5.13.0+. The previously certified adapters, the SDK, and the UI connection will not work for publishers who upgrade to MoPub SDK v5.13.0+. Publishers mediating Flurry must migrate to the Verizon Media-supported connection before they upgrade to MoPub SDK v5.13.0+. Please find Verizon adapters here and Verizon integration instructions here. We are also removing the Flurry UI connection for all new accounts and publishers that are not currently mediating Flurry. Previously certified MoPub and Flurry SDK and adapter combinations will continue to work, but only with MoPub SDK v5.12.0 or older.
If you plan to use the MoPub SDK to load and display ads from Flurry via mediation, use this article for integration instructions and information unique to the ad network. To learn more about how MoPub mediation works, refer to our MoPub Network Mediation article.
Supported Ad Formats
Flurry currently supports the following ad formats. For support information, visit the Flurry home page.
|MoPub Formats||Flurry Ad Formats|
Download and Integrate
To download the Flurry adapters, navigate to the Mediation Integration Tool. You must also download the Flurry SDK:
Flurry adapters are released as an Android Archive (AAR) file starting with version 22.214.171.124. The AAR includes the required Manifest data for Flurry. As a result, you no longer need to update your
AndroidManifestmanually for any generic data, such as permissions and Activities. Any other app-level placement configuration required by Flurry must be manually entered into the
For the latest download and integration instructions, consult Flurry’s tutorials before you integrate the SDK and adapters.
Set Up Flurry on the MoPub Dashboard
Ad Unit Nameare required.
Ad Spaceis backwards-compatible with
Ad Unit Name.
Network Reporting and Auto CPM
The following setup is required to take advantage of Auto CPM. To enable Flurry network reporting and Auto CPM:
In the Network settings page for Flurry:
enable reporting access
provide the Programmatic API Token
To find the Programmatic API Token, in Flurry’s Manage section, navigate to Users and create a new Programmatic User.
Navigate to the Auto CPM preferences page and turn on 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, make sure that both the old custom native network and the new Flurry network UI are set up for backward compatibility.
Important: During migration, make sure that 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
Refer to Yahoo! Flurry help for more information about accessing your Programmatic API token.
Test an Ad
As you test your SDK integrations and network setups, we recommend that you leverage test ad placements to ensure a consistent fill rate.
To set up test mode, follow the instructions in Flurry’s testing article.
With test mode enabled, you can request ads using the ad unit ID you created earlier for this purpose and receive a Flurry test ad. Be sure to disable test mode after testing!
Yahoo! Gemini Custom Properties
For inquiries and support, email Flurry support.
Last updated August 24, 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.)