Hi, We released a fix for this issue recently, and I'm now seeing consistent results with and without the *Query* field included. Please check your report's output and post back to this thread if you still see any issues.
Cheers, Josh, AdWords API Team On Monday, March 10, 2014 4:39:14 PM UTC-4, Josh Radcliff (AdWords API Team) wrote: > > Hi Jonathan, > > Could you send over the report definitions you are using when you see > these discrepancies? Per the forum rules > <https://groups.google.com/forum/#!topic/adwords-api/lUQpWowB44k>, please > avoid posting any sensitive information about your account. If you'd > prefer, you can send the information only to me by clicking "Reply to > Author". > > My suspicion is that the discrepancies between the two reports is related > to single vs. multiple attribution > <https://devsite.googleplex.com/adwords/api/docs/guides/reporting-concepts#single>, > > but having the exact report definitions and AdWords account IDs you're > using will help me confirm this. > > Thanks, > Josh, AdWords API Team > > On Tuesday, February 25, 2014 4:08:59 AM UTC-5, Takeshi Hagikura (AdWords > API Team) wrote: >> >> Hi Jonathan, >> >> Apologies for the late reply. >> >> I'm looking into it each of those. >> I'll update the thread once I've got the answer. >> >> Best, >> - Takeshi, AdWords API Team >> >> On Saturday, February 15, 2014 3:11:57 AM UTC+9, jsob...@tripadvisor.com >> wrote: >>> >>> Hi Takeshi, >>> >>> Thanks for confirming that the description for "Query" is wrong. Can you >>> please let me know if it is possible to include the longer query strings in >>> the report and if so, how? >>> >>> I see that in the reports API the description has been updated to: >>> >>> "We only show the first 128 char bytes of a query; so two rows with >>> seemingly identical query strings just indicates that there were some >>> differences past the 128th byte." >>> >>> When I was running the report, I observed that the number of rows I got >>> back in the report results varied drastically if I included or excluded the >>> "Query" column. Can you possibly update the description to explain why that >>> might be the case? >>> >>> Also, can you help with explaining the other discrepancies in total >>> clicks and impressions that I am seeing between the two reports? >>> >>> Thanks! >>> >>> Jonathan >>> >>> On Thursday, February 6, 2014 4:44:49 AM UTC-5, Takeshi Hagikura >>> (AdWords API Team) wrote: >>>> >>>> Hi Jonathan, >>>> >>>> The description for "Query" seems to be wrong in Keywordless Query >>>> Report. >>>> >>>> Originally the description was for "Search Query Performance Report" >>>> not for the Keywordless Query Report. >>>> It seems to be there by mistake. >>>> We'll fix this. >>>> >>>> Best, >>>> - Takeshi, AdWords API Team >>>> >>>> On Friday, January 31, 2014 6:41:47 AM UTC+9, jsob...@tripadvisor.com >>>> wrote: >>>>> >>>>> Hello Google AdWords API Support, >>>>> >>>>> I am trying to use the AdWords API to get the Keywordless Query Report >>>>> here: >>>>> >>>>> >>>>> https://developers.google.com/adwords/api/docs/appendix/reports#keywordless-query >>>>> >>>>> I am trying to verify that the data I am pulling is correct by >>>>> comparing total clicks and impressions from the "Keywordless Query >>>>> Report" >>>>> to the "Ad Performance Report" in the AdWords UI filtered for AdType DSA. >>>>> What I am seeing is that in the Keywordless Query Report total clicks are >>>>> close but less than for the Ad Performance Report, and total impressions >>>>> are drastically lower for the Keywordless Query Report than the Ad >>>>> performance Report. >>>>> >>>>> I am pulling the following columns for the Keywordless Query Report: >>>>> >>>>> AverageCPC >>>>> Impressions >>>>> Clicks >>>>> Cost >>>>> Ctr >>>>> CriterionId >>>>> AdGroupId >>>>> CampaignId >>>>> Title >>>>> Domain >>>>> Url >>>>> >>>>> I notice that if I also pull the "Query" column then a large number of >>>>> rows do not get returned and there is a much bigger discrepancy in total >>>>> clicks and impressions. I am guessing that this is because the note for >>>>> the >>>>> Query column in the report description page says: >>>>> >>>>> "If the string for this attribute is longer than 128 char bytes, the >>>>> returned >>>>> result will NOT be a single aggregated row." >>>>> >>>>> This message seems misleading. If the query is greater than 128 >>>>> characters, is it impossible to see what the query was? If not, how do I >>>>> see what the query was? >>>>> >>>>> Why would I be seeing a discrepancy in these two reports? Is this >>>>> expected? >>>>> >>>>> Thanks in advance for your assistance. >>>>> >>>>> Jonathan >>>>> >>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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. For more options, visit https://groups.google.com/d/optout.
