Issue

Data discrepancies between the Facebook UI and destination.

Environment

Connector: Facebook Ad Insights / Facebook Ads

Resolution

Difference in Aggregation

Verify the aggregation level you are using in your connector config by checking which fields you have configured. When viewing the data in the Facebook UI, you must view it at the same aggregation level to get a correct comparison, or else you may see discrepancies.

Info on aggregation

Depending on the breakdowns, action breakdowns, and fields you selected while configuring the connector, we query at different levels:

• Ad level: If you select the ad_id and/or ad_name fields, and/or product_id breakdown, and/or action_target_id action breakdown
• Adset level: If you select the adset_id and/or adset_name fields
• Campaign level: If you select the campaign_id and/or campaign_name and/or objective fields
• Account level: If you selected none of the fields listed above

NOTE: If you selected fields that correspond to more than one level, we query at the most granular level. For example, if you select both the ad_id and adset_id fields, we query on Ad level.

See our Schema Information docs for more info.

Summing Actions does not give the Sum of all actions

Summing Actions does not actually give you the sum of all actions as the data is hierarchical. This is outlined at the end of the Schema Information of our FB Docs:

Note: The action data is hierarchical: a simple sum of all actions will not equal the field total_actions. See Actions you can measure in Facebook Ads Reporting for more information.

Use a query that doesn't include a SUM to do your data comparison.

Fields not synced

Ensure the fields you are expecting to see synced have been configured in the connector report.

To see fields that can be synced, go to Facebook's documentation on Insights Parameters. If you can not see your required field there, also view the Facebook Breakdowns, as the field may be included as part of this.