Hello all,
Any update for SEARCH_VOLUME Data mismatch for Targetting Idea Service?
I am able to add multiple keywords.
So now only SEARCH_VOLUME is my biggest issue.
*
*
*Thanks,
*
On Wednesday, October 24, 2012 10:01:30 PM UTC+5:30, Chirag wrote:
>
> Yes, I am also facing same issue while adding more than one Query string
> to get stats/idea of keywords.
> $keyword[] = 'mars cruise';
> $keyword[] = 'cheap cruise';
> $keyword[] = 'cruise';
> Or
> $keyword[] = new Keyword('mars cruise', 'EXACT');
> $keyword[] = new Keyword('cheap cruise', 'EXACT');
> $keyword[] = new Keyword('cruise', 'EXACT');
>
> Also there is issue with SEARCH_VOLUME. It is diffrent SEARCH_VOLUME for
> global searches.
>
> Thanks,
> Chirag
>
> On Wednesday, October 24, 2012 12:03:33 PM UTC+5:30, veseo wrote:
>>
>> Any news? If this is a known problem, please postpone the sunset of
>> 201109 until it's sorted out, if not - please give us a hand to sort out
>> what we're doing wrong. As the things stand, starting the next Monday, we
>> will be presenting our clients with totally fake and seemingly random data,
>> even if we've been waiting for two weeks now for an answer (I sent an email
>> to the support team before creating that thread here). I'm sorry to say it,
>> but that's an example of a really poor (if not lacking at all) support job!
>>
>> On Tuesday, October 23, 2012 2:56:18 PM UTC+3, veseo wrote:
>>>
>>> Hi,
>>>
>>> while implementing the new versions of both TargetingIdeaService and
>>> TrafficEstimatorService, we ran into some problems, that lead to a
>>> (sometimes too big) discrepancy between the API results and its
>>> corresponding tool.
>>>
>>> 1. TargetingIdeaService vs. http://preview.tinyurl.com/adwtool:
>>>
>>> According to the migration guide:
>>>
>>> *SEARCH_VOLUME is equivalent to AVERAGE_TARGETED_MONTHLY_SEARCHES if
>>> language and/or location is specified. SEARCH_VOLUME is equivalent to
>>> GLOBAL_MONTHLY_SEARCHES if language and/or location is not specified.*
>>> *
>>> *
>>> But, either I'm doing something wrong (not likely, as the API usually
>>> crashes when passed invalid structure) or the results for targeted search
>>> volume between the API and the tool are completely different. Here's an
>>> example:
>>>
>>> *Keyword*: [katze]
>>> *Targeting*: Location: Austria; Language: German
>>> *API*: SEARCH_VOLUME 18100
>>> *Tool*: 5400
>>>
>>> I'm attaching the request and response xmls.
>>>
>>> 2. TrafficEstimatorService vs http://preview.tinyurl.com/trafftool
>>>
>>> The problem here seems to persist from earlier, so it's not v201206
>>> specific. We tried with the following data:
>>>
>>> *Keyword*: [katze]
>>> *Targeting*: Location: Austria; Language: German; Search Network:
>>> Google Search
>>> *Max CPC*: €2.00
>>> *Tool Average CPC*: €1.94
>>> *API results*: min CPC: €0.42, max CPC: €0.51 - as you can see, totally
>>> different from the Tool results.
>>>
>>> I'm also attaching the XML request and response files for reference.
>>>
>>> Can someone please shed some light as to why both TargetingIdea and
>>> TrafficEstimator services provide incorrect data?
>>>
>>
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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
