Flurry Publisher Integration
In 5 minutes, you can complete your integration as a Flurry publisher and receive all of Flurry’s ad products, including AppCircle, AppCircle Clips, AppCircle Re-Engagement, and AppSpot, Flurry’s ad network mediation and adserving platform. Integration requires two steps.
Step 1: Creating an ad space.
To participate as a publisher with Flurry, the first step is to create an Ad Space. An Ad Space is an area within your app that is designated to display ads. You can create as many Ad Spaces as you like, and customize the size, look, and serving rules of each.
By default, you will receive yield-optimized ads from Flurry’s AppCircle network, but can also enable mediation of other ad networks such as iAd or AdMob, as well as serve direct-sold campaigns. Mediation and direct-sold ad management are not enabled by default so contact us at email@example.com if you are interested in this functionality.
Use the publisher tab in Flurry's developer portal to create an ad space, as well as define all of your serving logic, see your reporting, and manage your accounting.
Step 2: Integrating the ad space code.
Once an Ad Space is created, you will be given a unique code for that Ad Space. If you are responsible for integrating the code into the client, you can simply drop the code into your view controller. If you are not a developer you can email the code to your integration team, along with the SDK, an upgrade of which is required to participate in Flurry's new ad serving system. Learn more about integration here.
Creating an Ad Space
To create a new ad space, click on Publishers>Inventory>Ad Spaces from the left-hand nav. This page will contain a table of all Ad Spaces created, and columns that indicate the status and basic performance of the particular Ad Space. You can sort by application to organize Ad Spaces, or by any of the columns in the table. To create an Ad Space, click the “Create Ad Space” button at top right.
You will see three modules once you hit the “Create Ad Space” button: Basic Set Up, AppCircle Network, and Advanced Options.
Basic Set Up
Enter a name for the Ad Space, associate it with a project, and select the ad space placement. Placement is where you select the ad size for the Ad Space: Banner Top, Banner Bottom, or Full Screen. Further customized controls of ad unit behavior can be added via delegate definition in the client
Once you’ve filled out the Basic Set Up criteria, you will be prompted with the code for your Ad Space. Copy this unique Ad Space code and paste it into your client code. Learn more about how to integrate your code here. Your code will not change, regardless of how many further changes or edits to your Ad Space. All of that is handled server side. At this point you’re ready to start showing ads.
Configure AppCircle Network Options
Use this section to edit the look and feel of AppCircle ads, as well as designate the ad space as rewarded or non-rewarded.
You have three options available for showing rewarded and non-rewarded ads. If you have a reward system such as currency or virtual goods to give to users, we recommend you choose to enable rewards with “Let Flurry Decide”. This option allows Flurry to show the highest value ad based on AppCircle’s yield optimizer. If you always want to show rewarded ads, select “Rewarded.” If you don’t have a currency, choose “Non-Rewarded”.
If you choose “Rewarded,” or “Let Flurry Decide”, you will be prompted to set up and define your rewards. To learn more about how to manage your rewards, click here.
Use this section to create filters and set serving logic.
Filters your AppCircle ads by by Ad ID, App Name, and Advertiser Name, and Maturity Rating. Note that these filters are set per Ad Space.
Below the filters are serving logic settings. You can edit the Ad Refresh rate, which allows you to specify how often an ad rotates through Flurry's available ads. This is most useful with banner size ads, which persist on a view, and therefore warrant semi-frequent refreshes. You can opt to have the ads pre-cached for a particular ad space. This is a recommended option for app experiences where disruptive takeovers, or interstitial ads are rendered between pages, game levels, or other content areas. Pre-caching ensures that the ad is already loaded before it’s rendered, and therefore has the least load time. For rewarded inventory, such as the catalogue view, this option is less optimal, as users will be returning to the experience to fetch new ads to earn more rewards.