Re: Shopping Performance Report returns same product twice

['Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hello Ad Ja,

Unfortunately, this doesn't look like very high priority for engineering at 
this moment.
So, there is no progress on this right now.

Also, do you know any other way of getting a report where it returns 
> products with the most recent information?

As far as I know, we cannot get that using the current version of the API. 

Best,
Thanet, AdWords API Team

On Friday, July 27, 2018 at 2:05:00 PM UTC+9, Ad Ja wrote:
>
> Hi Thanet,
>
> Apologies if it's late, but I'm currently working on a project that would 
> make this very useful.
> Is there any updates on this?
>
> Also, do you know any other way of getting a report where it returns 
> products with the most recent information?
>
> Thanks.
>
> On Wednesday, July 12, 2017 at 8:23:44 AM UTC+1, Thanet Knack 
> Praneenararat (AdWords API Team) wrote:
>>
>> Hello Marc,
>>
>> Really sorry for this long waiting.
>> It was a long conversation between many parties.
>>
>> First, it looks like this works as intended for engineering to return the 
>> CategoryL* as segment fields.
>> The documentation needs to be fixed.
>>
>> About the date range per row, I'm pushing this through but cannot tell 
>> the exact date to finish.
>>
>> Best,
>> Thanet, AdWords API Team
>>
>> On Tuesday, July 11, 2017 at 11:02:57 PM UTC+9, Marc P wrote:
>>>
>>> Hi Thanet,
>>>
>>> any updates on this issue?
>>>
>>> We are still having many problems due to this.
>>>
>>> At the very least, it would be helpful to get a date range per row in 
>>> the response, so we can now at what times the ID performed good and at what 
>>> times not so good.
>>>
>>> Cheers
>>> Marc
>>>
>>> On Wednesday, April 26, 2017 at 10:30:35 AM UTC+2, Thanet Knack 
>>> Praneenararat (AdWords API Team) wrote:

 Hi Marc,

 I totally understand what you said but, unfortunately, it's not 
 supported by the current version of SHOPPING_PERFORMANCE_REPORT.
 I'll give your feedback as a feature request to engineering.

 Best,
 Thanet, AdWords API Team

 On Tuesday, April 25, 2017 at 11:07:45 PM UTC+9, Firma Lemundo wrote:
>
> Hi Thanet,
>
> CategoryL5 is just one example, this seems to be happening for almost 
> all product related attributes.
>
> I guess the intended functionality is to show that a product changed 
> at some point in time, but this is very misguiding as I would not expect 
> to 
> get the same product twice (it has the same OfferId...) without the 
> information at what point it was changed or what time range we are 
> talking 
> about.
>
> This might be a case where it would be useful to have a parameter to 
> set, something like "showProductChanges = true/false".
>
> At the very least, there should be a possibility to distinguish at 
> what point in time the product changed, so for example:
>
> OfferId CategoryL2  DateRange
> 123  Clothing/Pants 03/14 - 03/18
> 123  Clothing/Shorts03/18 - 03/29
>
> In that case, I could at least detect which entry is the most recent 
> one (Clothing/Shorts) and use that one, but getting the results as is the 
> case now is like this:
>
> OfferId CategoryL2
> 123  Clothing/Pants
> 123  Clothing/Shorts  
>
> and I do not know whether the product with OfferId 123 is in 
> CategoryL2 Clothing/Pants or Clothing/Shorts RIGHT NOW.
>
> Thanks
> Marc
>
> Am Montag, 24. April 2017 19:07:03 UTC+2 schrieb Thanet Knack 
> Praneenararat (AdWords API Team):
>>
>> Hello Marc,
>>
>> Sorry for the delay. It looks like this works as intended--all data 
>> of CategoryL5 is returned in SHOPPING_PERFORMANCE_REPORT.
>> I'm still asking if there are other workarounds for this.
>>
>> Best,
>> Thanet, AdWords API Team
>>
>> On Monday, April 24, 2017 at 4:01:49 PM UTC+9, Marc P wrote:
>>>
>>> Hi Thanet,
>>>
>>> any update on this topic?
>>>
>>> Thanks
>>> 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 mea

Re: Shopping Performance Report returns same product twice

[Ad Ja]

Hi Thanet,

Apologies if it's late, but I'm currently working on a project that would 
make this very useful.
Is there any updates on this?

Also, do you know any other way of getting a report where it returns 
products with the most recent information?

Thanks.

On Wednesday, July 12, 2017 at 8:23:44 AM UTC+1, Thanet Knack Praneenararat 
(AdWords API Team) wrote:
>
> Hello Marc,
>
> Really sorry for this long waiting.
> It was a long conversation between many parties.
>
> First, it looks like this works as intended for engineering to return the 
> CategoryL* as segment fields.
> The documentation needs to be fixed.
>
> About the date range per row, I'm pushing this through but cannot tell the 
> exact date to finish.
>
> Best,
> Thanet, AdWords API Team
>
> On Tuesday, July 11, 2017 at 11:02:57 PM UTC+9, Marc P wrote:
>>
>> Hi Thanet,
>>
>> any updates on this issue?
>>
>> We are still having many problems due to this.
>>
>> At the very least, it would be helpful to get a date range per row in the 
>> response, so we can now at what times the ID performed good and at what 
>> times not so good.
>>
>> Cheers
>> Marc
>>
>> On Wednesday, April 26, 2017 at 10:30:35 AM UTC+2, Thanet Knack 
>> Praneenararat (AdWords API Team) wrote:
>>>
>>> Hi Marc,
>>>
>>> I totally understand what you said but, unfortunately, it's not 
>>> supported by the current version of SHOPPING_PERFORMANCE_REPORT.
>>> I'll give your feedback as a feature request to engineering.
>>>
>>> Best,
>>> Thanet, AdWords API Team
>>>
>>> On Tuesday, April 25, 2017 at 11:07:45 PM UTC+9, Firma Lemundo wrote:

 Hi Thanet,

 CategoryL5 is just one example, this seems to be happening for almost 
 all product related attributes.

 I guess the intended functionality is to show that a product changed at 
 some point in time, but this is very misguiding as I would not expect to 
 get the same product twice (it has the same OfferId...) without the 
 information at what point it was changed or what time range we are talking 
 about.

 This might be a case where it would be useful to have a parameter to 
 set, something like "showProductChanges = true/false".

 At the very least, there should be a possibility to distinguish at what 
 point in time the product changed, so for example:

 OfferId CategoryL2  DateRange
 123  Clothing/Pants 03/14 - 03/18
 123  Clothing/Shorts03/18 - 03/29

 In that case, I could at least detect which entry is the most recent 
 one (Clothing/Shorts) and use that one, but getting the results as is the 
 case now is like this:

 OfferId CategoryL2
 123  Clothing/Pants
 123  Clothing/Shorts  

 and I do not know whether the product with OfferId 123 is in CategoryL2 
 Clothing/Pants or Clothing/Shorts RIGHT NOW.

 Thanks
 Marc

 Am Montag, 24. April 2017 19:07:03 UTC+2 schrieb Thanet Knack 
 Praneenararat (AdWords API Team):
>
> Hello Marc,
>
> Sorry for the delay. It looks like this works as intended--all data of 
> CategoryL5 is returned in SHOPPING_PERFORMANCE_REPORT.
> I'm still asking if there are other workarounds for this.
>
> Best,
> Thanet, AdWords API Team
>
> On Monday, April 24, 2017 at 4:01:49 PM UTC+9, Marc P wrote:
>>
>> Hi Thanet,
>>
>> any update on this topic?
>>
>> Thanks
>> 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 

Re: Shopping Performance Report returns same product twice

[Marc P]

Hi Thanet,

thank you for the update. This sounds promising. Looking forward to getting 
the date ranges per row :)

Cheers
Marc

On Wednesday, July 12, 2017 at 9:23:44 AM UTC+2, Thanet Knack Praneenararat 
(AdWords API Team) wrote:
>
> Hello Marc,
>
> Really sorry for this long waiting.
> It was a long conversation between many parties.
>
> First, it looks like this works as intended for engineering to return the 
> CategoryL* as segment fields.
> The documentation needs to be fixed.
>
> About the date range per row, I'm pushing this through but cannot tell the 
> exact date to finish.
>
> Best,
> Thanet, AdWords API Team
>
> On Tuesday, July 11, 2017 at 11:02:57 PM UTC+9, Marc P wrote:
>>
>> Hi Thanet,
>>
>> any updates on this issue?
>>
>> We are still having many problems due to this.
>>
>> At the very least, it would be helpful to get a date range per row in the 
>> response, so we can now at what times the ID performed good and at what 
>> times not so good.
>>
>> Cheers
>> Marc
>>
>> On Wednesday, April 26, 2017 at 10:30:35 AM UTC+2, Thanet Knack 
>> Praneenararat (AdWords API Team) wrote:
>>>
>>> Hi Marc,
>>>
>>> I totally understand what you said but, unfortunately, it's not 
>>> supported by the current version of SHOPPING_PERFORMANCE_REPORT.
>>> I'll give your feedback as a feature request to engineering.
>>>
>>> Best,
>>> Thanet, AdWords API Team
>>>
>>> On Tuesday, April 25, 2017 at 11:07:45 PM UTC+9, Firma Lemundo wrote:

 Hi Thanet,

 CategoryL5 is just one example, this seems to be happening for almost 
 all product related attributes.

 I guess the intended functionality is to show that a product changed at 
 some point in time, but this is very misguiding as I would not expect to 
 get the same product twice (it has the same OfferId...) without the 
 information at what point it was changed or what time range we are talking 
 about.

 This might be a case where it would be useful to have a parameter to 
 set, something like "showProductChanges = true/false".

 At the very least, there should be a possibility to distinguish at what 
 point in time the product changed, so for example:

 OfferId CategoryL2  DateRange
 123  Clothing/Pants 03/14 - 03/18
 123  Clothing/Shorts03/18 - 03/29

 In that case, I could at least detect which entry is the most recent 
 one (Clothing/Shorts) and use that one, but getting the results as is the 
 case now is like this:

 OfferId CategoryL2
 123  Clothing/Pants
 123  Clothing/Shorts  

 and I do not know whether the product with OfferId 123 is in CategoryL2 
 Clothing/Pants or Clothing/Shorts RIGHT NOW.

 Thanks
 Marc

 Am Montag, 24. April 2017 19:07:03 UTC+2 schrieb Thanet Knack 
 Praneenararat (AdWords API Team):
>
> Hello Marc,
>
> Sorry for the delay. It looks like this works as intended--all data of 
> CategoryL5 is returned in SHOPPING_PERFORMANCE_REPORT.
> I'm still asking if there are other workarounds for this.
>
> Best,
> Thanet, AdWords API Team
>
> On Monday, April 24, 2017 at 4:01:49 PM UTC+9, Marc P wrote:
>>
>> Hi Thanet,
>>
>> any update on this topic?
>>
>> Thanks
>> 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
>>>
>>> 

Re: Shopping Performance Report returns same product twice

['Thanet Knack Praneenararat (AdWords API Team)' via AdWords API Forum]

Hello Marc,

Really sorry for this long waiting.
It was a long conversation between many parties.

First, it looks like this works as intended for engineering to return the 
CategoryL* as segment fields.
The documentation needs to be fixed.

About the date range per row, I'm pushing this through but cannot tell the 
exact date to finish.

Best,
Thanet, AdWords API Team

On Tuesday, July 11, 2017 at 11:02:57 PM UTC+9, Marc P wrote:
>
> Hi Thanet,
>
> any updates on this issue?
>
> We are still having many problems due to this.
>
> At the very least, it would be helpful to get a date range per row in the 
> response, so we can now at what times the ID performed good and at what 
> times not so good.
>
> Cheers
> Marc
>
> On Wednesday, April 26, 2017 at 10:30:35 AM UTC+2, Thanet Knack 
> Praneenararat (AdWords API Team) wrote:
>>
>> Hi Marc,
>>
>> I totally understand what you said but, unfortunately, it's not supported 
>> by the current version of SHOPPING_PERFORMANCE_REPORT.
>> I'll give your feedback as a feature request to engineering.
>>
>> Best,
>> Thanet, AdWords API Team
>>
>> On Tuesday, April 25, 2017 at 11:07:45 PM UTC+9, Firma Lemundo wrote:
>>>
>>> Hi Thanet,
>>>
>>> CategoryL5 is just one example, this seems to be happening for almost 
>>> all product related attributes.
>>>
>>> I guess the intended functionality is to show that a product changed at 
>>> some point in time, but this is very misguiding as I would not expect to 
>>> get the same product twice (it has the same OfferId...) without the 
>>> information at what point it was changed or what time range we are talking 
>>> about.
>>>
>>> This might be a case where it would be useful to have a parameter to 
>>> set, something like "showProductChanges = true/false".
>>>
>>> At the very least, there should be a possibility to distinguish at what 
>>> point in time the product changed, so for example:
>>>
>>> OfferId CategoryL2  DateRange
>>> 123  Clothing/Pants 03/14 - 03/18
>>> 123  Clothing/Shorts03/18 - 03/29
>>>
>>> In that case, I could at least detect which entry is the most recent one 
>>> (Clothing/Shorts) and use that one, but getting the results as is the case 
>>> now is like this:
>>>
>>> OfferId CategoryL2
>>> 123  Clothing/Pants
>>> 123  Clothing/Shorts  
>>>
>>> and I do not know whether the product with OfferId 123 is in CategoryL2 
>>> Clothing/Pants or Clothing/Shorts RIGHT NOW.
>>>
>>> Thanks
>>> Marc
>>>
>>> Am Montag, 24. April 2017 19:07:03 UTC+2 schrieb Thanet Knack 
>>> Praneenararat (AdWords API Team):

 Hello Marc,

 Sorry for the delay. It looks like this works as intended--all data of 
 CategoryL5 is returned in SHOPPING_PERFORMANCE_REPORT.
 I'm still asking if there are other workarounds for this.

 Best,
 Thanet, AdWords API Team

 On Monday, April 24, 2017 at 4:01:49 PM UTC+9, Marc P wrote:
>
> Hi Thanet,
>
> any update on this topic?
>
> Thanks
> 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? 
>

Re: Shopping Performance Report returns same product twice

[Marc P]

Hi Thanet,

any updates on this issue?

We are still having many problems due to this.

At the very least, it would be helpful to get a date range per row in the 
response, so we can now at what times the ID performed good and at what 
times not so good.

Cheers
Marc

On Wednesday, April 26, 2017 at 10:30:35 AM UTC+2, Thanet Knack 
Praneenararat (AdWords API Team) wrote:
>
> Hi Marc,
>
> I totally understand what you said but, unfortunately, it's not supported 
> by the current version of SHOPPING_PERFORMANCE_REPORT.
> I'll give your feedback as a feature request to engineering.
>
> Best,
> Thanet, AdWords API Team
>
> On Tuesday, April 25, 2017 at 11:07:45 PM UTC+9, Firma Lemundo wrote:
>>
>> Hi Thanet,
>>
>> CategoryL5 is just one example, this seems to be happening for almost all 
>> product related attributes.
>>
>> I guess the intended functionality is to show that a product changed at 
>> some point in time, but this is very misguiding as I would not expect to 
>> get the same product twice (it has the same OfferId...) without the 
>> information at what point it was changed or what time range we are talking 
>> about.
>>
>> This might be a case where it would be useful to have a parameter to set, 
>> something like "showProductChanges = true/false".
>>
>> At the very least, there should be a possibility to distinguish at what 
>> point in time the product changed, so for example:
>>
>> OfferId CategoryL2  DateRange
>> 123  Clothing/Pants 03/14 - 03/18
>> 123  Clothing/Shorts03/18 - 03/29
>>
>> In that case, I could at least detect which entry is the most recent one 
>> (Clothing/Shorts) and use that one, but getting the results as is the case 
>> now is like this:
>>
>> OfferId CategoryL2
>> 123  Clothing/Pants
>> 123  Clothing/Shorts  
>>
>> and I do not know whether the product with OfferId 123 is in CategoryL2 
>> Clothing/Pants or Clothing/Shorts RIGHT NOW.
>>
>> Thanks
>> Marc
>>
>> Am Montag, 24. April 2017 19:07:03 UTC+2 schrieb Thanet Knack 
>> Praneenararat (AdWords API Team):
>>>
>>> Hello Marc,
>>>
>>> Sorry for the delay. It looks like this works as intended--all data of 
>>> CategoryL5 is returned in SHOPPING_PERFORMANCE_REPORT.
>>> I'm still asking if there are other workarounds for this.
>>>
>>> Best,
>>> Thanet, AdWords API Team
>>>
>>> On Monday, April 24, 2017 at 4:01:49 PM UTC+9, Marc P wrote:

 Hi Thanet,

 any update on this topic?

 Thanks
 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 on

Re: Shopping Performance Report returns same product twice

['Thanet Knack Praneenararat (AdWords API Team)' via AdWords API Forum]

Hi Marc,

I totally understand what you said but it's not supported by the current 
version of SHOPPING_PERFORMANCE_REPORT.
I'll give your feedback as a feature request to engineering.

Best,
Thanet, AdWords API Team

On Tuesday, April 25, 2017 at 11:07:45 PM UTC+9, Firma Lemundo wrote:
>
> Hi Thanet,
>
> CategoryL5 is just one example, this seems to be happening for almost all 
> product related attributes.
>
> I guess the intended functionality is to show that a product changed at 
> some point in time, but this is very misguiding as I would not expect to 
> get the same product twice (it has the same OfferId...) without the 
> information at what point it was changed or what time range we are talking 
> about.
>
> This might be a case where it would be useful to have a parameter to set, 
> something like "showProductChanges = true/false".
>
> At the very least, there should be a possibility to distinguish at what 
> point in time the product changed, so for example:
>
> OfferId CategoryL2  DateRange
> 123  Clothing/Pants 03/14 - 03/18
> 123  Clothing/Shorts03/18 - 03/29
>
> In that case, I could at least detect which entry is the most recent one 
> (Clothing/Shorts) and use that one, but getting the results as is the case 
> now is like this:
>
> OfferId CategoryL2
> 123  Clothing/Pants
> 123  Clothing/Shorts  
>
> and I do not know whether the product with OfferId 123 is in CategoryL2 
> Clothing/Pants or Clothing/Shorts RIGHT NOW.
>
> Thanks
> Marc
>
> Am Montag, 24. April 2017 19:07:03 UTC+2 schrieb Thanet Knack 
> Praneenararat (AdWords API Team):
>>
>> Hello Marc,
>>
>> Sorry for the delay. It looks like this works as intended--all data of 
>> CategoryL5 is returned in SHOPPING_PERFORMANCE_REPORT.
>> I'm still asking if there are other workarounds for this.
>>
>> Best,
>> Thanet, AdWords API Team
>>
>> On Monday, April 24, 2017 at 4:01:49 PM UTC+9, Marc P wrote:
>>>
>>> Hi Thanet,
>>>
>>> any update on this topic?
>>>
>>> Thanks
>>> 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 ins

Re: Shopping Performance Report returns same product twice

[Firma Lemundo]

Hi Thanet,

CategoryL5 is just one example, this seems to be happening for almost all 
product related attributes.

I guess the intended functionality is to show that a product changed at 
some point in time, but this is very misguiding as I would not expect to 
get the same product twice (it has the same OfferId...) without the 
information at what point it was changed or what time range we are talking 
about.

This might be a case where it would be useful to have a parameter to set, 
something like "showProductChanges = true/false".

At the very least, there should be a possibility to distinguish at what 
point in time the product changed, so for example:

OfferId CategoryL2  DateRange
123  Clothing/Pants 03/14 - 03/18
123  Clothing/Shorts03/18 - 03/29

In that case, I could at least detect which entry is the most recent one 
(Clothing/Shorts) and use that one, but getting the results as is the case 
now is like this:

OfferId CategoryL2
123  Clothing/Pants
123  Clothing/Shorts  

and I do not know whether the product with OfferId 123 is in CategoryL2 
Clothing/Pants or Clothing/Shorts RIGHT NOW.

Thanks
Marc

Am Montag, 24. April 2017 19:07:03 UTC+2 schrieb Thanet Knack Praneenararat 
(AdWords API Team):
>
> Hello Marc,
>
> Sorry for the delay. It looks like this works as intended--all data of 
> CategoryL5 is returned in SHOPPING_PERFORMANCE_REPORT.
> I'm still asking if there are other workarounds for this.
>
> Best,
> Thanet, AdWords API Team
>
> On Monday, April 24, 2017 at 4:01:49 PM UTC+9, Marc P wrote:
>>
>> Hi Thanet,
>>
>> any update on this topic?
>>
>> Thanks
>> 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 lea

Re: Shopping Performance Report returns same product twice

['Thanet Knack Praneenararat (AdWords API Team)' via AdWords API Forum]

Hello Marc,

Sorry for the delay. It looks like this works as intended--all data of 
CategoryL5 is returned in SHOPPING_PERFORMANCE_REPORT.
I'm still asking if there are other workarounds for this.

Best,
Thanet, AdWords API Team

On Monday, April 24, 2017 at 4:01:49 PM UTC+9, Marc P wrote:
>
> Hi Thanet,
>
> any update on this topic?
>
> Thanks
> 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 *C

Re: Shopping Performance Report returns same product twice

[Marc P]

Hi Thanet,

any update on this topic?

Thanks
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 

Re: Shopping Performance Report returns same product twice

[Marc P]

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

Re: Shopping Performance Report returns same product twice

['Thanet Knack Praneenararat (AdWords API Team)' via AdWords API Forum]

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 
> 

Re: Shopping Performance Report returns same product twice

[Marc P]

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

Re: Shopping Performance Report returns same product twice

[Marc P]

Hi Thanet,

another request confirmed my confusion and my assumption that CategoryL5 
behaves as a segment in this case.
When I do the same request without requestion the CategoryLX fields, I get 
just one result with the OfferId.

SELECT OfferId,   AdGroupId,   AdGroupStatus,   AdGroupName,   
CampaignName,   Brand,   ProductCondition,   ProductTypeL1, 
  ProductTypeL2,   ProductTypeL3,   ProductTypeL4,   
ProductTypeL5,   CustomAttribute0,   CustomAttribute1,   
CustomAttribute2,   CustomAttribute3,   CustomAttribute4, 
 Channel,   ChannelExclusivity,   SearchClickShare,   
SearchImpressionShare,   Ctr,   Clicks,   Impressions,   
Cost,   ConversionValue,   ConversionRate,   Conversions,   
AverageCpc FROM SHOPPING_PERFORMANCE_REPORT WHERE CampaignStatus IN 
[ENABLED] AND AdGroupStatus IN [ENABLED] AND ConversionValue > 0 AND Cost > 
0 AND OfferId = 12044542 

-> 1 Result with OfferId 12044542

SELECT OfferId,   AdGroupId,   AdGroupStatus,   AdGroupName,   
CampaignName,   Brand,   ProductCondition,   ProductTypeL1, 
  ProductTypeL2,   ProductTypeL3,   ProductTypeL4,   
ProductTypeL5,   CustomAttribute0,   CustomAttribute1,   
CustomAttribute2,   CustomAttribute3,   CustomAttribute4,   
CategoryL1,   CategoryL2,   CategoryL3,   CategoryL4,   
CategoryL5,   Channel,   ChannelExclusivity,   
SearchClickShare,   SearchImpressionShare,   Ctr,   Clicks, 
  Impressions,   Cost,   ConversionValue,   ConversionRate, 
  Conversions,   AverageCpc FROM SHOPPING_PERFORMANCE_REPORT WHERE 
CampaignStatus IN [ENABLED] AND AdGroupStatus IN [ENABLED] AND 
ConversionValue > 0 AND Cost > 0 AND OfferId = 12044542 

-> 2 Results with OfferId 12044542 TWICE -> differing only on CategoryL5

Cheers
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 
 
  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

Re: Shopping Performance Report returns same product twice

['Thanet Knack Praneenararat (AdWords API Team)' via AdWords API Forum]

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 
>>> 
>>>  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/658f97f1-bad8-465f-8278-2d920cbfe785%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Shopping Performance Report returns same product twice

[Marc P]

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 
>> 
>>  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/192136c2-bd3e-4a1a-add2-cfc0c89d79f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Shopping Performance Report returns same product twice

['Thanet Knack Praneenararat (AdWords API Team)' via AdWords API Forum]

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 
> 
>  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/e294eb17-29de-48fc-aa8f-efe13844f24b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Shopping Performance Report returns same product twice

['Thanet Knack Praneenararat (AdWords API Team)' via AdWords API Forum]

Hello,

Let us investigate more based on your information sent earlier.
I'll update this thread once we know more.

Best,
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 
> 
>  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/a76858e0-c889-41bb-809b-c29cf9f9b264%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Shopping Performance Report returns same product twice

['Sreelakshmi Sasidharan (AdWords API Team)' via AdWords API Forum]

Hi, 

To take a closer look at your issue, could you please *Reply privately to 
author* and share your report definition, a copy of the 
SHOPPING_PERFORMANCE_REPORT and you client customer Id?

Thanks,
Sreelakshmi, AdWords API Team

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/6f148efd-0ce9-4c9c-8eaa-bfeed6493b91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Shopping Performance Report returns same product twice

[Firma Lemundo]

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 

 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/3ceef01e-4f52-434f-9790-bcd51f1c50f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.