Hi Thanet, thank you for your reply.
The date range solves it if you get the date range right, i.e. you request a range where the product was not changed in that date range. However, I do not know when and if products were changed and thus my fix right now is to always filter out all duplicates which is bad as I thus cannot act on the information and have to skip the duplicate products completely. Ideally, the report would only return the product once (as OfferId is unique for the product and I would not expect to get the same product twice) and have all the properties like CategoryL5 with the most recent information, i.e. CategoryL5 is as it is RIGHT NOW for the product even if it was different in the past. Cheers Marc On Wednesday, April 5, 2017 at 9:27:17 AM UTC+2, Thanet Knack Praneenararat (AdWords API Team) wrote: > > Hi Marc, > > Thanks very much for reporting. > Your previous example then shows that *CategoryL5* really behaves like a > segment. > If it's a key column, even if you don't request for it, there should be > two rows returned. > I'll talk with engineering to see how we fix this. > > As for your other questions: > >> 1) How do I know what are the "key fields" in a report? > > Unfortunately, it's not quite obvious from the field itself. But we try to > document it in the summary description in the beginning of each report type > page. > > 2) You wrote "Have a look at OfferId and CategoryL5, you can tell that >> those two rows are different" - you mean combined, correct? Because the >> OfferId here is the same > > Yes, combined. It's like you have a composite key in relational databases. > Only one key can't tell uniqueness of a row. We have to use them together > to tell uniqueness. > > I find this confusing and would expect to get just one row with the >> product and with CategoryL5 set to the most recent value for that product... > > I've passed this feedback to engineering too. > For now, would using date range help you? Or does it always return two > rows for any kinds of date ranges? > > Best, > Thanet, AdWords API Team > > On Wednesday, April 5, 2017 at 4:16:32 PM UTC+9, Marc P wrote: >> >> Hi Thanet, >> >> thank you for your help. Two more questions to clarify: >> >> 1) How do I know what are the "key fields" in a report? >> 2) You wrote "Have a look at OfferId and CategoryL5, you can tell that >> those two rows are different" - you mean combined, correct? Because the >> OfferId here is the same >> >> My point is this: I want to get the current information of the product, >> however I get two rows for the same OfferId and it is different only on >> CategoryL5 - thus I do not know which value of CategoryL5 is current and >> which one is old / legacy. >> >> This only happens when the product was changed on CategoryL5 - it is the >> same product (same OfferId). It appears twice only because it was changed >> at some point in time. >> >> I find this confusing and would expect to get just one row with the >> product and with CategoryL5 set to the most recent value for that product... >> >> Thank you again >> Marc >> >> On Thursday, March 30, 2017 at 6:06:33 PM UTC+2, Thanet Knack >> Praneenararat (AdWords API Team) wrote: >>> >>> Hi Marc, >>> >>> It's true that they're not the segment field, but it's a *key* column >>> in this report type. >>> The key columns are what you need to include in order to tell the >>> uniqueness of the report row. >>> For instance, if you look at either only *AdGroupName*, *CampaignName* >>> in this report type, you can't distinguish two rows from each other. >>> But if you have a look at *OfferId* and *CategoryL5*, you can tell that >>> those two rows are different. >>> >>> Put it in another way, they're an attribute field *that even when >>> you've not requested them, they're still requested implicitly.* >>> You can't combine those rows that have at least one *key field* >>> different from each other. >>> Not requesting them in AWQL / report definition just makes the reporting >>> service not return them with the results. >>> >>> This is different from segment fields. If you don't request them, >>> they're not requested implicitly. >>> Once you request them, you're likely to get more report rows than usual. >>> >>> Hope this help. >>> >>> Thanet, AdWords API Team >>> >>> On Thursday, March 30, 2017 at 10:40:27 PM UTC+9, Marc P wrote: >>>> >>>> Hi Thanet, >>>> >>>> yes, in this case it is CategoryL5 - for another customer id it is >>>> ProductTypeL3. >>>> >>>> My point is: both ProductTypeL3 and CategoryL5 are attributes as >>>> specified in >>>> https://developers.google.com/adwords/api/docs/appendix/reports/shopping-performance-report >>>> >>>> They are not Segments. >>>> >>>> So my understanding is that they should not split the data. Rather I >>>> would assume to get just one result with ProductTypeL3 and CategoryL5 >>>> having the most recent attribute value ? >>>> >>>> Thank you for your help >>>> Marc >>>> >>>> On Thursday, March 30, 2017 at 8:56:22 AM UTC+2, Thanet Knack >>>> Praneenararat (AdWords API Team) wrote: >>>>> >>>>> Hello, >>>>> >>>>> It seems what makes your returned rows look duplicate is not >>>>> *ProductTypeL3*, but the *CategoryL5*. >>>>> As *CategoryL5 *is also the main key of SHOPPING_PERFORMANCE_REPORT, >>>>> this works as intended. >>>>> In other words, to tell the uniqueness of a row in this report type, >>>>> *CategoryL5* should be taken into account as well. >>>>> >>>>> Cheers, >>>>> Thanet, AdWords API Team >>>>> >>>>> On Tuesday, March 14, 2017 at 10:04:37 PM UTC+9, Firma Lemundo wrote: >>>>>> >>>>>> Hi everyone, >>>>>> >>>>>> I am facing the following issue: >>>>>> >>>>>> I am using the SHOPPING_PERFORMANCE_REPORT to find the performance by >>>>>> the products (OfferId). >>>>>> I am not using Date or other segments and the product is only in a >>>>>> single adgroup. >>>>>> >>>>>> However, I still get two entries, because the product's ProductTypeL3 >>>>>> <https://developers.google.com/adwords/api/docs/appendix/reports/shopping-performance-report#producttypel3> >>>>>> changed >>>>>> in the time frame. >>>>>> >>>>>> So I get different data for the same product (which is in different >>>>>> time frames) which is very annoying for my purpose. >>>>>> >>>>>> Moreover, ProductTypeL3 is not a segment field, so I wonder if this >>>>>> is a bug, or expected behavior? >>>>>> >>>>>> Comments and help much appreciated :) >>>>>> >>>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords 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 Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/1f5d75d5-1c46-4d0e-9262-c0b1e65d6bba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
