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:
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.