Ok, so it seems the real issue I'm running into into is that I do not have a quick way to cross reference the Criterion IDs through the Reporting API to its human-readable value. It isn't provided into the CSV file, so I would have to look the list and then map them into the user's report. That seems like a missed detail, as the other reports I'm using are a bit more user-friendly (meaning, I could generate a CSV file and it potentially be ready to hand off to the end advertiser).
I'll chase down that road. - Stephen On Friday, February 6, 2015 at 8:55:10 AM UTC-6, Josh Radcliff (AdWords API Team) wrote: > > Hi Stephen, > > The fields you labeled as *Product ID *and *Parent ID* correspond to the > *id* and *parentCriterionId* attributes of > AdGroupCriterionService.ProductPartition > <https://developers.google.com/adwords/api/docs/reference/v201409/AdGroupCriterionService.ProductPartition>, > > respectively. > > The *ProductPartition*s in your example are a bit of a special case, > because they all have as their caseValue > <https://developers.google.com/adwords/api/docs/reference/v201409/AdGroupCriterionService.ProductPartition#caseValue> > instances > of the *ProductDimension* subclass of ProductOfferId > <https://developers.google.com/adwords/api/docs/reference/v201409/AdGroupCriterionService.ProductOfferId>. > > The only meaningful attribute of that dimension type is its value > <https://developers.google.com/adwords/api/docs/reference/v201409/AdGroupCriterionService.ProductOfferId#value>, > > which is simply the Offer ID of the corresponding product in Merchant > Center. The AdWords API does not have any additional information beyond > that, such as the product description, etc. > > For other types of *ProductDimensions*, such as ProductBrand > <https://developers.google.com/adwords/api/docs/reference/v201409/AdGroupCriterionService.ProductBrand>, > > the value attribute is far more meaningful, e.g., with a *value* of > "Nike" for products where brand = Nike, and those values will appear in the > *ProductGroup* field in reports. > > As far as how you can best show this information to your users and meet > RMF requirements, you can contact our API Compliance Team using this form > <https://services.google.com/fb/forms/apicontact/>, and they may have > some suggestions. They can also clear up any other RMF questions you may > have. > > Hope that helps! > > Cheers, > Josh, AdWords API Team > > On Thursday, February 5, 2015 at 3:24:11 PM UTC-5, Stephen Yeargin wrote: >> >> Image was dropped. >> >> http://cl.ly/image/222B0G2h2c2D >> >> >> On Thursday, February 5, 2015 at 12:33:06 PM UTC-6, 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/2430493b-20be-44b2-9883-c5e1028b3e17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
