Ironsource

Branch Certified Partner

Overview

IronSource

This guide will walk you through how to setup your campaigns with IronSource using Branch Universal Ads and track ad conversions across every device, platform, and channel.

1. Complete Universal Ads Prerequisites

DEVELOPER MAY BE REQUIRED

The following Universal Ads prerequisite includes providing URI schemes and other components that may require a developer:

DEVELOPER REQUIRED

The following Universal Ads prerequisites involve app code changes:

2. Enable the Integration

  1. Visit the Ads page on the Branch dashboard.
  2. Select Partner Management from the sidebar.
  3. Search for your Universal Ads Partner.
  4. Select Ironsource, provide your Advertiser ID and Password and hit Save & Enable.

3. Enable Postbacks

Basic postbacks will automatically be activated for events like Install and Purchase when you enable your ad partner.

You can then add additional postbacks, for example, if you wanted to add postbacks for custom events that are specific to your app like Account Created.

You can also edit postbacks if there's additional data you really need to pass along to your ad partner.

3a. Resetting Postbacks

There may be times when you need to reset a partner's settings; i.e. when a partner updates their postback templates or when perhaps you've made a mistake during partner setup. Resetting a partner's settings allows you to re-enable the partner integration with the correct information to accurately measure and attribute conversion.

Disables Ad Partner

Resetting partner settings will:

  • Disable the ad partner.
  • Clear out all of your saved credentials and postbacks that are already setup.
  • Return the ad partner to its basic configuration.

To reset Ironsource's postbacks:

  1. Click on the Account Settings tab.
  2. Click the Reset All Settings button in the right-hand corner.

Updated about a month ago


Ironsource


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.