People

Learn about the people using your product with aggregated demographics and audience insights including age, gender, location, education and interests. You can also use Custom Audiences to focus on specific segments of your audience that you want to learn more about.

General

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 INFO

This 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.
CUSTOM PARAMETERS

This category contains parameters that are based on custom parameters defined by the developer (example: content ID or purchase value).

USER PROPERTIES

This 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.

Was this information helpful?

To create a new filter in Facebook Analytics, select the analytics entity, or entities, and build your filter. Next, add conditions and refine. Finally, save your filter if you'd like to reuse it later.

You don't need to save your filters to share them or create Custom Audiences.

To create and save a filter in Facebook Analytics:

  1. Select the analytics entity or group you'd like to filter.
  2. Next to , click + Add Filter and select Create new filter from the top section of Facebook Analytics. The filter will read Filter data by people who. If you'd rather filter by events, you can click the filter and select Filter data to events that.
  3. Add conditions. Depending on the analytics entity you've selected and if you're filtering by events or people, you will see options related to:
    • Events: Actions people take in an analytics entity or group that you define and log (example: app launches and purchases). You can filter by including or excluding events.
    • Demographics: Characteristics like age, gender, country or language.
    • Device Info: Information about devices people use (example: device model, browser or app version).
    • User Properties: Custom user details. For example, an airline might create a user property of “frequent flyer status.” Learn how to create user properties.
    • App Install Source: The way a person found and installed your app. Learn more about app install sources.
    • Web Parameters: Information related to web events, such as referrer domain. For example, a company might use this to see people who are coming to their website from a specific web domain (example: www.facebook.com).

    Keep in mind, depending on the parameters you'd like to use, you may be able to use different operators (example: is, is not, contains, does not contain and so on) to customize your filter.

  4. Refine the condition you selected and add more filters as needed.
  5. Check the percentage of your audience included in this view and update your filter as needed. Here's an example:

    If you see an error message in your charts, you may need to choose a less granular filter.

  6. Click and select Save Filter, then name your filter and click Save to confirm. You can also click away from the filter to preview without saving.

    Keep in mind that not all roles can save filters. Even if you can't save the filter you created, you can still share it.

Now that you've created a filter, you can explore other sections with your new filtered view of Facebook Analytics. You can remove the filter from your view by clicking X on the filter.

Note: If you see an error message in a chart, you can troubleshoot it.

Was this information helpful?

When you apply a saved filter, the charts will only show metrics people or events that meet the specified conditions.

To apply a saved filter in Facebook Analytics on the web:

  1. Click the relevant section from the menu on the left, then, if needed, select the relevant subsection.
  2. Near the top of your screen, click Add Filter.
  3. Select a saved filter from the list.

Now that you've applied a filter, you can explore other sections with your new filtered view of Facebook Analytics. You can remove the filter from your view by clicking X on the filter near the pie chart.

Note: If you see an error message in a chart, you can troubleshoot it.

Was this information helpful?
You can create Custom Audiences from filters, saved or unsaved, in Facebook Analytics. You can create Custom Audiences for apps, pixels, and event source groups that only contain apps and pixels. If you have access to Pages and Instagram event sources in Facebook Analytics, you can also create Custom Audiences from these event sources and associated event source groups. You may not be able to create a Custom Audience from all filter options.

You can create a Custom Audience from a saved or unsaved filter in Facebook Analytics and later select your Custom Audience when you create your ad campaign.

To create a Custom Audience in Facebook Analytics:

  1. Either create the filter you'd like to use, or select an existing, saved filter. You may save any new filters you create if you'd like.
  2. Select , and select Create Custom Audience.
  3. Enter a name for your Custom Audience.
  4. Specify the following options:
    • Ad Account: The Facebook Ads Manager account associated with your Custom Audience.
    • Filter: Select Use Current Filter or a saved filter that you'll use to create your Custom Audience.
    • In the: Select the time period for people to qualify for your Custom Audience.
  5. Select Create Custom Audience. If you are unable to create a Custom Audience with your current filter selection, you may need to update your filter before you create your Custom Audience. You may not be able to create a Custom Audience from all filter options.
  6. Select View Audiences to view, edit or delete this audience in Audience Manager.

Note: New Custom Audiences may take up to 1 hour to become available. Event-based Custom Audiences are a type of Engagement Custom Audience, which means this audience's size may change as people's engagement changes.

Learn more:

Was this information helpful?

You can create a Lookalike Audience from a Custom Audience to reach people who are similar to your existing customers. To create a Lookalike Audience in Ads Manager from a Facebook Analytics Custom Audience, you'll have to first create a Custom Audience from a filter in Facebook Analytics.

Learn how to create a Lookalike Audience in Ads Manager.

Note: Newly created audiences may take up to 1 hour to become available.

Was this information helpful?

If you're seeing error messages in your Facebook Analytics charts, it may be related to any of the following reasons:

Error MessagePossible Reasons

All Other

The filter that you're viewing, or the audience that you're viewing for a given time period, may not be large enough.

Try adjusting the conditions of your filter to increase the number of people represented in your filtered view. You can also try increasing the time interval you're viewing.

Unknown

You may see Unknown when:

  • The information may not have been verified, like when people are not logged into Facebook.
  • There are not enough people to anonymize and aggregate their information.
  • People chose not to disclose some information, like gender.
  • People select a gender option that is not yet supported by Facebook Analytics.
Try increasing the time interval you're viewing or making your filter less granular to decrease the number of Unknown results.

No Data Is Available

Your events may not be logging correctly. Learn more about checking if your events are logging correctly.

Other Values

You may see Other Values to let you know we've grouped together results that we don't recognize, or results with insufficient numbers to display.

For example, you may see this when you break down a chart by browser. People may have triggered events in browsers we don't yet support, or people may not have triggered enough events in a given browser or group of browsers to show results in your charts.

Application request limit reached

If you see the "Application request limit reached" error message, it may be due to a momentarily high request volume.

Recommendation: Wait (ideally at least 24 hours) and try again later when access is unblocked.

Was this information helpful?

Technology

In Facebook Analytics, Client Type, Device OS and Channel are all different parameters you can use to break down your charts, when available:

  • Client Type: The software used to access your event source (example: native app, Games on Facebook).
  • Device OS: The operating system used to access your event source.

    Keep in mind that individuals who 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 mobile phones, the Device OS will be logged as Multiple Values.

  • Channel: 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 for Facebook Analytics.

The table below identifies the Client Type, Device OS and Channel for various example scenarios:

ScenarioClient TypeDevice OSChannel

A person uses an iPhone, opens a music app and plays music. The play_music event is logged by the Facebook SDK.

Native App iOS iOS

A person uses an Android mobile phone, opens a music app and plays music. The play_music event is logged by the Facebook SDK.

Native App Android Android

A person uses an Android mobile phone, opens Facebook for Android, clicks a music URL in a post and plays music through the browser in the app. The play_music event is logged by the Facebook SDK for JavaScript.

WebView Android Web

A mobile measurement partner (MMP) sends events to Facebook Analytics, but doesn't clarify whether it's for an iPhone or Android mobile phone.

Native App Other Values Other Mobile OS

A person uses a Windows 10 computer, opens a browser, visits a music website and plays music. The pageview event is logged by the Facebook SDK for JavaScript or the Facebook pixel.

Browser Windows Web

A person uses a Mac computer, opens a browser, visits a music website and plays music. The pageview event is logged by the Facebook SDK for JavaScript or the Facebook pixel.

Browser Mac OS Web

A person uses a Mac computer, opens a browser, visits Facebook and plays music via a music app in Facebook. The play_music event is logged by the Games on Facebook SDK.

Games on Facebook Mac OS Games on Facebook
Was this information helpful?