I really appreciate your response, that is very helpful. I am a version behind on the API and was hoping not to go through an SDK update (it is a painful process with the PHP library right now). That allowed me to get more data in place. Here is a draft example of the report I was able to generate using a customer's data that happens to have a Shopping account attached to it.
Those column labels are likely wrong, but I don't have anything else to explain them. I'd rather show a more descriptive name than IDs, as those are meaningless to the end user. Is there any guidance on what we can show here to make this actionable? - Stephen On Thursday, February 5, 2015 at 2:00:46 PM UTC-6, Josh Radcliff (AdWords API Team) wrote: > > Hi, > > Regarding the errors you mentioned, please note that the report > documentation > <https://developers.google.com/adwords/api/docs/appendix/reports#product-partition> > shows > the fields that are available in the *latest version* of the API, which > is currently v201409. If you are using an earlier version (v201406), you > can use ReportDefinitionService.getReportFields > <https://developers.google.com/adwords/api/docs/reference/v201406/ReportDefinitionService#getReportFields> > for > v201406 to get the list of available fields. > > Regarding the difference between the two reports, the > SHOPPING_PERFORMANCE_REPORT provides statistics at the *product* level, > while the PRODUCT_PARTITION_REPORT provides statistics at the *criterion* > level > (specifically, one row per AdGroupCriterion > <https://developers.google.com/adwords/api/docs/reference/v201409/AdGroupCriterionService.AdGroupCriterion> > where > the criterion > <https://developers.google.com/adwords/api/docs/reference/v201409/AdGroupCriterionService.AdGroupCriterion#criterion> > is > of type ProductPartition > <https://developers.google.com/adwords/api/docs/reference/v201409/AdGroupCriterionService.ProductPartition>). > > The former is useful for giving advertisers a view of which products are > being advertised in their impressions and which of those impressions are > generating clicks. The latter is useful for evaluating their bidding > configuration, since all bidding in shopping campaigns is configured at the > *AdGroupCriterion* level as described in our Shopping campaigns guide > <https://developers.google.com/adwords/api/docs/guides/shopping#partitioning>. > See the > detailed descriptions for the reports here > <https://developers.google.com/adwords/api/docs/appendix/reports#product-partition> > and here > <https://developers.google.com/adwords/api/docs/appendix/reports#shopping> as > well. > > Best regards, > Josh, AdWords API Team > > On Thursday, February 5, 2015 at 1:33:06 PM UTC-5, Stephen Yeargin wrote: >> >> Hi there! >> >> We are in the process of implementing R.120 as part of the RMF audit to >> include the PRODUCT_PARTITION_REPORT. We had previously implemented the >> SHOPPING_PERFORMANCE_REPORT without too much trouble. In looking at these >> two report definitions, I cannot help but be confused as to what data I'm >> trying to show to our clients. Most of our agency clients are not using >> Google Shopping, and this isn't something they are really clamoring for. >> >> In SHOPPING_PERFORMANCE_REPORT: >> >> - OfferId -- appears to be a UPC >> - ProductCategory[X] - These make sense >> - ProductType[X] - These make sense >> >> In PRODUCT_PARTION_REPORT: >> >> - Id -- Appears to be a standard keyword ID >> - ParentCriterionId -- Can't actually include this column (see below) >> - ProductGroup -- Can't actually include this column (see below) >> - PartitionType (segment) -- Can't actually include this column (see >> below) >> >> >> For the two above columns, I get an XML error indicating it's an invalid >> column. The report runs fine if I remove them. >> >> >> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >> <reportDownloadError><ApiError><type> >> ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT >> </type><trigger></trigger><fieldPath>PartitionType >> </fieldPath></ApiError></reportDownloadError> >> >> >> So the PRODUCT_PARTITION_REPORT isn't terribly useful right now. It just >> shows an ID and the relevant metrics. >> >> My root question is what am I trying to communicate with these two >> reports? The SHOPPING_PERFORMANCE_REPORT makes sense, but the >> PRODUCT_PARTITION_REPORT less so. And what should I call these in our UI? >> They are both "Shopping" related, so I'm guessing "Offers" for >> SHOPPING_PERFORMANCE_REPORT and "Products" for PRODUCT_PARTITION_REPORT >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/52dbd80f-52f3-47f8-a83b-4c8e789ea02f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
