In an effort to provide more consistent and accurate keyword data to our developers and advertisers, we will be changing some of the fields within the KeywordEstimate object on Thursday, November 3rd.
We will add the following field to the KeywordEstimate object:
· clicksPerDay - (float) The estimated number of clicks generated per day for a keyword in a given ad group
Similarly, we will remove the following fields from the KeywordEstimate object:
· impressions - The estimated number of impressions for a given keyword · ctr - The estimated click-through-rate for a given keyword. · notShownPerDay - The estimated number of times that the ad would not be shown, despite a keyword match.
These changes will take effect on the afternoon of Thursday, November 3rd (Pacific time zone). At that time, we will update the TrafficEstimatorService WSDL which may disrupt the operation of your programs. Therefore, we have posted a temporary copy of the "new" TrafficEstimatorService WSDL at http://www.google.com/apis/adwords/developer/wsdl_preview.xml so you can begin making the necessary adjustments now (This temporary copy will be removed on November 4, 2005, after the normal WSDL location is updated).
Given that the placement of an ad, the CTR, and the number of clicks per day for the ad depends on many things (like how good the text is, how well targeted it is..) it seems that removing the only hard fact, impressions, will make the tool less usefully and not more. Though I guess if we can get numbers on what Google assumes will be the CTR for a certain position, we can get back the impressions value. That way we can calculate the number of clicks with our own CTR value and get much more accurate results.
So in short, can you at least give us a hint what CTR the tool thinks will be on say position 1,2,and 3?
I believe this may be just the first phase of a new
"less is more" concept.
I expect subsequent versions will alternately snip out
or merge previously inaccurate fields, until finally
(AdWords 1.0) the TrafficEstimatorService will be void
of inaccuracy by providing no information whatsoever.
> Given that the placement of an ad, the CTR, and the
> number of clicks
> per day for the ad depends on many things (like how
> good the text is,
> how well targeted it is..) it seems that removing
> the only hard fact,
> impressions, will make the tool less usefully and
> not more.
> Though I guess if we can get numbers on what Google
> assumes will be the
> CTR for a certain position, we can get back the
> impressions value. That
> way we can calculate the number of clicks with our
> own CTR value and
> get much more accurate results.
> So in short, can you at least give us a hint what
> CTR the tool thinks
> will be on say position 1,2,and 3?
> Thanks in advance
__________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
> it seems that removing the only hard fact, > impressions, will make the tool less usefully and not more.
That was my thought as well, impressions is the only figure that can be accurate. Perhaps the reason for removing it is that it gives us too much information (how many searches there are on Google for a specific phrase).
Well done, Google. I just want to release my first Adwords program - partly based on the ctr value. I work about two month for it. Why we should develop programs for Google, if Google changes the API every two month (see also KeywordService)?
> Well done, Google. I just want to release my first Adwords program -
> partly based on the ctr value. I work about two month for it. Why we
> should develop programs for Google, if Google changes the API every two
> month (see also KeywordService)?
> Thank you, Google :-(
While I can understand that you're upset about your program it should be noted that the API is fairly clearly marked as a *beta* release and as such you should have taken steps to decouple your program from the backend API.
I'm also quite disappointed to hear this. I depended on all the data being removed from the API to offer estimated keyword search volume data and other extended stats to my customers. Without this info my tools are not as useful.
Unless I'm missing something, I really don't see the improvement in the TrafficEstimatorService after the change. It looks more like a downgrade. Can you please explain your full reasoning for this change?
I think it would help us more if you add the new clicksPerDay field and keep the rest as well. That way we can choose what to use.
> Given that the placement of an ad, the CTR, and the number of clicks
> per day for the ad depends on many things (like how good the text is,
> how well targeted it is..) it seems that removing the only hard fact,
> impressions, will make the tool less usefully and not more.
> Though I guess if we can get numbers on what Google assumes will be the
> CTR for a certain position, we can get back the impressions value. That
> way we can calculate the number of clicks with our own CTR value and
> get much more accurate results.
> So in short, can you at least give us a hint what CTR the tool thinks
> will be on say position 1,2,and 3?
Sorry but no, we do not plan to disclose that data through the API.
" The Bellman perceived that their spirits were low,
And repeated in musical tone
Some jokes he had kept for a season of woe -
But the crew would do nothing but groan."
I'll spare you the jokes and would refer to Coleridge's "Rime of the Ancient
Mariner"
"Facile credo, plures esse Naturas invisibiles quam visibiles in rerum
universitate. Sed horum omnium familiam quis nobis enarrabit ? et gradus et
cognationes et discrimina et singulorum munera ? Quid agunt ? quae loca
habitant ?" - T. Burnet, *Archaeol. Phil.*, p. 68 (slightly edited by
Coleridge).
Translation:
"I can easily believe, that there are more invisible than visible Beings in
the universe. But who shall describe for us their families? and their ranks
and relationships and distinguishing features and functions? What they do?
where they live?"
P@
On 11/1/05, Ben Michelson <ber...@yahoo.com> wrote:
> I believe this may be just the first phase of a new
> "less is more" concept.
> I expect subsequent versions will alternately snip out
> or merge previously inaccurate fields, until finally
> (AdWords 1.0) the TrafficEstimatorService will be void
> of inaccuracy by providing no information whatsoever.
> > Given that the placement of an ad, the CTR, and the
> > number of clicks
> > per day for the ad depends on many things (like how
> > good the text is,
> > how well targeted it is..) it seems that removing
> > the only hard fact,
> > impressions, will make the tool less usefully and
> > not more.
> > Though I guess if we can get numbers on what Google
> > assumes will be the
> > CTR for a certain position, we can get back the
> > impressions value. That
> > way we can calculate the number of clicks with our
> > own CTR value and
> > get much more accurate results.
> > So in short, can you at least give us a hint what
> > CTR the tool thinks
> > will be on say position 1,2,and 3?
> > Thanks in advance
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005
> http://mail.yahoo.com
