At a glance: ironSource, an AppsFlyer integrated partner, builds monetization, engagement, analytics, and discovery tools for app developers, device manufacturers, mobile carriers, and advertisers. In addition to click-based mobile attribution, ironSource also offers cost, ad revenue, retargeting and view-through attribution, which you can record with AppsFlyer.
Note As an all-installs network, ironSource prefers to receive postbacks for all new installs of your app from ANY source, including organic. To do so, select Events attributed to any partner to send all install postbacks to ironSource.
The setup is done from the partner integration setup page, but to find the partner you must first go to the marketplace.
Note
Before setting up an integration, make sure you contact the partner and open an account with them.
To activate the integration:
- Go to the Marketplace: From the top menu of any AppsFlyer page, click Marketplace.
- Search for the partner and select it.
- Click Set up integration. You’re directed to the integration 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. - Complete the configuration using the relevant tabs, as described below.
ironSource's configuration window includes 5 tabs: Integration, Attribution link, Cost, Ad Revenue, 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.
Tip
- The General Settings step in the Integration tab is mandatory for all partners
- All the rest of the steps are either descriptive or optional
Integration tab
Activate partners
On the first visit here, you will need to turn on the Activate Partner toggle to enable setup of the integration tab parameters. The toggle must stay on for as long as you work with the partner.
For more details about partner activation please click here.
Advanced Privacy
For iOS apps only, when Advanced Privacy (for iOS 14.5+ and later) is turned on, you can control what data is shared with ironSource via postbacks and reports.
Transaction ID
For iOS apps only, when Share SKAN transaction ID is turned on, you're allowing AppsFlyer to share the transaction ID of SKAdNetwork postbacks with ironSource. By doing so, ironSource could decode your SKAdNetwork Conversion Values.
Note
For SKAN interoperation with AppsFlyer, contact your ironSource account manager to enable sending SKAN data to MMPs.
General settings
Advertiser ID
ironSource connects with AppsFlyer via a unique advertiser ID (6-digit number) and a password. If you don't already have the advertiser ID and password, you must obtain them from ironSource to continue with the integration. Otherwise, copy the ID and the password and paste them into the respective fields.
Install and Re-engagement attribution
These two toggles enable attributing to ironSource new installs and re-attributions of users who viewed your ad but didn’t click on it. Learn more about view-through attribution.
To attribute new installs:
- Turn on Install view-through attribution.
- Configure the length of the view-through lookback window in the Attribution link tab.
To attribute new re-engagements of existing users:
- Turn on Re-engagement view-through attribution.
- Configure the length of the view-through lookback window in the Attribution link tab.
Default postbacks
Send automatic postbacks to ironSource 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 ironSource.
Select Events attributed to any partner, or organic to have your entire user base available to be reported to ironSource.
Note
As an all-installs network, ironSource prefers to receive postbacks for all new installs of your app from any source, including organic. To do so, select Events attributed to any partner, or organic to send all install postbacks to ironSource.
In-app event postbacks
Configure mapping of in-app events with ironSource events, sent via postbacks:
- Turn on In-app event postbacks.
- Click Add event to add an SDK or server-to-server event to the list. The following table describes the fields to complete:
Parameter name Description AppsFlyer event The name of the event, as received by AppsFlyer either from the SDK integrated into your app or from server-to-server events.
Tip: Don't see the event you are looking for?- Make sure to activate the event on a device with a non-organic installation, and recheck.
- Type it in AppsFlyer event, then click Create custom. Read more about custom event mapping.
mapped to partner event The unique name or ID of each event, as defined on the partner's side. Possible mapping configurations are:
- Text field: Get the corresponding event ID from the partner.
- Drop-down box: Select the most suitable pre-defined AppsFlyer event.
- As is: Send the events as they are, without name mapping.
for users from Select the sending option for the event:
- This partner only: Send postbacks only when this event is attributed to this partner.
- All media sources including organic: Send postbacks for events attributed to any partner, as well as organic events.
including - No data (default): Send only the event itself without any event values.
- Values and revenue: Send all the event parameters, including the revenue value (if exists in the event).
- Values without revenue: Send all the parameters excluding the revenue value.
- [Optional] Click the Add condition
icon to set conditions for an event.
- Click Save integration.
- [Optional]After saving the integration, while remaining on the configuration page, you can integrate more of your apps with the partner:
- From the top-left corner, under the partner name, click the app name to open the list of apps.
- Select a different app from the drop-down list.
- Repeat the integration steps for the selected app.
Note
- For iOS apps only: Your control over data shared with the partner via postbacks and reports depends on the Advanced Privacy (for iOS 14.5+ and later) toggle state.
- You can send ad revenue postbacks to ironSource so they can optimize campaigns using ad revenue data:
- Event name: af_ad_revenue
- Mapped to: adRevenue
Attribution link tab
Generate and save attribution links and send them to the partner for attributing specific campaigns, ad sets, or single ads - both for UA and retargeting campaigns. You can use either a single-platform link or a OneLink.
More about attribution link structure and parameters.
To generate an attribution link, follow these instructions.
Read more about how ironSource defines clicks and views.
Cost tab
AppsFlyer gets cost details by API. See the ad network cost integration table for full details on the supported dimensions, metrics, and features. Note: Cost data requires an ROI360 subscription.
To enable the cost API:
View your cost API status and the last time AppsFlyer managed to pull matching cost data in either the cost (and ad revenue) integration status dashboard, or in the individual ad network dashboard.
Ad revenue tab
If you display ads in the app sent by the partner this section is relevant.
- ironSource offers aggregate and user-level ad revenue granularity.
- Potential discrepancy when using user-level granularity: Ad revenue data is pulled daily at 14:00 UTC from ironSource and contains yesterday's data. ironSource may continue to update the data after we pull it. This causes a discrepancy between the AppsFlyer and ironSource data.
Learn more about ad revenue attribution.
To enable the ad revenue API:
- Follow these integration instructions.
Permissions tab
In this tab, you can select the permissions to grant ironSource, whether the partner acts as an ad network, agency, or even both. Note that even if attribution is disabled for ironSource, the permissions tab is active and you can grant control to ironSource.
Use these toggles to give the ad network permissions to handle its own configuration for your app:
Ad network permissions
- Allow to configure integration - permit the partner to set up the integration tab (except in-app event postbacks)
- Allow to configure in-app event postbacks - permit the partner to setup in-app event postbacks mapping to itself on the integration tab
- Allow access to your retention report - only to the partner's own retention data
- Allow access to your aggregate loyal user data - only to the partner's own loyal user data
- Allow access to your aggregate in-app events data - only to the partner's own in-app events data
- Allow access to your aggregate revenue data - only to the revenue data attributed to the partner
- Allow access to your Protect360 dashboard - only to the partner's own Protect360 data, and providing the feature is enabled for the advertiser
Learn more about granting ad network permissions.
Agency permissions
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.