Hi Ewan, I think the behavior you saw was due to a transition period, because all the fields you mentioned are now officially available in the KEYWORDS_PERFORMANCE_REPORT as returned by the getReportFields() method. Let us know if you see other anomalies though.
Best, - Eric On Sep 2, 1:09 pm, "okiebug1...@gmail.com" <okiebug1...@gmail.com> wrote: > Thanks much for this info Ewan, this will speed up my report > processing in a big way. The mandate to retrieve the names of the > keywords' Campaign and AdGroup via resolving the AdGroupID slows down > the report run considerably. > > I'm now more hopeful we will soon have the ability to select multiple > days and a daily aggregation. > > David > > On Sep 2, 7:07 am, ewan <e...@ppcbullet.com> wrote: > > > > > Hi Eric, > > > I've noticed that some of these fields are in fact available even > > though they don't appear in the list returned from the Report > > Definition Service. For example, it is possible to add a "CampaignId" > > and "CampaignName" field to the Keyword Performance Report and the > > correct results are returned. > > > I've also noticed that some other fields don't actually return an > > error when they aren't officially available. They just return no > > data. For example, I can use "AdGroupStatus" in the keyword report > > but don't get anything back. I would assume that this field is quite > > important as it's really needed for filtering because the status > > doesn't cascade down and the report ends up with a ton of keywords for > > Ad Groups that aren't actually active. > > > Does this mean that new fields are on the way that just aren't > > documented yet? > > > Thanks, > > > Ewan > > > On Aug 21, 6:56 am, AdWords API Advisor <adwordsapiadvi...@google.com> > > wrote: > > > > Hi David, > > > > I will take your concerns to the appropriate teams within Google. No > > > sunset date has been announced for the v13 ReportService yet, and when > > > it is announced customers will have at least 4-6 months to migrate > > > their applications. > > > > Best, > > > - Eric > > > > On Aug 20, 8:25 am, "okiebug1...@gmail.com" <okiebug1...@gmail.com> > > > wrote: > > > > > Hello Eric, > > > > > I am shocked to hear this undocumented requirement for what should be > > > > a standard performance report, Keyword performance in our case. The > > > > mandate to consume multiple methods just to translate report field's > > > > ids is a tough pill to swallow. Please let the team know this is > > > > adding hours to the migration and causing additional web service > > > > method consumption, not to mention supporting data base files to > > > > handle these lookups. All this additional work could be eliminated > > > > via the simple addition of the fields that define an AdWords campaign, > > > > rather than their ID's in the reports. > > > > > The date issue is unfortunate, since I like to run an EOM procedure to > > > > clear my data warehouse and then recreate via a performance report for > > > > the month, in order to get latent conversions. I can then show your > > > > customers the value or ROI in a lower cost per conversion, which > > > > translates to higher budgets and a greater spend. This would now > > > > require, yet again, multiple report method consumption. > > > > > I've migrated our in-house apps going back to Google's V5 and have > > > > always looked forward to the migration for added functionality and > > > > knowing the Google team was moving the bar forward with each > > > > migration. Now this has my head spinning trying to understand how a > > > > simple report, readily available w/n the engines portal for all to run > > > > interactively, could be translated with in the API to multiple web > > > > services method's consumption and additional data base tables just to > > > > resolve the basic elements of an AdWords campaign: Campaign Name, > > > > which isn't even returned in the Keyword report, AdGroup, Keyword and > > > > date. Please say it doesn't have to be this way. > > > > > How can you make my argument known and get this rectified w/o > > > > interruption in services? Has there been a drop dead date released > > > > for V13, or better yet has the request for functionality for V201003 > > > > been closed. Do I need to get our account rep involved at this time, > > > > in order to further support our push-back against this release? > > > > > TGIF, > > > > David > > > > > On Aug 19, 3:50 pm, AdWords API Advisor <adwordsapiadvi...@google.com> > > > > wrote: > > > > > > Hi David, > > > > > > The v201003 ReportDefinitions are not backward compatible with v13 > > > > > DefinedReportJobs, and the field names may be different. > > > > > > The v201003 reports currently don't support any aggregation or > > > > > segmentation, which is to say you can't break out the results by day, > > > > > week, etc. Instead the values will be calculated for the entire span > > > > > of the report, much like the Summary aggregationType in v13. For this > > > > > reason there is no date field. We plan to add segmentation in a later > > > > > version of the API, but at this time I don't have any estimates for > > > > > when it will be available. > > > > > > The v201003 reports only contain the ID of the direct parent entity > > > > > and not the fields of the parent entities. For instance, you can not > > > > > obtain campaign or ad group information in an ad report, only the ad > > > > > group ID. To get this information you will need to run separate > > > > > campaign and ad group reports. Since report generation is very fast, > > > > > and report definitions can be reused with sliding date ranges, it > > > > > shouldn't be too much work to request this extra data. > > > > > > We are very interested in learning more about how users are finding > > > > > the new v201003 reporting system, so please continue to let us know > > > > > your feedback. > > > > > > Best, > > > > > - Eric Koleda, AdWords API Team > > > > > > On Aug 19, 2:23 pm, "okiebug1...@gmail.com" <okiebug1...@gmail.com> > > > > > wrote: > > > > > > > I have found and fixed issues with selectors date formatting that > > > > > > caused first error. > > > > > > > B E F O R E: > > > > > > <dateRange> > > > > > > <min>08/14/2010</min> > > > > > > <max>08/14/2010</max> > > > > > > </dateRange> > > > > > > > A F T E R: > > > > > > <dateRange> > > > > > > <min>20100814</min> > > > > > > <max>20100814</max> > > > > > > </dateRange> > > > > > > > And now I am surprised to find that the existing V13 columns or > > > > > > fields > > > > > > in a KEYWORDS_PERFORMANCE_REPORT are not supported or carried > > > > > > forward, > > > > > > so we have completely lost backward compatibility. As I mentioned, > > > > > > this is unexpected, since I thought I had read existing report > > > > > > fields > > > > > > would be supported. > > > > > > > My next question, is how am I going to run a Keyword report for an > > > > > > account and obtain Date|Campaign|AdGroup|Keyword and metrics ie. > > > > > > impressions, clicks, cost, conversions? > > > > > > > The getReportFields yields: > > > > > > > Available fields for KEYWORDS_PERFORMANCE_REPORT: > > > > > > AdGroupId(Long) > > > > > > AverageCpc(Money) > > > > > > AverageCpm(Money) > > > > > > AveragePosition(Double) > > > > > > BottomPosition(int) > > > > > > Clicks(Long) > > > > > > ConversionRate(Double) > > > > > > ConversionRateManyPerClick(Double) > > > > > > Conversions(Long) > > > > > > ConversionsManyPerClick(Long) > > > > > > Cost(Money) > > > > > > CostPerConversion(Money) > > > > > > CostPerConversionManyPerClick(Money) > > > > > > Ctr(Double) > > > > > > DestinationUrl(String) > > > > > > FirstPageCpc(Bid) > > > > > > Id(Long) > > > > > > Impressions(Long) > > > > > > IsNegative(Criterion) > > > > > > KeywordMatchType(KeywordMatchType) > > > > > > KeywordText(String) > > > > > > MaxCpm(Bid) > > > > > > PlacementUrl(String) > > > > > > PreferredPosition(int) > > > > > > PrimaryDisplayStatus(AdGroupCriterionPrimaryDisplayStatus) > > > > > > ProxyMaxCpc(Bid) > > > > > > QualityScore(Integer) > > > > > > Status(UserStatus) > > > > > > > If this is the correct list of eligible fields for the report, I > > > > > > have > > > > > > lost my date as well as Campaign, AdGroup. This cannot be correct, > > > > > > for how can I run over a date range and get daily breakout, without > > > > > > multiple reports? > > > > > > > Please let me know how to keep this simple and run a report over a > > > > > > date range to obtain metrics by Date|Campaign|AdGroup|Keyword. > > > > > > > Thanks in advance for any suggestions. > > > > > > > On Aug 19, 10:45 am, "okiebug1...@gmail.com" <okiebug1...@gmail.com> > > > > > > wrote: > > > > > > > > I've attempted to build a report definition, via following the > > > > > > > July 13 > > > > > > > article on the AdWordsAPI blog. > > > > > > > > I'm a .NET developer using the wsdl.exe and then performing the > > > > > > > clean > > > > > > > up of the generated stub class as outlined in the NoClientLibrary > > > > > > > wiki > > > > > > > article, which was a savior for my initial migration of my > > > > > > > Campaign > > > > > > > Manager apps. > > > > > > > > My stub class was generated via: "C:\Program Files\Microsoft > > > > > > > Visual > > > > > > > Studio 8\SDK\v2.0\Bin\wsdl.exe" /l:vb /o:GoogleReportService.vb / > > > > > > > sharetypeshttps://adwords.google.com/api/adwords/cm/v201003/ReportDefinitionSer... > > > > > > > > Here is my first pass for generating a keyword performance report: > > > > > > > > POST /api/adwords/cm/v201003/ReportDefinitionService HTTP/1.1 > > > > > > > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services > > > > > > > Client > > > > > > > Protocol 2.0.50727.3615) > > > > > > > VsDebuggerCausalityData: > > > > > > > > uIDPo9+2a6wTfzFDkqG5NirrhIQAAAAAFpchaoptL0imFxrUAO > > > > > > > +QrK4XNxUPmCNHrECENuBAxbwACAAA > > > > > > > Content-Type: text/xml; charset=utf-8 > > > > > > > SOAPAction: "" > > > > > > > Host: adwords.google.com > > > > > > > Content-Length: 1530 > > > > > > > Expect: 100-continue > > > > > > > > <?xml version="1.0" encoding="utf-8"?> > > > > > > > <soap:Envelope > > > > > > > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; > > > > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > > > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > > > > > > <soap:Header> > > > > > > > <RequestHeader xmlns="https://adwords.google.com/api/adwords/cm/ > > > > > > > v201003"> > > > > > > > <authToken>******</authToken> > > ... > > read more » -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
