App Events API

• Automatically Logged Events - The Facebook SDK automatically logs app installs, app sessions, and in-app purchases.
• Standard Events - Popular events that Facebook has created for you.
• Custom Events - Events you create that are specific to your app.

1. name - A required string that describes the event. The name appears in the Event log when the app event is sent to Analytics.
2. valueToSum - An optional value that Analytics adds to other Value To Sum values from app events with the same name.
3. parameters - Optional values included with your app event.

• Your advertiser ID, the advertising ID from an Android device or the Advertising Identifier (IDFA) from an Apple device
• An app access token for Facebook to authenticate. Do not store your app access token on the client.

curl -i -X POST "https://graph.facebook.com/{app-id}/activities
   ?event=MOBILE_APP_INSTALL
   &application_tracking_enabled=0
   &advertiser_tracking_enabled=0
   &advertiser_id={advertiser-tracking-id}
   &{app-access-token}"

{
  "success": true
}

• You should report only one install per user. Deduplicate IDs on the ID and user levels if possible.

print("isAdvertiserTrackingEnabled: \(Settings.shared.isAdvertiserTrackingEnabled)")

curl -i -X POST "https://graph.facebook.com/{app-id}/activities
   ?event=CUSTOM_APP_EVENTS"
   &advertiser_id={advertiser-tracking-id}
   &advertiser_tracking_enabled=1
   &application_tracking_enabled=1
   &custom_events=[
      {"_eventName":"fb_mobile_purchase",
       "event_id":"123456",
       "fb_content":"[
            {"id": "1234", "quantity": 2,},
            {"id": "5678", "quantity": 1,}
        ]",
       "fb_content_type":"product",
       "_valueToSum":21.97,
       "fb_currency":"GBP",
      }
    ]
   &{app-access-token}"

{
  "success": true
}

• View-Through Attribution Claims - Setting consider_views=TRUE returns attribution data for installs that occurred within 1 day of an ad impression, provided the Accounts Center account did not click on an ad within 30 days.The response returned will be is_view_through=TRUE and view_time will replace click_time. All other attributions are the same as with ad click attribution data.
• Cross-Campaign Claims - Advertisers are able to track the performance of all ads that have led to an app event. Facebook sends claims for events from ad campaigns as long as the campaign objective is not set to mobile app install or mobile app engagement. This data is surfaced only if the advertiser has added the app to “Mobile App Events Tracking” field in their ad.
• User Case — If your client wants to track the installs generated by a Page post ad or website ad clicks that sends users to a mobile site, they can do this in ads manager and Facebook will claim the relevant app installs.
• Cross-Device Claims - Advertisers with apps on multiple platform can see data for app installs being driven from ads across these multiple platforms.
• Use Case — A user clicks an iPhone ad for an app and then installs the same app on their iPad. We can then attribute the iPad app installation to the iPhone ad regardless of the ad targeting.

curl -i -X POST "https://graph.facebook.com/{app-id}/activities
   ?event=CUSTOM_APP_EVENTS
   &advertiser_id={advertiser-tracking-id}
   &advertiser_tracking_enabled=1
   &application_tracking_enabled=1
   &custom_events=[
      {"_eventName":"fb_mobile_purchase",
      "event_id":"123456",
       "fb_content":"[
            {"id": "1234", "quantity": 2,},
            {"id": "5678", "quantity": 1,}
        ]",
       "fb_content_type":"product",
       "_valueToSum":21.97,
       "fb_currency":"GBP",
      }
    ]
   &ud[em]={sha256-hashed-email}
   &{app-access-token}"

{
  "success": true
}

• version must be a2 for Android
• version must be i2 for iOS

• ApplicationActivities Parameters
• Android Developer Documentation - Display Metrics⁠
• Android Developer Documentation - External Storage⁠
• Apple Developer Documentation - Display Metrics⁠
• Apple Developer Documentation - External Storage⁠
• Apple Developer Documentation - Screen Size⁠

public static final Uri ATTRIBUTION_ID_CONTENT_URI = Uri.parse("content://com.facebook.katana.provider.AttributionIdProvider");

public static final String ATTRIBUTION_ID_COLUMN_NAME = "aid";

public static String getAttributionId(ContentResolver contentResolver) {
        String [] projection = {ATTRIBUTION_ID_COLUMN_NAME};
        Cursor c = contentResolver.query(ATTRIBUTION_ID_CONTENT_URI, projection, null, null, null);
        if (c == null || !c.moveToFirst()) {
            return null;
        }
        String attributionId = c.getString(c.getColumnIndex(ATTRIBUTION_ID_COLUMN_NAME));
        c.close();
        return attributionId;
    }

ASIdentifierManager *manager = [ASIdentifierManager sharedManager];
NSString *advertiserID = [[manager advertisingIdentifier] UUIDString];

if (advertiserID) {
  // do stuff
}

curl ...
  -H "X-Forwarded-For: fd45:f238:3b40:23b1:ffff:ffff:ffff:abcd" \
  https://graph.facebook.com/<APP_ID>/activities/

curl ...
  -H "X-Forwarded-For: 192.168.0.99" \
  https://graph.facebook.com/<APP_ID>/activities

1. Go to Events Manager⁠.
2. Click the Data sources icon on the left side of the page.
3. Select the name and ID of your data.
4. Click Test events, and select channel as App.
5. Send a AE-API request with graph api tool.
6. Your interactions will soon appear in the Test events tab.

• Is the FB SDK integrated properly?
• Is the client using the wrong app ID?

• Are the attribution windows the same? Facebook generally has a larger attribution window than most mobile measurement partners.
• Is the MMP SDK integrated properly?
• Is the client using the wrong app ID?
• Is the discrepancy iOS7 only? Is the MMP receiving Apple’s Advertising Identifier (IDFA) from the device and passing it properly to FB?

• App Events
• App Events Best Practices
• Handling Errors
• GDPR Compliance
• Facebook Ads Manager⁠
• Facebook App Dashboard