This guide applies to cases in Data Studio were the scorecard or summary row was working with a filter but now suddenly returns "Null", "No data" or NA.
The good news is Google finally fixed the issue that caused this problem when using filters (Discrepancies in Data Studio When Using a Filter) - Data Studio can now pass the filter details as part of the request. This means we can finally get the true reach values from Facebook.
The bad news is that filters that used to work with Reach (and other unique count metrics) may break and show as "Null", "No data" or NA values in the reporting. This is happening because the filter creates a situation where it it trying to sum together unique metric counts across non-unique objects (like multiple campaign names, account names, placements, etc.)
Basically what is happening behind the scenes is this error:
Can't Be Calculated, Would Require Summing Deduplicated Values
It's unfortunate this fix by Google that addresses so many problems with Data Studio discrepancies now makes some configurations invalid, so we apologize for that and hope the recommendations below help you fix the reporting.
In some case, adjusting the filter can fix the error. A common cause is using a "Placement" filter for finding instagram-based posts. If you switch to this filter instead, it does the same thing and avoids the error:
If you were filtering on Campaign name and it finds multiple items with that string:
- If you only mean to get one campaign, then change the filter to use the "Campaign ID" field instead as it's unique.
- If you mean to get more than one campaign with the filter, this sadly cannot be done anymore and the value you got before was very likely wrong anyway. You need to redesign the report to work around this as the deduplicated sums error (which Data Studio interprets as "No Data" or null) is the intended response. This may mean removing the filter, or placing the data in a table rather than a scorecard as it can be split properly.