6 messages in com.googlegroups.adwords-apiAdWords API Re: updating maxcpc to 0 ...
FromSent OnAttachments
eelco.v98726 Jun 2008 04:50 
AdWords API Advisor26 Jun 2008 08:52 
eelco.v98726 Jun 2008 09:19 
AdWords API Advisor26 Jun 2008 12:33 
eelco.v98727 Jun 2008 02:34 
AdWords API Advisor27 Jun 2008 07:55 
Subject:AdWords API Re: updating maxcpc to 0 to use adgroup's maxcpcc?
From:AdWords API Advisor (adwo@google.com)
Date:06/27/2008 07:55:24 AM
List:com.googlegroups.adwords-api

No worries. Glad it was something simple.

Cheers, -Jeff Posnick, AdWords API Team

On Jun 27, 5:34 am, "eelco.v987" <eelc@gmail.com> wrote:

Jeff, Thanks for your input, I have tried the same on the production environment, which didn't work either.

However, I found the problem, it seems the CPC check we built long ago wasn't working correctly when set to 0 . Sorry for not thinking about this earlier and thanks very much for your assistance. Next time, I'll wait a day before asking stupid questions :)

Cheers, Eelco

On 26 jun, 21:34, AdWords API Advisor <adwo@google.com> wrote:

Okay, yeah, that's the response you'd get assuming the update went through. I'd be interested to hear if you could reproduce this in the production environment, which is a little bit easier to troubleshoot (e.g. you can doublecheck things in the AdWords web interface in addition to relying on the AdWords API).

Cheers, -Jeff Posnick, AdWords API Team

On Jun 26, 12:20 pm, "eelco.v987" <eelc@gmail.com> wrote:

Hi Jeff, I keep appauding your fast responses, anyway:

The update with maxcpc set at 0, gives the below mentioned response, which is the basically the same response as a working update for say 0.10. I hope this may be of any help to you.

<?xml version="1.0" ?> - <soapenvEnvelope xmlnssoapenv="http://schemas.xmlsoap.org/soap/ envelope/" xmlnsxsd="http://www.w3.org/2001/XMLSchema" xmlnsxsi="http://www.w3.org/2001/XMLSchema-instance"> - <soapenvHeader> <responseTime xmlns="https://adwords.google.com/api/adwords/v12" soapenvactor="http://schemas.xmlsoap.org/soap/actor/next" soapenvmustUnderstand="0">83</responseTime> <operations xmlns="https://adwords.google.com/api/adwords/v12" soapenvactor="http://schemas.xmlsoap.org/soap/actor/next" soapenvmustUnderstand="0">6</operations> <units xmlns="https://adwords.google.com/api/adwords/v12" soapenvactor="http://schemas.xmlsoap.org/soap/actor/next" soapenvmustUnderstand="0">6</units> <requestId xmlns="https://adwords.google.com/api/adwords/v12" soapenvactor="http://schemas.xmlsoap.org/soap/actor/next" soapenvmustUnderstand="0">81b18107a4e2ba3cc55bea0fb1731a77</ requestId> </soapenvHeader> - <soapenvBody> <updateCriteriaResponse xmlns="" /> </soapenvBody> </soapenvEnvelope>

Cheers, Eelco

On 26 jun, 17:53, AdWords API Advisor <adwo@google.com> wrote:

Hello Eelco,

The return value for maxCpc in the scenario you describe should be 0, yes. I can't reproduce different behavior when making some calls to the production environment in a test ad group. Are you sure your initial attempt to change the maxCpc for the keyword to 0 went through properly?

Cheers, -Jeff Posnick, AdWords API Team

On Jun 26, 7:50 am, "eelco.v987" <eelc@gmail.com> wrote:

The Developer's guide notes the following about Criteria, but I'm mostly interested in updateCriteria:

Optional field for Keyword objects only: maxCpc: The new CPC for this keyword. If zero is specified, the CPC for this keyword will be cleared, so the default CPC for the adgroup will be used instead.

I tried this on my sandbox, to see what happens, though they seem to update corectly (haven't received any errors), when using getCriteria afterward it still shows e.g. 11cents, though it should've been set to 0 (or adgroup cpc value?).

Hoewever, when making a new criteria with maxcpc set to 0 or left out , it just shows 0.

Am I missing something, or is this working fine, but just not showing anything? Many thanks in advance.

Cheers, Eelco- Tekst uit oorspronkelijk bericht niet weergeven -

- Tekst uit oorspronkelijk bericht weergeven -- Tekst uit oorspronkelijk bericht
niet weergeven -

- Tekst uit oorspronkelijk bericht weergeven -