App setup: How to integrate external Attribution services


Leanplum integrates with many 3rd party attribution providers. The providers send Leanplum a postback that contains all of the publisher information which in turn allows you to view the marketing channels in Leanplum as well as target by them for a/b tests or marketing campaigns.

Before you turn the integration on with your specific partner, you first need to confirm that your Leanplum integration is using the same device ID as the 3rd party you're hoping to integrate with. This is important as Leanplum matches the user install with the 3rd party postback using the device ID, so if they do not match Leanplum cannot report the data.

Once the device ID is confirmed, you can contact your 3rd party provider or log into their portal, and select Leanplum as the partner to send the postback too. You should then provide the App ID and Client Key specific to your Leanplum dashboard. These keys can be found by going to the following: Select the app list at the top of the dashboard -> Click on Manage Apps at the bottom of the list -> Click on Keys & Setting next to the app name in question.

Device ID


IDFV: This is an app level identifier for a particular vendor. As long as you have apps installed from the same vendor it will stay the same (IE, Facebook and Messenger)

IDFA: This is unique for every device, but can be reset.


GAID: Will always be in this format and have a combination of numbers and lowercase letters, 18ef2444-46bc-4ac8-b95b-c657da47ea81. The attribution provider can change their postback setup to send the Android ID instead of the GAID. This is the easiest fix but we are not sure whether they capture the Android ID or is allowed to send it via postback. The customer needs to check with the attribution provider AM and see if they can pass Android ID

Android ID: Will typically also be numbers and lowercase letters, but is usually in this format, 3ac0274c59b96b6f. the customer will then need to update the Leanplum SDK implementation to capture the GAID as device ID instead of the Android ID. This option will require some minor dev work on the clients end (the change required should only take 1 line of code).

Was this article helpful?
Have more questions? Submit a request