Duplicate entries for Criterions in Product Partition Report

[Stefan Kleine Stegemann]

When downloading a product partition report, we sometimes receive duplicate rows for a single criterion. The reports are segmented by Date and Device and we're getting two rows for the same combination of CampaignId, AdGroupId, CriterionId and Device. When this happens, one row usually contains only 1 impression but no clicks and no conversions while the other row looks like it contains the "real" data.

Here is the report definition:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<reportDefinition xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201609">
  <ns2:selector>
    <ns2:fields>CampaignId</ns2:fields>
    <ns2:fields>AdGroupId</ns2:fields>
    <ns2:fields>Id</ns2:fields>
    <ns2:fields>Date</ns2:fields>
    <ns2:fields>Device</ns2:fields>
    <ns2:fields>Impressions</ns2:fields>
    <ns2:fields>Clicks</ns2:fields>
    <ns2:fields>Conversions</ns2:fields>
    <ns2:predicates>
      <ns2:field>CampaignId</ns2:field>
      <ns2:operator>EQUALS</ns2:operator>
      <ns2:values>xxxxxxxx</ns2:values>
    </ns2:predicates>
    <ns2:dateRange>
      <ns2:min>20161015</ns2:min>
      <ns2:max>20161113</ns2:max>
    </ns2:dateRange>
  </ns2:selector>
  <ns2:reportName>BMOS Report</ns2:reportName>
  <ns2:reportType>PRODUCT_PARTITION_REPORT</ns2:reportType>
  <ns2:dateRangeType>CUSTOM_DATE</ns2:dateRangeType>
  <ns2:downloadFormat>GZIPPED_XML</ns2:downloadFormat>
</reportDefinition>

And here the duplicate entries with "obfuscated" ids:

CampaignId,AdGroupId,Id,Date,Device,Impressions,Clicks,Conversions
888888888,77777777777,11111111111,2016-10-17,DESKTOP,117,0,0
888888888,77777777777,11111111111,2016-10-17,DESKTOP,1,0,0
999999999,66666666666,22222222222,2016-11-10,DESKTOP,1,0,0
999999999,66666666666,22222222222,2016-11-10,DESKTOP,6931,160,1

Any idea why this happens? Is this behavior expected?

[Shwetha Vastrad (AdWords API Team)]

Hi Stefan,

Could you provide the clientCustomerId or the CampaignId where you observed duplicate entries? This will help me in investigating the root cause for this issue. 

Thanks,

Shwetha, AdWords API Team. 

[Stefan Kleine Stegemann]

Hi,

the problem has been solved. In fact, it turned out to be a problem on our side. Thanks very much for your support and your help, AdWords API Team!

Best,

Stefan