AppsFlyer Facebook Configuration

The following guide will walk you through the steps for enabling the integration between AppsFlyer and Bidalgo.

Step 1 - Getting Started with AppsFlyer

  1. Log in to the AppsFlyer dashboard.
  2. Make sure that AppsFlyer is already integrated with FB.
 

Step 2 - Provide Bidalgo Permission to View FB Data

This step will provide Bidalgo with access to Facebook/Bidalgo attributed data on the AF dashboard. While this step is not mandatory, it will provide Bidalgo with the ability to compare data between AF and Bidalgo.

Steps:

  1. Under Configuration -> Integrated Partners search for Bidalgo.
  2. Under the Permission tab, provide Bidalgo with the permissions below.

AF_agency_permission.gif

 

Step 3 -  Integrated Partners

Locate Bidalgo - Facebook Marketing Partner under integrated partners.

bidalgo_facebook3.gif

  1. Enter the Mob Channel parameter on the 2 edit boxes. We recommend using the following format: <company Name>_<App Name>_<Platform>_FB. For example:
    • IOS - Piedpiper_thebox_ios_FB
    • Android - Piedpiper_thebox_android_FB
  2. Enable In-App Events Postback and select to add manually the relevant events. Please note that the following events are typically added:
    1. af_purchase - don't forget to select send Value
    2. Login
    3. af_level _achieved 
    4. af_app_opened

 AF_facebook_configuration.gif

 

Note!

1. "Map all SDK events"

If you'd like to forward S2S events to Bidalgo, do not select the "Map all SDK event option"
in order to map S2S. Uncheck the "Map all SDK events" checkbox and map all the required events one by one.

2.Unable to Find Purchase Event

If you are unable to locate the purchase event, it means that you have not configured the Appsflyer SDK to send these events. In order to configure it, follow the instructions at: https://support.appsflyer.com/hc/en-us/categories/201114756-SDK-Integrations.

 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.