Overview
Attention
Branch's new experience is rolling out in phases, so your interface may differ. This article covers the legacy version of ad partner setup. For the new version, see Ad Partners (New).
ironSource works with the world’s largest mobile game companies, ironSource is developing the industry's leading growth engine for games. With a robust mobile ad mediation platform, mobile ad network, and a data-driven user acquisition platform, ironSource closes the monetization and marketing loop to empower game developers to turn their games into successful businesses. Founded in 2010, ironSource is a global company, with a strong local presence in Tel Aviv, London, New York, San Francisco, Beijing, Shenzhen, Bangalore, Seoul, and Tokyo.
Partner Capabilities
| Capability | Details |
|---|---|
| Company Type | Network |
| Deep Linking | Supported |
| Attribution | All Types |
| Ad Campaign Types | • Retargeting • Acquisition |
| Ad Formats | • Interstitial video • Rewarded video • Offerwall |
| Click Types | • Client-side click • Server-side click |
| Supported Platforms | • iOS • Android |
| Link Wrapping | Not Supported |
| Cost Ingestion Support | Contact support at ironSource for more information. |
| Cost Ingestion Types | Contact support at ironSource for more information. |
| Pricing Models | • CPI • CPCV • CPE (Offerwall) • CPM • CPC |
Before you begin
In order to enable ironSource, you need to have completed the following:
Created a Branch Dashboard.
Have Branch's Performance product enabled for your Branch Account.
Implemented the Branch SDK into your mobile app (iOS | Android)
Running campaigns through ironSource.
Enable ironSource
1. Enable ironSource in Branch
In the Branch Dashboard under Ads > Partner Management, find/search for ironSource. If you're already logged into the Branch Dashboard, you can also click here to go there directly.
Click the Save & Enable button.
2. Configure Postbacks
Enabling ironSource will automatically enable the following postbacks:
- INSTALL
- OPEN
- PURCHASE
- ACHIEVE_LEVEL
- COMPLETE REGISTRATION
- COMPLETE TUTORIAL
You can configure these postbacks or add more under the Postback Config tab.
Send All Events
Optionally, you can check the checkbox for a given postback for sending all events. When checked, all events will be sent regardless of attribution. Otherwise, the postback will only fire for events attributed to ironSource.
Adding Postbacks
Click the Add New Postback button at the bottom of the screen. A modal will appear that will allow you to select an event that you are tracking with the Branch SDKs (including Custom Events).
For more in-depth postback configurations, view our guides:
3. Configure Attribution Windows
After configuring your events, navigate to the Attribution Windows tab to set windows by attribution type.
Recommended Attribution Windows
| Attribution Type | Window |
|---|---|
| click to session start | 90 days |
| click to install | 30 days |
| click to conversion event | 90 days |
| impression to session start | 1 day |
| impression to install | 1 day |
| impression to conversion event | 1 day |
4. Create Branch Ad Link
Next, you'll need to create a Branch Ad Link for your ironSource campaigns in order for Branch to properly attribute conversions.
The Branch Ad Link you create will be placed in your ironSource campaign.
5. Verify Data in Branch
After launching your ironSource campaigns, and conversions begin to happen, you'll want to verify data is being sent from Branch to ironSource. You can look at the Branch Dashboard's Liveview Webhook Records and apply the following filter:
| Filter | Operator | Value |
|---|---|---|
| ad partner (3p) | equals | a_ironSource |
Once applied, data should flow through the Liveview, and you can see the data being sent to ironSource from Branch.