Skip to content



We've partnered with Localytics to provide an easy way to deliver Branch installs and attributions to your Localytics dashboard. This is great for segmenting your users and providing higher granularity for your organic cohorts vs paid cohorts.

How it works

We have built a custom integration to automatically send all Branch install data to Localytics without any extra work on your side (besides integrating both SDKs). We just need some configuration information from your Localytics account, and we'll take care of the rest.

How do we differentiate Localytics and Branch installs?

We rely on a Branch link being clicked which leads to an install. This sets an internal boolean that an install came from Branch.



Set up Localytics

  1. On the Localytics dashboard, navigate to the Attribution section, click the ••• (overflow) button, and select Settings. image
  2. Once there, you'll need to add your Store ID (iTunes for iOS, Play Store for Android).
  3. Under the section Ad Tracking Setup, check the box labeled Third-party Attribution. This will enable an Attribution ID for you. Copy it, and have it handy for the next steps. image

What does this mean?

Once you have selected to allow third-party attribution, Localytics will attribute non-Localytics installs to your dashboard. This information is delayed by 10 minutes.

Configure the Branch Dashboard

  1. On the Branch Dashboard (, navigate to the Integrations page.
  2. Locate Localytics and choose Enable.
  3. If you have not yet entered billing information, please do so now.
  4. Enter your Localytics Attribution ID for each platform and hit Save


Please test your integration!

Branch is not responsible for inaccurate API keys.


What Branch sends to Localytics

Branch Analytics Tag Localytics Data Placeholder Tag
Campaign campaign

Branch will also send any arbitrary parameters you attach to a link on to Localytics. All Branch data will appear in the Localytics "Attribution" dashboard, but not the "Events" dashboard.


Debugging strategies

When debugging Localytics, be sure to wait 10 minutes after you simulate an install. Also be sure to collect IDFA or Google Advertising ID.