We support Adjust, Appsflyer, Branch.io, Kenshoo, Singular and Tenjin.
We recommend that you "post back" your Adjust or Appsflyer data into Facebook. That is the easiest way to make sure things are working properly. Here is how you do it. Any other questions, please contact us.
We can also integrate with Kenshoo, Tenjin, and Branch.io, contact us if you're interested.
Configuring Adjust
1) Log into your Adjust dashboard. Ho to Menu-> Settings and record your user's API Token.
2) Next, return to the Dashboard and click on the App you want to pass event data for. This is the AppToken. Record the name of the App and the token.
3) Finally, email the API Token, App Tokens and the corresponding app names to support@consumeracquisition.
Configuring AppsFlyer
Option 1: Configure agency access
This gives AdRules access only to data generated by campaigns created by AdRules. If the account is a new account, this option is satisfactory.
https://support.appsflyer.com/hc/en-us/articles/208643876-Agency-Permission
- Agency name “Consumer Acquisition”
- Please turn all toggles “on”
Option 2: Send us your API key
For an existing account, this will provide historical data. Log in to Appsflyer and find your API key (see graphic below) and email the API key to support@consumeracquisition.com and we'll get it configured. If you have specific event columns to calculate in for ROAS, please let us know, otherwise, we can “auto-detect” events.
2) Optional – map your event columns to Facebook standard events. Use the standard events even if the naming convention isn't an exact match. If you do, you can leverage App Events Bidding, which is extremely powerful. You can only do this with the standard events.
If you are passing in downstream events data to Appsflyer (and not to Facebook) then we can optimize your campaigns around those events. For example, if you pass in “purchases” along with a revenue amount per purchase, we can build optimized ads that are designed to bring users who would be more likely to convert to a purchase and conversely, eliminate ads with lower ROAS.
Furthermore, if you pass the data into Facebook (via Appsflyer) or directly into Facebook (via SDK), and mapped to their standard events, we can utilize Facebook’s vast data to find users most likely to convert to a payer. Essentially, Facebook would “know” what type of user is most likely to become a payer, and start optimizing towards these particular “lookalikes”. We’ve seen great results using this method.
Renaming default Facebook events in AdRules UI
When you have mobile events mapped to default Facebook events, you can create custom events in AdRules to rename the default Facebook events (only in the AdRules UI).
- In the reporting section, click on the gear to bring up the column selector
- Click on "Expressions" to create a custom expression that will only appear in AdRules
- Column 1 - select the default Facebook event you mapped your mobile measurement partner data into but leave Column #2 blank
- In Display Name you can create a friendly name for your new event so it is easier to remember.
- Hit apply and add the new expression into your reports.
Facebook Tracking and Events
Here is a a bit of information we share to make sure we can see in-app events and use the best audiences to build dynamic lookalike audiences. If you only implement custom events, you track via facebook.com/analytics we are not able to see them in Ad Manager or through the Facebook SDK in our tool. We recommend you instrument the app to feed in-app events into one of the 14 Facebook default events - or see if your mobile measurement partner (MMP) can post back into those default events. You can add calls to one of the predefined events on top of your current custom event calls to your MMP but I believe this modification requires an app update.
What’s Included
A standard integration will import purchase count and revenue cohorts, for the purposes of ad optimization. For example, you might want 3 and 7 day purchase count and revenue, post-install date. Purchase count and revenue are a total of two slots, per each cohorted period. You have 10 available slots into which data may be imported and used in AdRules reporting.
Measuring Engagement Over Time: Whenever possible, map your in-app events to the standard FB events to have out-of-the-box reporting in AdRules and Facebook. The standard event names do not necessarily need to correspond to the actual events in your app. We strongly recommend using the standard events to take full-advantage of out-of-the-box features. By default, Facebook offers 1-Day, 7-Day and 28-Day attribution windows from the day the user clicked on the ad. This enables you to include or exclude engagement data in reporting simply by changing your attribution window in the UI.
Measuring ROAS: You can pass an optional revenue amount to certain events, such as Purchased, Added to Cart and Spent Credits. Out-of-the-box, this facilitates ROAS tracking with 1, 7 and 28 day windows from time of click.
Custom Attribution Windows: To do custom attribution windows for Engagement data or ROAS, such as 3-Day or from "time of first app use", you can programmatically detect, in the app, if the timeframe is adequate before making the FB SDK call. For example, you could detect if <= 3 days had passed since first app use to decide whether to call a Purchase event. You could additionally call an alternate event after 3 days that is reserved only for this purpose.
SDK References
Standard In-App Events
Mobile measurement partner configuration - feed your events into one of the 14 default Facebook events.
