Overview
AppsFlyer is a leading SaaS platform specializing in mobile marketing analytics and attribution. It empowers app marketers to measure and optimize their user acquisition campaigns by tracking the entire customer journey, from the initial ad interaction to in-app activities. The platform provides a comprehensive suite of tools, including multi-touch attribution, which identifies all the marketing touchpoints that led a user to install an app. Furthermore, AppsFlyer offers robust fraud protection to ensure marketing budgets are spent on real users and provides deep linking capabilities for a seamless user experience. By offering detailed analytics and performance reports, AppsFlyer enables businesses to make data-driven decisions to enhance their marketing strategies and maximize their return on investment. This integration with Zeotap enables you to send event data to Appsflyer.Pre requisites
- You must have an A ctive AppsFlyer account.
- Mobile App(s) Configured in AppsFlyer: a. Your mobile application(s) (Android and/or iOS) must be already added and configured in your AppsFlyer account. This is the foundational step for AppsFlyer to recognize your app. b. Crucially, the AppsFlyer SDK must be properly integrated into your mobile app(s). This SDK is responsible for generating and collecting the unique appsflyer_id for each user installation, which is a mandatory identifier for our integration to send mobile app events to AppsFlyer.
- For Mobile S2S API: You must have the specific mobile app (Android and/or iOS) already added and configured in your AppsFlyer account. This is where you get the app_id and Dev Key.
- For Web S2S API: If you plan to send web events, you must have your web property (website) added as a “web app” and typically associated with a “brand bundle” in AppsFlyer. This is where you get the Web Dev Key.
- Obtained AppsFlyer Credentials: a. App ID: The unique identifier for your mobile app (e.g., com.example.app for Android, id123456789 for iOS). b. Dev Key (for Mobile S2S): The primary authentication key for your AppsFlyer account, found in App Settings or Security Center > API Tokens. c. Web Dev Key (for Web S2S): The specific authentication key for your web property, found under My Apps > View brand bundles
Creating a Destination
Click on Appsflyer . A screen appears displaying details about the particular destination towards the left. On the right-hand side of the screen find a list of fields that are required for the integration to be established. Enter the required details as mentioned in the following steps:a. Enter a name for the Destination.b. Enter the Dev Key.c. Enter the Destination Instance.d. Enter the App ID.e. Enter the Web Dev Key.f. Enter the Bundle ID.
In the new screen that appears, choose the appropriate Action and mapping as explained below.a. Choose the desired action under Choose your Action and then choose the corresponding identifiers under Map the Fields. By default, the Output Identifiers that are accepted by the platform, such as customer user ID (CUID), Appsflyer ID are displayed. However, you can edit, add, or remove an identifier from the list.b. Mandatory Fieldsi. Event Nameii. Event Valueiii. Customer User IDiv. Appsflyer ID.
c. Click Save Mapping.
Activate the Destination on Journeys
After creating a destination, next, you need to link it in the Send to Destination node within the workflow, as explained below.
Under the Destination Details tab, the Access Token and Ad Account ID fields are automatically populated based on the value that you have entered while creating the destination.
