Summary

The Evergreen Dashboard allows mobile developers to manage the behavior of the Evergreen SDK. Changes that can have a meaningful impact on user engagement and monetization in your app can be made at any time, without the need to update your SDK integration.

Background

There are four main entities in the Evergreen Panel. Together they make up the acronym SERF:
  • Segments – cohorts of users defined by one or more rules. For example, you can create a "Non-Payers" Segment defined by the rule "Payer Profile equals Non-Payer" or a "Males" Segment tied to the rule "Gender equals Male."  These rules are set up using parameters passed to our SDK. For more information on how to pass these parameters in your integration, consult our Technical Documentation
  • Events – key moments in your app. Events should be fired in places where user engagement or monetization flows might be triggered. For example, you might integrate an "out_of_currency" Event that fires when the player runs out of currency, or a "level_up" event that fires when the player gains a level. Consult our Technical Documentation for information on how to integrate Events. Actions, created within each Event in the Merchant Panel, determine what actually happens when the Event fires. Continuing with the previous example, you can create an Action for the "out_of_currency" Event that triggers the Offer Wall to open when it fires, or a more complex one for the "level_up" Event that triggers an interstitial video to show for the "Non-Payers" Segment 1 out of every 5 times it fires
  • Rewards – currency, items, unlocks, and other benefits the user can receive from engaging with your app. Rewards are tied to Events in Actions
  • Formats – what gets shown to the user when an Action is triggered for an Event. Examples include an Offer Wall, a video interstitial, or an "Engage" touchpoint that presents the user with a local deal or coupon. We frequently add new Formats to our platform, and these can be tied to Events from the Evergreen Panel at any time

Getting Started

1. Create an App

Navigate to the "Apps Console", then "My Apps" tab and create a new app with the "+ App" button at the top of the page. Fill in basic information about the app in the "App Settings" tab. Make a note of the "App Key" value - you will need to use this in your integration. Also note the "Client-side Rewards" value. If this value is "Yes" we will reward users via our Rewards UI, client-side. If it is "No", you need to provide a server-side callback for any Rewards you configure. For more information, see "Configure Rewards" below. Make sure to save your settings at the bottom of the page before continuing further.

app_settings2

2. Add Events

In the Events tab, add new Events using the "+ Event" button. The value you enter in the "Name" field must match the Event name you used in your integration. You can immediately tie the Event to an Action, or you can wait until you have finished other steps of the configuration. In this example, we only enter Event names to start. adding_events

3. Configure Rewards

If you would like to provide currency or item (including unlocks) rewards to your users when they interact with a TrialPay product, head to the Rewards tab and add a new currency or item Reward. If you set "Client-side Rewards" to "Yes" in the App Settings tab, you can also optionally set up a server-side callback for rewards notification. If you set "Client-side Rewards" to "No", you must provide a Callback URL. We will ping this Callback URL for each completed offer that issues a Reward.

4. Define Segments (Optional)

To target Actions to cohorts of users in the Events tab, create Segments in the Segments tab. This is an optional step, as Actions can be targeted to all users instead of a particular cohort. You can create one or more rules per Segment, all of which must be true for a given user to be assigned to that Segment. The order of the Segments in this tab matters: Segments cannot overlap and those higher in the list take priority. This means, for example, that if a user fits into both the "Males" and "Non-payers" Segment, and the "Non-payers" Segment is listed first, that user will be considered a "Non-payer." You can change the order of segments at any time by clicking the up or down arrows on the right side of the collapsed Segment tiles. adding_segments

5. Create Actions

Time to bring it all together. Create Actions by editing your Events in the Events tab. There are two modes when creating Actions for a given Event: simple and advanced. You can toggle between these options using the "Use advanced event configuration" checkbox. In simple mode, you can only create one Action for an Event - made up of a Format and a Reward. This Action will be targeted to the special "All Users" Segment. In this first example, we use simple mode to have the "out_of_currency" Event trigger a coin-rewarding Offer Wall for all users when it fires. adding_simple_action In advanced mode, you can tie multiple Actions to the Event. In addition, advanced mode Actions are more complex than those in simple mode: in simple mode an Action is made up of a Format and Reward, while in advanced mode, an Action is made up of a Segment, a Frequency, and one or more Format+Reward pairs. This is easiest to understand with an example. Here, we configure the "level_up" Event to show an interstitial video to the "Non-Payers" Segment 1 out of every 5 times it fires, and to trigger an Offer Wall instead if videos are not available. We could also add an additional Action for another Segment like "Payers" later on (not shown). adding_advanced_action

Wrapping Up

The Evergreen Merchant Panel is a powerful tool to control the behavior of the Evergreen SDK. We encourage you to try different configurations to find what works best for your app. For more information on how to make use of the features outlined above, contact your TrialPay account manager.