At a glance: Vungle, an AppsFlyer ad network integrated partner, offers an in-app video advertising platform for performance marketers. In addition to click-based mobile attribution, Vungle offers cost and view-through attribution, which can be recorded with AppsFlyer.
Vungle integration in AppsFlyer
To configure the partner integration:
- Go to Configuration > Integrated Partner.
- In the list of integrated partners, search for Vungle.
- Click Vungle to open the configuration page.
- Set tabs as needed:
- [Mandatory] Integration: Configure the integration (connection) between Vungle and AppsFlyer.
- Attribution link: Generate attribution links to be used with ads on Vungle.
- Cost is not active for this partner.
- Ad revenue is not active for this partner.
- Permissions: Grant permissions to Vungle to view and manage your data in AppsFlyer.
Note: You can grant permissions without the need to complete the Integration tab.
Read more about how to set up the Partner Configuration Window Header.
The following sections explain how to configure each tab.
Connect to Vungle by activating and setting parameters in the integration tab. Vungle must supply its unique network ID, app_id; this is necessary in order to connect with AppsFlyer.
Vungle is an ALL-installs network; they want postbacks for all new app installs, from all sources (including organic). To send all install postbacks to Vungle, select Events attributed to any partner.
To configure the integration:
- Enable Activate partner. See more information about partner activation.
- Under General settings enable/disable View-through attribution:
- [Default] Enable: Activate to attribute view-through installs to Vungle. The length of the lookback window is configured in the Attribution link tab.
- Disable: View-through installs from the partner are not attributed.
Default postbacks: AppsFlyer sends postbacks to Vungle after user installs and re-engagements. Use this section to define users who are the source of these postbacks. Under Sending Option,
Select Only events attributed to this partner for events attributed to Vungle users.
Select Events attributed to any partner or organic to make your entire user available for reporting to Vungle.
- In-app events settings: To send postbacks to Vungle, map in-app event IDs to Vungle's. Configure the parameters as follows:
- Enter the Vungle app_id.
- Enable In-app events postbacks.
- Select a Sending Option.
- Click Add event to add an SDK event to the list. Complete the parameters as described in the following table.
|SDK event name||
Event name received by AppsFlyer from:
Tip: If a needed event isn't in the list, perform a non-organic installation on a device, then check again.
|Partner event identifier||
Unique event name or ID as defined by Vungle.
Get from Vungleevent ID corresponding to your SDK event and insert it in the text field.
[Default] Not enabled: AppsFlyer sends all the in-app parameters to Vungle, except for the revenue parameter (
Enabled: AppsFlyer sends all the in-app parameters including, when available, the revenue amount.
- Parameters let you perform drill-down analyses.
- Existing parameters can be edited.
|Attribution link type||Link activation||Lookback window|
A lead clicks on an ad served by Vungle
The click-through lookback window is the maximum time from click to install.
Vungle gets an attribution if a lead clicks and installs an app before the lookback window expires.
|Impression||A lead views an ad served by Vungle.
Read more about how Vungle defines clicks and views.
The view-through lookback window is the maximum time from impression to install.
Vungle gets an attribution if a lead views (impression) an app and then installs before the lookback window expires. This applies if there are no other relevant ad clicks.
Learn more about link structure and parameters.
Typical link parameters:
Name of the campaign.
Add it to compare between campaigns running with Vungle.
Name of the ad set.
Use to differentiate between ad sets within Vungle campaigns.
Name of the specific ad.
Use to differentiate between ad set creatives found within Vungle campaigns.
Sub Site ID
Publisher ID used to attribute installs to specific publishers.
Recommended practice! If there are many publishers,
|Subscriber parameters||af_sub1 up to af_sub5||
Use to insert values:
To generate the attribution links:
- Select a name from the Parameter name drop-down list, then set the parameter value.
- To add more parameters, click Add parameter and repeat the previous step.
- Set the duration of the click-through lookback window.
- Set the duration of the view-through lookback window.
- Copy the click and impression attribution links to use in your Vungle campaigns.
Note: AppsFlyer does not save partner links.
AppsFlyer gets cost details by API.
|Geo||Media source||Campaign||Adset||Ad||Site ID|
Before you begin:
- In your Vungle dashboard get your API credentials. You need:
- Reporting API key
- Reporting API ID
To enable the cost API:
- In the Cost tab, enable Get Cost Data.
- Complete the credential fields.
- Click Save Cost.
- Click Test Connection
- The message API connection verified displays.
- The API is active. AppsFlyer collects data from the partner 6 times a day, on average once every four hours.
- Make sure the attribution data sent includes the correct campaign ID (not just campaign name) so that cost data can be matched,
- Cost data syncs status and messages
This section is only relevant for publishers who display Vungle ads to users. It is important to measure the engagement of users acquired from different sources to find the most profitable sources.
- Go to the Ad Revenue tab.
- Enable Get Ad Revenue Data.
- Enter the Vungle App ID.
- Enter the Secret Key.
- This is an API key used to pull in-app advertising revenue data from Vungle.
- See Vungle's info about retrieving the API key.
- Select the type of aggregated ad revenue data you want to receive: Attributed revenue and/or Aggregated monetization revenue:
- Attributed Revenue: Revenue based on the user acquisition source.
In Event Source, select in-app event that represents the ad monetization trigger. This event is usually sent for each ad impression. For example, ad watched or video watched.
- Aggregated monetization revenue: Revenue based on the ad source.
- Attributed Revenue: Revenue based on the user acquisition source.
- Click Save Ad Revenue.
- Click Test connection.
- Do one of the following:
Learn more about ad revenue/monetization measurement.
You can give Vungle permission to view information or configure changes in the integration. The type of permission varies according to the business relationship (ad network/ad agency) you have with Vungle.
Note: It is possible to give Vungle permissions even if there is no active integration with them.
Ad network permissions
To enable ad-network permissions:
- Enable Ad network permissions.
- Give Vungle team members access to one or more of the following:
|Allow to configure integration||Set up the integration tab (except in-app event postbacks).|
|Allow to configure in-app event postbacks||Set up in-app event postbacks that are mapped to integration tab.|
|Allow access to your retention report||Partner's retention data|
|Allow access to your aggregate loyal users data||Partner's loyal-user data|
|Allow access to your aggregate in-app events data||Partner's in-app events data|
|Allow access to your aggregate revenue data||Revenue data attributed to the partner.|
|Allow spend ingestion|
|Allow access to your Protect360 dashboard||[If enabled] Partner's Protect360 data|
Learn more about giving ad network permissions.
You can allow Vungle to configure your app as an agency.
To enable agency permissions:
- Enable Agency permissions.
- Give Vungle agency access to one or more of the following:
|Allow access to your Protect360 dashboard||[If enabled for your account] Agency's Protect360 data|
|Allow access to your retention and cohort reports||Agency's retention and cohort data|
Allow access to aggregate organic data
|Agency's aggregate organic data|
|Allow to configure in-app event postbacks||Set up in-app event postbacks that are mapped to the integration tab.|
Learn more about granting agency permissions.