Zero Impressions *are* being filtered by default

[Jason Brinkle]

I was comparing results between requests to the AdWords and new Ads APIs and was noticing some missing data coming from the new Ads API. Upon further investigation, it's missing the rows where impressions == 0. The documentation seems to indicate that this should not be happening...

Workflow Changes in the Google Ads API  |  Google Developers

• Rows for zero impressions are returned by default in the Google Ads API. There is no includeZeroImpressions parameter. If you want to exclude zero impression rows, use a predicate such as metrics.impressions > 0 in your Google Ads Query Language.

...but the only conditional expression I have in my WHERE is around dates.

SELECT ...

FROM ad_group_ad

WHERE segments.date >= "2022-03-30" AND segments.date <= "2022-04-05"

Jason

[Jason Brinkle]

This is probably relevant: I'm using the Python SDK

...and I just stumbled across this: Zero Metrics  |  Google Ads API  |  Google Developers
Sounds like the date query turns on the filtering?

[Mat]

It's ridiculous but they have maked default the gap in the report if there is zero metrics for the row and they have deleted the option to include zero metrics. Hey Google, you have screwed it up.

[Google Ads API Forum Advisor]

Hello,

Thanks for reaching out. Zero metrics entities are always excluded when a report is segmented. If you segment by date and the selected entity does not have metrics within the specified date range, no row will be returned. 

Please see this guide that covers how zero metrics are handled under different reporting conditions.

Regards,
Matt
Google Ads API Team

Matt Google Ads API Team

ref:_00D1U1174p._5004Q2bbCeK:ref

[Mat]

The guide is useless. There is no way to handle the zero metrics because you do not give the option to get data with zero metrics.

"There is no way to get zero metrics rows." Period. This could be the whole guide. It used to be possible in the old API but it is not in the new one.

[Google Ads API Forum Advisor]

Hi Mat,

I have responded to your concern in the other user's thread. Please continue any further correspondence on that thread.