I've found out some more about the low values for exact keyword match on local search volumes.
Update: The search volumes in STATS requests differ from the search volumes in IDEAS requests. This explains why we experience different values in the keyword tools. Is this an old issue that has resurfaced? A fix for clients would be to exploit STATS requests, which is how it had to be done quite some time ago. However, to ensure values for all keywords there is an overhead in API-units. Are you looking into this discrepancy between the two data sources? Best regards -- Martin On Feb 8, 10:44 am, Martin <[email protected]> wrote: > We have noticed a a huge drop in local (sv_SE) exact match targeting > for most (or all) keywords we are interested in. > > The search volumes in the API also differ largely from the values in > the Keyword Tool. > > Is there being work done to correct this issue? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [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
