---
schema_version: "1"
id: bd0add9da6024e6d39db0ec9b5770f85ff54e42eeb97482e0c803f4582d183cc
title: Mapping Reach Data for Facebook Ads Custom API in Marketing Cloud Intelligence Data Pipelines
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mcidp_data_streams_api_connect_fbcustom_mapping_reach_data.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mcidp_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: 6792f7f711f8c1ed10888bd6d4bcacc68bbf23fd6f5fa3f0bcefc09f1266d4ad
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 Data Pipelines

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.