---
schema_version: "1"
id: c9dce03e7f3c50d4e594934e25c963d33c486c6bd23e161344083ea08eeb397b
title: Mapping Reach Data for Facebook Ads Custom API in Marketing Cloud Intelligence
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/dato_data_streams_api_connect_fbcustom_mapping_reach_data.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.dato_data_streams_api_connect_fbcustom_mapping_reach_data.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9c32a0389646b5182b39c35f0fd27afdca0da51d71b30214edefc0c85103cb02
description: To report reach data correctly, you must map the data correctly. Consider these best practices for optimal results.
products:
  - Marketing
  - Marketing Cloud Intelligence
release: "264"
---
# Mapping Reach Data for Facebook Ads Custom API in Marketing Cloud Intelligence

To report reach data correctly, you must map the data correctly. Consider these best practices for optimal results.

- Set up an individual data stream for each granularity of reach that you want to report on.
- Don’t include non-reach measurements because they duplicate the data.
- Don’t map frequency because it appears incorrectly at an aggregated level. Frequency data is at the user level and can’t be pulled at an aggregated level. To calculate frequency, create a calculated measurement outside of the mapping for any granularity of reach that you set up. For example, Impressions/Reach.
- Always select lifetime as the aggregation function.
- Map reach to a delivery custom metric that you aren’t using to easily know which granularity of reach you’re reporting.