Getting zero impression rows after setting setting includeZeroImpression to False

[Ketaki]

Hi AdWords team,

We have set AdWordsAppConfig's property IncludeZeroImpressions to False in the code as shown below,

  AdWordsUser user = new AdWordsUser();

   AdWordsAppConfig config = user.Config as AdWordsAppConfig;

  config.IncludeZeroImpressions = False

But we are getting some rows with zero impressions. From API we are gettimg more no. of zero impression rows as compared by code.

But can you please verify why Reporting service is returning the some no. of zero impression rows?

Regards,

Ketaki.

[Vishal Vinayak (Adwords API Team)]

Hi Ketaki,

To help debug, could you please provide me with the SOAP XML report definition? Please click on Reply privately to author when responding. 

Regards,

Vishal, AdWords API Team

[Ketaki]

Hi Vishal,

Below is the SOAP XML report definition and definition of AdWordsUser,

<reportDefinition xmlns="https://adwords.google.com/api/adwords/cm/v201603">

 <selector>

<fields>ExternalCustomerId</fields>

<fields>AccountDescriptiveName</fields>

<fields>AdGroupId</fields>

<fields>AdGroupName</fields>

<fields>CampaignId</fields>

<fields>CampaignName</fields>

<fields>Id</fields>

<fields>Criteria</fields>

<fields>KeywordMatchType</fields>

<fields>AdNetworkType2</fields>

<fields>Device</fields>

<fields>ClickType</fields>

<fields>Date</fields>

<fields>ConversionCategoryName</fields>

<fields>ConversionTypeName</fields>

<fields>ClickConversionRate</fields>

<fields>ConversionRate</fields>

<fields>ConvertedClicks</fields>

<fields>Conversions</fields>

<fields>ConversionValue</fields>

<fields>CostPerConvertedClick</fields>

<fields>ValuePerConvertedClick</fields>

<fields>ViewThroughConversions</fields>

   <predicates>

   </predicates>

   <dateRange>

<max>XXX</max>

<min>XXX</min>

   </dateRange>

 </selector>

 <reportName>AdWords Data Feed: Keyword Conversion</reportName>

 <reportType>Google.Api.Ads.AdWords.v201603.ReportDefinitionReportType.KEYWORDS_PERFORMANCE_REPORT</reportType>

 <dateRangeType>CUSTOM_DATE</dateRangeType>

 <downloadFormat>XML</downloadFormat>

</reportDefinition>

<AdWordsUser = Google.Api.Ads.AdWords.Lib.AdWordsUser>

<base = Google.Api.Ads.Common.Lib.AdsUser>

<Config>

<AdWordsAppConfig>

<DeveloperToken>XXX</DeveloperToken>

<ClientCustomerId>XXX</ClientCustomerId>

<IncludeZeroImpressions>False</IncludeZeroImpressions>

</AdWordsAppConfig>

<OAuth2AccessToken>XXX</OAuth2AccessToken>

<OAuth2ClientId>XXX</OAuth2ClientId>

<OAuth2ClientSecret>XXX</OAuth2ClientSecret>

<OAuth2RedirectUri>XXX</OAuth2RedirectUri>

</Config>

</base>

</AdwordsUser>

As you can see above we have set IncludeZeroImpressions property to False. Still we are getting zero impression rows. Means we are getting rows with below fields's value as zero,

ClickConversionRate

ConversionRate

ConvertedClicks

Conversions

ConversionValue

CostPerConvertedClick

ValuePerConvertedClick

ViewThroughConversions

Regards,

Ketaki.

[Vishal Vinayak (Adwords API Team)]

Hi Ketaki,

The includeZeroImpressions field is related to Impressions only. Setting it true would ensure that the report does not contain any records when there are no impressions. Other fields, however, can have zero values, even when Impressions are non zero. I can still try to double check this error for you. Could you please provide me with a sample report and your clientCustomerId? Please click on Reply privately to author when responding. 

[Ketaki]

Hi Vishal,

On the AdWords developer site  [Link is: https://developers.google.com/adwords/api/docs/guides/zero-impression-reports]

includeZeroImpressions = false represents,

rows are excluded only if all specified metric fields in the query have zero values.

If you really want to only get rows where the Impressions field is not zero, consider excluding zero impressions with a predicate

With this consideration report should not return any rows with all metric's value is zero; when includeZeroImpressions is set to false.

Please correct me if I am wrong.

Regards,

Ketaki.

[Vishal Vinayak (Adwords API Team)]

Hi Ketaki,

To be able to help further, could you please provide me with a sample report generated via the API (where you see this problem) and your clientCustomerId? Please click on Reply privately to author when responding. 

[Ketaki]

Hi Vishal,

I have sent you the sample report definition with ClientCustomerId by Reply privately to author option. Can you please debug and provide reason of getting zero impression rows?

Regards,

Ketaki.

[Ketaki]

Hi Vishal,

Do you have any updates on this?

Regards,

Ketaki.

[Vishal Vinayak (Adwords API Team)]

Ketaki - I sent the following response to your email (which you might have missed) at 08/18/16 13:58:51 Eastern Standard Time. Waiting on you to provide the necessary information. Please click on Reply privately to author when responding.

------------------------------------------

Ketaki,

To be able to debug, I would also need the sample report where you observed the issue. You can send the CSV file that was generated or simply a text file containing some of the records from the report that you think are zero impression records.

Regards,

Vishal, AdWords API Team  

------------------------------------------

[Ketaki]

Hi Vishal,

I have sent you the file with zero impression rows.

Thanks.

Regards,

Ketaki.

[Vishal Vinayak (Adwords API Team)]

Hi Ketaki,

After checking, I found out that although conversions are zero for the specified rows, impressions are non-zero (for that day). To exclude rows in that case, I would recommend using a predicate on conversions i.e. conversions > 0. Please refer to this guide for more information on how to use predicates in your report.

[Ketaki]

Thank you Vishal. I checked by including impressions in the report fields, and it has non-zero values.

So now we can say that,

"includeZeroImpressions = false represents,

rows are excluded only if all specified metric fields along with impressions in the query have zero values."

Regards,

Ketaki.

[Nadine Sundquist (AdWords API Team)]

Hi Ketaki,

I'm double-checking to make sure this is expected behavior. So far, it looks like it is expected. If so, we'll be updating our documentation. Thanks for bringing this up.

Best,

Nadine, AdWords API Team