Can't see Conversion data in my Facebook widget

Facebook doesn't return conversions that are set up using the Facebook Pixel under the standard conversion headings like leads, reason why you don't see any data for these conversion fields in the Facebook widgets. 

We've added additional conversion fields to the Facebook widgets that have (FB Pixel) in brackets. You'll have to select these to see the conversion data from Facebook pixels

How does the new attribution change affect Facebook reporting?

Due to Apple enforcing its policy, Facebook ads recently made a change to the attribution settings because of which some data is neither available through the Facebook Ads API nor on the Facebook Ads interface.

Facebook has added a new column called attribution settings which can be set at the ad set or campaign level. Old campaigns that are paused will continue to have the old settings but new or active campaigns will use by default the 7 day-click window.

If ad sets have different attribution settings, those will be used.

If campaigns have different attribution settings, you won't be able to see the aggregate data/summary view for all the campaigns together.

If a campaign has multiple ad sets, and those ad sets have different attribution settings (ex 7 days and 28 days click), then there won't be aggregated data and you will see a dash. To aggregate the data, all ad sets should have the same attribution settings.

The same change happened in the Facebook Ads API so we have updated the Facebook widgets by adding a new option.

  • You can now use a unified attribution setting (recommended). It is the one used to see data on the Facebook Ads interface. The preview might show a hyphen at the account level unless all the campaigns have the same attribution setting.

  • You can use the default attribution setting i.e. 7-day click attribution. It is the one Facebook Ads sends data for, even if campaigns have different attribution settings/or ad sets have different attribution settings. The data may not always match with the data in the Facebook Ads interface because the Facebook interface uses a unified attribution setting. This setting is recommended if you have 7-day attribution for all campaigns.

Is there a workaround in Optmyzr?

To see account-level data, you can select a multi-account widget like KPIs.

If you have multiple attribution settings for campaigns inside your account and you still want to see a summary of Conversions (Results), you might want to use the Multi-account widgets with the "Conv" metric selected.

This workaround would be possible only if ad sets inside campaigns have a unique attribution setting, otherwise, any such campaign will not be included in the aggregate.

This result can also be achieved by reporting on the "All Conv" metric if you want to stick to Facebook widgets.

Note: You can use all conversion metrics inside Facebook widgets to get data at the account level, even if the custom conversions from Facebook will show a hyphen.

For a traffic campaign, every click is tracked as a conversion. How can I count just the purchase as conversions?

To report on a specific conversion type as 'Purchases' in your traffic campaign you can follow these simple steps:

  1. Select the conversion type “Offsite Conversion: FB Pixel Purchase” or “Onsite Conversion: Purchase” based on your requirements in any of the Facebook widgets.

  2. Select the 'Conv' metric from the 'Choose Columns' tab. The 'Conv' metric will automatically report on the Conversion type that you've selected in the widget.

Once you preview the widget, you'll be able to see the Purchase data for your campaigns.

I am using the Multi-Account KPI Widget to view data for my Facebook campaigns but there is a data discrepancy with Optmyzr and my Facebook manager. How can I get a detailed report for this using Optmyzr?

The way in which data is shown in the Multi-Account KPI Widget is different from the other Facebook widgets. For example, the All conversions metric in the Facebook widget shows the same data as the Conversions metric in the multi-account widget. The ‘All conversions metric’ in the multi-account widget will match the Results column in Facebook ads.

This is the same for All conv. rate and Conv. rate., cost/All conv., cost/conv, All conv. value and conv. value and other related metrics.

To view additional data like additional clicks or custom conversions, you can use the campaign performance Facebook widget.

When I duplicate a multi-account template and try to add the Facebook account it shows "Cannot change account being used to another type. Please select new account picker."

When duplicating a multi-account template, the original account type(s) (Google Ads and Microsoft Ads) remain the same. This means that to add a Facebook Ads account to a multi-account report template, you'll need to add a new account selector widget. This is because the previously selected account picker widgets only support Google Ads and Microsoft Ads.

Note: If you wish to change the account in the account selector, you'll need to make sure that the account type is the same. For example, you can change your Google Ads account only with the same platform account.

My leads are not showing on my report. I can see all KPIs running on Facebook, except for leads.

Facebook recently changed its attribution settings in response to the IOS 14 update, and this is affecting how the data is presented both in the Facebook interface and through the API (and, therefore, in Optmyzr). We've added two attribution options to the Report Settings: 'Use unified attribution setting (Recommended)' and 'Use default attribution setting i.e 7-day click Attribution'. If you change the attribution to the 7-day click Attribution, you'll be able to view lead data.

How does this new attribution change affect Facebook reporting?

Facebook has added a new column called attribution settings which can be set at the ad set or campaign level. Old campaigns that are paused will continue to have the old settings but new or active campaigns will use by default the 7 day-click window.

If ad sets have different attribution settings, those will be used.

If campaigns have different attribution settings, you won't be able to see the aggregate data/summary view for all the campaigns together.

If a campaign has multiple ad sets, and those ad sets have different attribution settings (ex 7 days and 28 days click), then there won't be aggregated data and you will see a dash. To aggregate the data, all ad sets should have the same attribution settings.

The same change happened in the Facebook Ads API so we have updated the Facebook widgets by adding a new option.

  • You can now use a unified attribution setting (recommended). It is the one used to see data on the Facebook Ads interface. The preview might show a hyphen at the account level unless all the campaigns have the same attribution setting.

  • You can use the default attribution setting i.e. 7-day click attribution. It is the one Facebook Ads sends data for, even if campaigns have different attribution settings/or ad sets have different attribution settings. The data may not always match with the data in the Facebook Ads interface because the Facebook interface uses a unified attribution setting. This setting is recommended if you have 7-day attribution for all campaigns.

My report is showing data from the Facebook campaign as being 68 Clicks & 61 Unique clicks, but when I check the Facebook platform, it shows 44 clicks with 41 of those being unique. What can be the reason for this discrepancy?

The 44 clicks that you see in the FB interface are link clicks. Link Clicks are the number of clicks on links to selected destinations or experiences, on or off Facebook-owned properties, whereas the clicks that you see on Optmyzr reports are Clicks (All) which includes the following:

  • Link clicks

  • Post likes, comments, or shares

  • Clicks to a Facebook Page or Instagram profile

  • Clicks to expand a photo or video to full screen

Since Clicks (All) includes link clicks, the number is greater than what you see in the Facebook interface.

Did this answer your question?