After a lot of investigation, on more than one hundred accounts, re-reading from 1st January 2019, I can add:
The strange finding is negative conversions on a report segmented to ConversionTrackerId. This happens with about 4% of the accounts. But... only with GEO_PERFORMANCE_REPORT! Not on keyword performance, ad performance etc.etc. I wrote I could see the negative conversions in the web UI as well. That's not really correct, in the web UI you cannot segment by conversion types. The negative conversion is there, just not by conversion type as I claimed On Tuesday, August 11, 2020 at 4:07:20 PM UTC+2, Zweitze wrote: > > So it was fixed a year ago, but now something is back! > But my explanation of Aug 2 2019 won't hold in this situation, something > else is going on. Now it's a Geo Performance report and its request is: > <?xml version="1.0" encoding="utf-8"?> > <reportDefinition> > <selector xmlns="https://adwords.google.com/api/adwords/cm/v201809";> > <fields>CampaignId</fields> > <fields>MostSpecificCriteriaId</fields> > <fields>CountryCriteriaId</fields> > <fields>CityCriteriaId</fields> > <fields>Date</fields> > <fields>Device</fields> > <fields>AdNetworkType2</fields> > <fields>ConversionTrackerId</fields> > <fields>Conversions</fields> > <fields>ViewThroughConversions</fields> > <fields>ConversionValue</fields> > <predicates> > <field>CampaignStatus</field> > <operator>IN</operator> > <values>ENABLED</values> > <values>PAUSED</values> > <values>REMOVED</values> > </predicates> > <predicates> > <field>LocationType</field> > <operator>EQUALS</operator> > <values>LOCATION_OF_PRESENCE</values> > </predicates> > <dateRange> > <min>20181202</min> > <max>20200811</max> > </dateRange> > </selector> > <reportName > xmlns="https://adwords.google.com/api/adwords/cm/v201809";>PhysicalLocationConversion > > 02-12-2018...11-08-2020</reportName> > <reportType xmlns="https://adwords.google.com/api/adwords/cm/v201809 > ">GEO_PERFORMANCE_REPORT</reportType> > <dateRangeType xmlns="https://adwords.google.com/api/adwords/cm/v201809 > ">CUSTOM_DATE</dateRangeType> > <downloadFormat xmlns=" > https://adwords.google.com/api/adwords/cm/v201809 > ">GZIPPED_XML</downloadFormat> > </reportDefinition> > > You get a lot of rows, four with negative conversions: > <row campaignID='1936550158' mostSpecificLocation='1010543' > countryTerritory='2528' city='1010543' day='2019-10-22' device='Mobile > devices with full browsers' networkWithSearchPartners='Google search' > conversionTrackerId='278161913' conversions='-1.00' viewThroughConv='0' > totalConvValue='-8.34'/> > <row campaignID='1692881737' mostSpecificLocation='9065109' > countryTerritory='2528' city='9063492' day='2019-05-31' device='Mobile > devices with full browsers' networkWithSearchPartners='Google search' > conversionTrackerId='278161913' conversions='-1.00' viewThroughConv='0' > totalConvValue='-8.34'/> > <row campaignID='1676831485' mostSpecificLocation='9064490' > countryTerritory='2528' city='9063488' day='2019-05-18' device='Mobile > devices with full browsers' networkWithSearchPartners='Google search' > conversionTrackerId='278161913' conversions='-1.00' viewThroughConv='0' > totalConvValue='-8.34'/> > <row campaignID='1676831485' mostSpecificLocation='9065109' > countryTerritory='2528' city='9063492' day='2019-07-29' device='Computers' > networkWithSearchPartners='Google search' conversionTrackerId='278161913' > conversions='-1.00' viewThroughConv='0' totalConvValue='-8.34'/> > > There's a subtle difference with the previous is issue: this time the > request includes ConversionTrackerId, which is a segmentation on conversion > types. In other words, the hypothesis with "Include in conversions" is off > the table. Also note that one of the records is from October 22, over two > months after the fix was implemented. > > This problem is probably not only related to the API. I managed to see the > record of May 18 in the web UI as well. I couldn't see the records of May > 31 and Oct 22 in the web UI, probably due to the heavy segmenting involved, > which is not supported by the web UI. Nevertheless I'd like to ask the > question here because product support don't understand why this is problem. > > If anyone can look into this, thanks! > > Zweitze. > > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/23e34c97-6028-4dd6-b81d-a6aa5b7adf15o%40googlegroups.com.
