Hi Fraser Cain,

Yeah I know what you mean, but we were disabled too - we do not have
any
kind of this keyword tool, we only use it to make nice reports for our
clients - who we advertise on Adwords.

How did you apply for provisional access? I just dont get the answer
from
API team. And I hate that we are in the same line, as advertisers who
just
started - I know back then I didn`t need it so much, as you need it
once
your customers use it.

Strange, hard to do business like this,

Thanks for replay,

On Sep 22, 1:12 am, Fraser  Cain <[email protected]> wrote:
> We've been given provisional access to the API as well - we have 7
> days to complete the application and fulfill their requirements. We
> can explain our current functionality and our development plans, but
> there's no way we can fully hook into all the required parts of the
> API within a couple of days. It seems kind of hopeless at this point,
> but we'll give it our best shot.
>
> If you want to see what we're doing, our application is located 
> athttps://www.keywordstrategy.org
>
> We've also researched all the other data providers out there, so if
> anyone wants my recommendations, just drop me an email.
>
> My overall belief is that Adwords doesn't want us to pay for data,
> they want us to bring them paying customers who will buy search ads.
> So we're going to pivot our offerings to emphasize that ability.
> Hopefully we'll demonstrate enough value that they'll keep us around.
>
> On Sep 19, 7:44 am, keesjan <[email protected]> wrote:
>
>
>
>
>
>
>
> > Thats great news for you. I also read 
> > onhttp://searchengineland.com/google-angers-adwords-api-developers-by-r...
> > that one client was TopTenWholesale was given more time:
>
> > "So far, at least one API developer — Jason Prescott of TopTenWholesale.com
> > and Manufacturer.com, who I quoted above — has been granted “provisional”
> > access to the API again, after writing an e-mail and contacting a Google
> > representative. Prescott’s company will have to provide all of the above
> > information before September 23, and presumably it will have to meet
> > Google’s requirements, before the access decision becomes final."
>
> > Can you say your app is meeting the full RDF  
> > http://code.google.com/apis/adwords/docs/requirements.htmlandspecailly
> > -(what I think a lot of apps in this group fail for now -
>
> > "If an AdWords API Client provides any functionality related to
> > TargetingIdeaService, TrafficEstimatorService, or BulkOpportunityService, it
> > must fully implement the required Creation Functionality, Management
> > Functionality and Reporting Functionality marked "Required" in the table
> > below."
>
> > Do you share your apps URL here? This will help to get the fog away about
> > what Google wants

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

Reply via email to