Manage Rewarded Options
If you plan to use a rewarded integration with your Flurry ads, you will need to designate the Ad Space type in which you'd like display rewarded ad units, as well as define what rewards you plan to give to the user.
Select Your Ad Space
Flurry provides several options for developers who choose to host rewarded promotions within their app. Rewarded inventory can be served into both banner size Ad Spaces, as well as takeovers. Flurry provides rewarded solutions for two ad types: With Clips video ads, users are offered a reward for watching a video. Users are rewarded after the video view is complete. Users can also view a further promotion, either a link to a mobile web site, or a download opportunity for the app that has been advertised. Neither of these actions are rewarded. On the Android platform users can be rewarded for downloading and launching a new app. Either of these promotions can be hosted in a range of ad units, however, one of most popular integrations remains the storefront area of an app. In a storefront users can generally purchase goods, get virtual currency, and see opportunities to take actions in order to earn free currency or goods. In the storefront the most effective ad unit is the Catalog View. This web view ad unit lists a number of ads that a user can interact with in order to earn rewards. Most often developers will create a button within their app, stating something like "click here for free points," which launches the Catalog view. If you have selected "Rewarded" as the ad mix you'd like integrate, and you have designated your Ad Space placement to be "Full Screen," you will have the option to display a full screen takeover interstitial ad unit, which displays a single promotion, or a Catalog View.
Define Your Rewards
If you have selected your AppCircle ad mix within your Ad Space to be “Rewarded,” or “Let Flurry Decide”, you will be prompted to define the rewards that you will give a user for engaging with a Flurry promotion. To define your rewards you will need to go to the Manage tab on the left nav, and click Rewarded Options. YOU WILL NOT BE ABLE TO SERVE REWARDED ADS WITHOUT FILLING OUT YOUR REWARDED OPTIONS. In the Rewarded Options tab you will see a table that lists projects for which you can define rewards. Click “Create Reward” in the right-side column. For developers who already have callbacks set up for rewards wither older integrations, your details will be listed on this page. You cannot, however, edit these settings. To access this new functionality, drop in a new Ad Space, download the latest SDK, and create your rewards.
You will see a new page for the project you have selected. The first field to complete is the reward name. This is the name of the virtual good or currency that you will give to your user for engaging with a Flurry promotion. The name will display in the Ad Space. The reward name limit is 13 characters, not including the quantity. Next, you can select a square icon as a visual example of the reward or currency to upload. This choice is optional, but Flurry highly suggests you include an image in order to boost conversion rate. This image will appear within the ad unit along with the reward type and quantity.
You will next select the quantity/conversion rate of your reward or currency. Add the amount you’d like to credit the user for every $1 you receive from Flurry. When a user sees your rewarded ad space they will see how much currency or reward that they will receive for converting on the presented ad.
The final step to define your rewards is to paste your callback URL into the bottom field. The callback URL is the notification Flurry sends to your servers with information to credit a user for converting on a rewarded ad. When you add your callback URL be sure to format the string with key parameters for awarding your users.
Callback URL Security
Flurry will add the following parameters to the end of the callback URL automatically:
fguid - a unique identifier for the action to be rewarded
rewardquantity - an integer number denoting the number of reward units to be granted to the user
fhash - an md5 hash which can be used to verify that the callback really came from Flurry and that the reward quantity is correct
The fhash value is the following:
md5( fguid:rewardquantity:secretkey )
Here is an example using realistic looking input:
The URL that the Flurry service will hit in this example would be:
We recommend that you verify that the fhash value equals:
md5( f2dcd862-f2c7-4e61-beb3-a7e8641bc944:10:865B906F71E61D1C6FAF280A5F06C9037A9AC24D )
which in this case equals: 89e602b688ea323c2e22fe2d2e514f6f.
Doing so ensures that the callback really came from Flurry because only we and you know your secret key.
Because Flurry wants to ensure that your users get their rewards there is a possibility that you could get the same callback URL twice for the same rewarded action. Therefore we also recommend that you store the fguid on your end and ensure that you only give your users one reward for each unique fguid value that you recieve from our callback service.
You can see your application's secret key by going to the Publishers tab -> Manage -> Rewarded Options page in the Flurry Developer Portal. Or simply click on this URL:
Note that there is a different secret key for each of your applications!