Q: Can I fetch data from custom conversions and custom events that are configured in my Facebook Ads account?

A: Yes. ReportGarden treats any custom conversion pixel or custom event set in Facebook Ads just like any other metric. They will show up in the metrics list.

In case you don't see a custom event or custom conversion in the metric list, or if you have added a new custom event or custom conversion, go to the sub account edit page. There, you will see an option at the top right to Fetch Custom Conversions. Click on that button, and wait for a few seconds to import the conversion metrics.

Go back to the reports page and refresh your report. You will see that the conversion metrics appear like any other metrics while creating/editing a new widget

Q: How does attribution window work with Facebook Ads?

A: By default, all widgets have the default attribution window. It means that the data is aggregated at the ad group level, and it respects the attribution window that is set at each ad group.

So, for example, if one ad group has an attribution window of 1 day view and 7 day click and another ad group has an attribution window of 7 day view and 7 day view, it takes the respective attribution windows into account and aggregates the data for inline metrics.

Q: Can I choose a custom attribution window for Facebook Ads data?

A: Yes. If you go to the advanced tab, you can choose the option to select the attribution window accordingly.
Please note that since the iOS14 changes, a lot of attribution metrics are skewed and often come up as 0s. This is inline with the data that is being shown in Facebook Ads business manager.

Q: Why isn't the data in ad sets not matching up with the data in campaigns?

A: Since the iOS14 changes from facebook, there have been a few instances where the attributed metrics like add to cart, purchases, conversions, are showing different values in Facebook Business Manager as well. This is because of the changes related to iOS14, where the attribution is no longer deterministic. This happens especially in cases where there are different campaigns, with different ad groups having different attribution windows in the same campaign.

Attribution and attribution related metrics are best obtained through the ad set level, which is what ReportGarden defaults to wherever possible.

Q: Why isn't the data for Estimated Ad Recalls not populating/matching with the data in Facebook Ads?

A: In many cases, there would be a mismatch between the estimated ad recall rate and estimated ad recallers. API doesn't return the correct values all the time. According to the Facebook API, these metrics are still in "development" and are "estimates". ReportGarden has tried to derive those metrics. The calculation goes as "Estimated Ad Recallers" x 100 / Reach. But as everyone is aware, similar to reach, estimated ad recallers cannot be aggregated, which is why the discrepancy in the numbers is not fixable.

Also, please note that at the moment, this metric is only available for assets in the Brand awareness, Post engagement and Video views Objectives. This metric is estimated and in development.

Q: Why isn't the data for metrics like Purchases, Conversions, Leads, etc not showing up for dimensions like Age, Gender, Publisher Platform, etc?

A: Since the iOS14 changes from facebook, the API does not support collecting data for inline metrics (like purchases, leads, add to carts, etc) for the following dimensions/segments

  • Age

  • Gender

  • Publisher platform

  • Country

  • Region

All of them would be falling into the category "unknown".


´╗┐This behaviour is from facebook's limitation, and is currently not supported in business manager as well.

Q. Why is reach and frequency in ReportGarden different from Facebook Ads?

A: Reach and Frequency are non-aggregate metrics. Meaning, the total reach by campaigns/adsets would not match with the overall reach. This is because, by definition, Reach is the number of unique people that have seen this ad.

It can so happen that the ads in different ad sets (Adset 1 and Adset 2) can be seen by the same person, so the reach for Adset 1 and Adset 2 would be 1 each, but the reach for the campaign would also be 1 (since it is the same person that has viewed the ad).

When we are calculating the total row for such metrics, the only option for us is to add the reach metric in each row, since it would be impossible to determine otherwise. We try and get the summary from Facebook Ads for combinations and when filters are present, but there are limitations to these.

Also, when dealing with reach, the platforms themselves work on a sample and extrapolate the data. This is especially true for demographic data like age and gender. There would be minor discrepancies with respect to reach and frequency metrics.

Did this answer your question?