Facebook Platform
See your metrics for Facebook Platform integrations for apps, like Account Kit and Login.
General
In the People section, you can only look at information from the last 28 days.
When you filter by a date range, you'll only see information from the period of time that you've specified, up to 2 years in the past.
To filter by a date range in Facebook Analytics on the web:
- Go to the section of Facebook Analytics with information you'd like to filter (example: Active Users.
For Funnels, Cohorts and Breakdowns you need to view a specific funnel, cohort or breakdown.
- In the top left, select the first dropdown menu. This menu will display the date range you're currently viewing (example: Last 28 days).
- Select an available pre-defined or custom date range, up to 2 years.
- Select Update.
Now the analytics you view will be filtered by the date range you selected.
You can change the information displayed in many charts on Facebook Analytics by selecting a new metric (Metric) or time interval (Time Interval) from the top right of each chart. You can also break down the information you see in these charts by selecting a new parameter (Show By).
Keep in mind, if you see an error message in a chart, you can troubleshoot it.
Metric
To change the metric displayed in a chart, click the dropdown menu to the right of Metric, then select the metric you'd like to see. Keep in mind that these options will be different for each chart.
Time Interval
To change the time interval displayed in a chart, click the dropdown menu to the right of Time Interval, then select the time interval you'd like to see. Keep in mind that changing a chart's time interval will only apply to information shown in that chart.
Show By
To break down your chart by a new parameter, or dimension, click the dropdown menu to the right of Show By, then select an option from the Event Info, Custom Parameters or User Properties categories:
EVENT INFOThis category contains standard parameters built into Facebook Analytics.
Keep in mind, if you see Unknown for any of these parameters, we may not have enough data to anonymize and aggregate the information. Try increasing your Time Interval.
This category includes:
- Age: Shows the age of people that accessed your product.
- App Version: Shows the app version that people used to access your product (example: version 2.3 or 4.4).
- Browser: Shows the web browser that people used to access your product (example: Chrome, Safari, Firefox).
- Browser Version: Shows the web browser version that people used to access your product.
- Channel: Shows the different ways people can interact with your product. More specifically, this is the environment used to log events. Learn more about setting up channels.
- City: Shows the city location of people that accessed your product.
- Client Type: Shows the software used to access your product (example: native app, Games on Facebook). Learn the difference between Client Type, Device OS and Channel.
- Country: Shows the country location of people that accessed your product.
Device OS: Shows the operating system that people used to access your product. Learn the difference between Client Type, Device OS and Channel.
Keep in mind that single users that complete an event on different operating systems will appear as Multiple Values. For example, if a person launches your app on both Android and iOS, it will appear in Facebook Analytics as Multiple Values.
- Device Model: Shows the device model people used to access your product.
- Device Type: Shows the device type that people used to access your product (example: phone, tablet or others).
- Event Logging SDK: Shows the Facebook SDK version used to log an event (example: FBAndroidSDK.4.10.0 or FBiOSSDK.4.10.0).
- Facebook Login: Shows people that used Facebook Login to access your product. Learn more about Facebook Login in Facebook for Developers.
- Gender: Shows the gender of people who accessed your product if available.
- Install Attribution: Shows the action that people took to find and install your mobile app (example: click or view app install ad). Learn how installs are measured.
App Install Source: Shows where people found and installed your mobile app (example: Facebook Ad, Facebook Organic, Instagram Ad, Audience Network). Keep in mind that when you filter by app install source, the results only show app install campaigns and not engagement. Learn more about app install sources.
You can use the following filters to view app install sources that deal with ads (example: Facebook Ad) on a more granular-level:
- App Install Source - Campaign: Shows the campaign that people found and install your app.
- App Install Source - Ad Set: Shows the set of ads that people found and install your app.
- App Install Source - Ad: Shows the ad that people found and install your app.
- Language: Shows the language spoken by the people that accessed your product.
- Mobile Carrier: Shows the mobile carriers of the devices used to access your product (example: T-Mobile or AT&T).
- Processor Core Count: Shows the processor core count of the devices used to access your product.
- Region: Shows the region location of devices that accessed your product.
- Remaining Space in GB: Shows the remaining space on the devices used to access your product.
- Screen Size of Device: Shows the screen size of the devices used to access your product.
- Time Zone of Device: Shows the time zone of the devices used to access your product.
- Session Traffic Source: Shows visits to your website from high-level categories. Learn more about the difference between Session Traffic Source, Session Traffic Source by Search Engine and Session Traffic Source by Social Network.
- Session Traffic Source by Search Engine: Visits from large search engines (example: Ask.com, Bing, DuckDuckGo, Google, Yahoo). Learn more about the difference between Session Traffic Source, Session Traffic Source by Search Engine and Session Traffic Source by Social Network.
- Session Traffic Source by Social Network: Visits from large social networks (example: Facebook, Twitter, LinkedIn, Google Plus). Learn more about the difference between Session Traffic Source, Session Traffic Source by Search Engine and Session Traffic Source by Social Network.
This category contains parameters that are based on custom parameters defined by the developer (example: content ID or purchase value).
USER PROPERTIESThis category contains parameters that are based on custom user data defined by the developer. For example, an airline might create a user property of “frequent flyer status.” Keep in mind that the user properties category is also used as a condition when creating filters.
Learn how to create user properties.
Note: Facebook Analytics only displays the 10 largest values for each parameter.
Account Kit
Account Kit helps your audience quickly register and log into your app using their email address or phone number as a credential. If this option is available to you, you can measure this functionality in Facebook Analytics in Facebook Platform > Account Kit.
Use Account Kit to measure your Account Kit activity and see trends for Account Kit logins, confirmations and conversions.
If you log app events through the Facebook SDK for your Android/iOS app and you've integrated the Account Kit SDK into your app, you'll see information in Account Kit like login activity and dialog, notifications and demographics.
Keep in mind that you may see Unknown when Facebook Analytics does not have enough data to anonymize and aggregate information or when people choose not to disclose their gender or select a gender option that is not yet supported by Facebook Analytics.
Here's an Account Kit example:
You log app events for your app and you've integrated the Account Kit SDK into it. You can use the information in Account Kit to see if people are able to successfully log into your app when using Account Kit (example: Account Kit Login Dialog chart).
To determine where to focus troubleshooting for potential login problems, you can look at the Conversion metric and break it down by Device OS, Login Type, Country and SDK.
Learn more
- Account Kit login flow events and the difference between login starts and login attempts
- Troubleshoot error messages in charts
Login
Facebook Login helps your audience quickly register and log into your app using their Facebook information as a credential. If this feature is available to you, you can measure this functionality in Facebook Analytics in Facebook Platform > Login.
You can use Facebook Login to measure your Facebook Login activity and see trends for logins using Facebook Login, as well as permissions views and acceptances. If you've implemented Facebook Login, you should be able to see the following charts:
- Facebook Login Activity: Shows login activity, which you can break down by New Logins, Permission Removals or Active Login Users.
- Login Dialog: Shows the Facebook Login flow, which you can break down by Accept Rate, Impressions or Accepts.
- New Logins from App Center (Games): Shows new logins to your app using Facebook Login from the Facebook App Center, which you can break down by Accept Rate, Impressions or Accepts.
- Demographics of New Facebook Logins: Shows demographic information of new users logging in with Facebook Login, which you can break down by Gender & Age, Country or Language.
Here's a Login example.
You check Login in Facebook Analytics after running an app install campaign. You break down the Demographics of New Facebook Logins chart by Country and see an influx of new users from Spanish-speaking countries. You may then decide to look into translating your app into Spanish to better serve this new audience.
Note: If you see an error message in a chart, you can troubleshoot it.
Depending on the channel you're using, app installs and new logins may represent different actions people take.
iOS and Android
On mobile channels, like iOS and Android, app installs and new logins represent different actions:
- App installs happen the first time a person launches an app.
- New logins happen the first time a person logs into an app or website using Facebook Login or Account Kit.
Games on Facebook
On Games on Facebook, app installs and new logins are the same.
You may notice a difference in Active Users and Active Login Users because they are determined differently in Facebook Analytics.
Active Users
A user must complete one of the following events to be considered an Active User during a given time period. These events may include:
- Viewing your website and the
logPageViewmethod is called. Learn more about event logging for websites. - Launching your app on Games on Facebook.
- Sending messages to a Messenger bot.
Active Login Users
We log Active Login Users whenever someone accesses your app using Facebook Login. You can view Active Login Users in Facebook Platform > Login.
