At a glance: WakeApp, an AppsFlyer ad network integrated partner, is a global company specializing in mobile marketing.
To configure your campaigns with Wakeapp, follow the steps below.
Setting up WakeApp
Prerequisite: Before setting up the integration, make sure you contact the partner and open an account with them.
To activate or edit the integration:
To activate: In AppsFlyer, from the side menu, select Collaborate > Partner Marketplace.
To edit: In AppsFlyer, from the side menu, select Collaborate > Active Integrations.
- Search for the partner and select it.
- Click Set up integration. You’re directed to the Active Integrations setup page.
- In the Integration tab, turn on Activate partner.
Note: The toggle must stay on (activated) for as long as you work with the partner. Learn more about partner activation.
- Complete the configuration using the relevant tabs, as described below.
The Wakeapp configuration includes 3 active tabs: Integration, Attribution link, and Permissions. Click on the items below to read about the tabs setup.
For a detailed description of the Partner Configuration Window Header, click here.
- The General Settings step in the Integration tab is mandatory for all partners
- All the rest of the steps are either descriptive or optional
The Integration Tab is divided into different sections as described below.
On the first visit here, you will need to turn on the Activate Partner toggle to enable setup of the Integration tab's parameters. The toggle MUST be on for as long as you work with the partner.
For more details about partner activation please click here.
Send automatic postbacks to Wakeapp following user installs and re-engagements. Use this section to define the source of the users that allow sending these postbacks.
Select Only events attributed to this partner for events coming only from users attributed to Wakeapp.
In-app events settings
In this section, you can map your AppsFlyer events with Wakeapp via postbacks.
- Toggle In-App Event Postbacks to ON
- Select the Sending Option for all SDK-defined events.
- Only events attributed to this partner for events coming only from users attributed to this partner
- Events attributed to any partner or organic to have your entire user base available to be reported to the partner
- Click Add Event to add an SDK Event to the list
- Complete the following parameters:
|SDK Event Name
|The name of the event, as received by AppsFlyer either from the SDK integrated with your app or from server to server events.
Tip - If you don't see the event you want in the list, make sure to activate the event on a device with a non-organic installation and recheck.
|Partner Event Identifier
|The unique name or ID of each event, as defined on Wakeapp's side.
Obtain the corresponding Event ID from Wakeapp and set the text field.
When unchecked - sends all the parameters of the rich in-app event to the partner, except for the revenue parameter, which is contained in the af_revenue parameter.
When checked - sends all the parameters including the revenue value (if it exists in the event).
Attribution link tab
This tab is divided into different sections:
Attribution link parameters
In this section, select which parameters you want to add to the attribution link.
Adding parameters to the attribution link here enables you to later perform thorough drill-down analyses. Parameters that are already defined on the attribution link can be edited by adding them and their new values here.
Campaign - add it to compare different campaigns running with Wakeapp.
Attribution link parameter: c
Adset - set ad set names to compare different ad sets within specific Wakeapp campaigns.
Attribution link parameter: af_adset
Ad Name - set ad set names to compare different creatives within specific ad sets within specific campaigns Wakeapp.
Attribution link parameter: af_ad
Site ID and Sub Site ID - set Site ID parameter to attribute installs to specific publishers. If many publishers exist, we advise on limiting the number of used site IDs and using the sub-site ID parameter, to avoid exceeding the site ID limitations.
Attribution link parameters: af_siteid and af_sub_siteid
Subscriber Parameters - use any of the 5 subscriber parameters to insert useful values. Note that these parameters get parsed and appear in the raw data report, which makes them very handy for performing data aggregation or filtering.
Attribution link parameters: af_sub1, af_sub2, af_sub3, af_sub4, af_sub5
Add any other parameter to the attribution link simply by typing it in a new parameter box. For more information about AppsFlyer's Attribution Link Structure and Parameters.
This slider allows you to set the maximum time from click to install. Only installs (first launches) that take place within the lookback window may be attributed to Wakeapp.
Attribution link parameter: af_click_lookback
More details about the click lookback window here.
Click attribution link
This is the attribution link that contains all the setup information you have set for it. Send it to Wakeapp to be activated when leads click on a corresponding ad.
Cost data is not supported in the integration with this partner.
Ad revenue tab
Ad Revenue is not supported in the integration with this partner.
In this tab, you can select the permissions to grant Wakeapp, whether the partner acts as an ad network, agency, or even both. Note that even if attribution is disabled for Wakeapp, the permissions tab is active and you can grant control to Wakeapp.
Use these toggles to give the agency permissions to handle its own configuration for your app:
- Main toggle - Set to On to reveal the agency permissions options
- Allow access to your retention report - only to the agency's own retention data
- Allow access to aggregate organic data
- Allow to configure in-app event postbacks - permit the agency to setup in-app event postbacks mapping to itself on the integration tab
Learn more about granting agency permissions.