MoEngage Docs

Branch Integration

Use Install Attribution data from Branch in MoEngage

Branch, one of MoEngage's Technology Partners allows you to track the install acquisition data like the Publisher Name and Campaign Name of Install in MoEngage which you can then use to enhance your marketing automation campaigns on MoEngage.

To integrate Branch with MoEngage, you need to follow the below steps:

STEP 1: Configure Settings on MoEngage Dashboard

Go to MoEngage Dashboard: 'Settings' -> 'Analytics'.

Under 'Acquisition Settings', turn on 'Acquisition Tracking', and select Branch from the dropdown.
This by default will generate an 'App Key'.

Hit Save to save all these changes.

MoEngage dashboard 'App Settings'

STEP 2: Configure Settings on Branch Dashboard

To configure the settings on Branch Dashboard, please follow the steps mentioned in the integration document for Branch.

How to use the Acquisition Data in MoEngage

Once MoEngage starts receiving data from Branch, you can leverage this data in the following ways:

  1. We track two User Attributes - "Campaign Name" and "Publisher Name". These attributes can be used in your campaigns, segmentation and analytics.
  1. Acquisition Analytics Dashboard: Once the integration is enabled, you can also see your acquisition data analysis on the acquisition dashboard here.

Note : 3rd party Acquisition Data from partners is calculated every 2 hrs in MoEngage and aggregated data on Acquisition dashboard is refreshed every 6hrs.

Frequently Asked Questions -

Q1. Can I see the install data from Facebook in MoEngage?
A. As per Facebook data sharing policies, the install data from Facebook can only be seen in Branch and not sent to any other platforms. These would be seen as Organic Installs in MoEngage. You could alternatively use our APIs to send Facebook data to MoEngage separately.

Updated 8 months ago

Branch Integration


Use Install Attribution data from Branch in MoEngage

Suggested Edits are limited on API Reference Pages

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