AdWords API how do I get the auth token

2010-03-26 Thread molaMolar
Hi all, in the new version of the AdWords API, how do I get the auth
token?.
I make the call is:

$namespace = 'https://adwords.google.com/api/adwords/cm/v200906';

# Define SOAP
$auth = new AuthToken($email, $password, $account_type, $service);
$headers =
  'RequestHeader xmlns=' . $namespace . '' .
  'authToken' . $auth-get_auth_token() . '/authToken' .
  'clientEmail' . $client_email . '/clientEmail' .
  'userAgent' . $user_agent . '/userAgent' .
  'developerToken' . $developer_token . '/developerToken' .
  'applicationToken' . $application_token . '/applicationToken' .
  '/RequestHeader';


I put in  fields  $account_type and $service?

thanks and sorry for my english.

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: edit ad extension error

2010-03-26 Thread freesystems.t...@gmail.com

hi

i have one ad which is already overridden by ad extension. so now i
want to override with different local business ad extension.

request is

Array
(
[0] = AdExtensionOverrideOperation Object
(
[operand] = AdExtensionOverride Object
(
[adId] = 4609056651
[adExtension] = AdExtension Object
(
[id] = 77669151
[AdExtensionType] =
[_parameterMap:private] = Array
(
[AdExtension.Type] =
AdExtensionType
)

)

[overrideInfo] =
[status] =
[approvalStatus] =
[stats] =
)

[operator] = ADD
[OperationType] =
[_parameterMap:private] = Array
(
[Operation.Type] = OperationType
)

)
)

response xml is

[faultstring] =
[AdExtensionOverrideError.AD_ALREADY_HAS_ADEXTENSION_OVERRIDE @
operations[0].operand]
[faultcode] = soap:Server
[detail] = stdClass Object
(
[ApiExceptionFault] = stdClass Object
(
[message] =
[AdExtensionOverrideError.AD_ALREADY_HAS_ADEXTENSION_OVERRIDE @
operations[0].operand]
[ApplicationException.Type] = ApiException
[errors] = SoapVar Object
(
[enc_type] = 0
[enc_value] = AdExtensionOverrideError
Object
(
[reason] =
AD_ALREADY_HAS_ADEXTENSION_OVERRIDE
[fieldPath] =
operations[0].operand
[trigger] =
[ApiErrorType] =
AdExtensionOverrideError
[_parameterMap:private] = Array
(
[ApiError.Type] =
ApiErrorType
)

)

[enc_stype] = AdExtensionOverrideError
[enc_ns] = 
https://adwords.google.com/api/adwords/cm/v200909
)

)

)

)



On Mar 26, 7:00 am, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
 Hi,

 Can you post the SOAP XML request and response that demonstrates this
 behavior?

 Best,
 - Eric Koleda, AdWords API Team

 On Mar 24, 5:42 am, freesystems.t...@gmail.com adwo...@kutenda.com
 wrote:



  Hi,

  when i editing the ad extension override then i getting the error
  AD_ALREADY_HAS_ADEXTENSION_OVERRIDE.

  so how to override the ad-extension of ad which have already
  overridden ad extension.

  reply ASAP.

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: how do I get the auth token

2010-03-26 Thread molaMolar
sorry, I've found.

the problem is that I do not get the auth token,
How do I get the auth token?

On 26 mar, 11:07, molaMolar na...@actualweb.es wrote:
 Hi all, in the new version of the AdWords API, how do I get the auth
 token?.
 I make the call is:

 $namespace = 'https://adwords.google.com/api/adwords/cm/v200906';

 # Define SOAP
 $auth = new AuthToken($email, $password, $account_type, $service);
 $headers =
   'RequestHeader xmlns=' . $namespace . '' .
   'authToken' . $auth-get_auth_token() . '/authToken' .
   'clientEmail' . $client_email . '/clientEmail' .
   'userAgent' . $user_agent . '/userAgent' .
   'developerToken' . $developer_token . '/developerToken' .
   'applicationToken' . $application_token . '/applicationToken' .
   '/RequestHeader';

 I put in  fields  $account_type and $service?

 thanks and sorry for my english.

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: Same AdParam for different Criteria in same AdGroup: AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES

2010-03-26 Thread AdWords API Advisor
Hi Kemal,

I took another look at the criterionIds, and I can see the problem.
You passed in different values, but they ended up as 2147483647 in the
request.  This is a known issue with some versions of PHP, where
numbers too large for integer values are truncated to 2147483647.
More information is available here:

  http://code.google.com/p/google-api-adwords-php/issues/detail?id=5

The solution is to cast your numbers as floats before setting them on
the objects.

Best,
- Eric

On Mar 26, 9:49 am, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
 Hi Kemal,

 I looked at the logs for that request, and the errors are accurate.
 There are multiple operation that have the same adGroupId,
 criertionId, and paramIndex in that request.  Please ensure that there
 are no duplicate operations in the request and this error should go
 away.

 Best,
 - Eric Koleda, AdWords API Team

 On Mar 24, 3:45 pm, Kemal dis...@gmail.com wrote:



  Hi,

  The requestId is 09adeafeb0c60d291d19880e8aac3bf1

  Cheers,
  Kemal

  On Mar 24, 9:12 pm, AdWords API Advisor adwordsapiadvi...@google.com
  wrote:

   Hi Kemal,

   What you are trying to accomplish should be allowed.  Can you double
   check that the adGroupId-criterionId-paramIndex combination is unique
   for each operation?  Do you have the SOAP XML logs or requestId from a
   request that demonstrates this behavior?

   Best,
   - Eric Koleda, AdWords API Team

   On Mar 23, 10:19 am, Kemal dis...@gmail.com wrote:

Hello,

I am trying to set the same AdParams (AdParamId's are the same, so are
the values) for different criteria in the same AdGroup, all in one
mutate call. But it throws me a
AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES error.

The documentation states that The same ad param cannot be specified
in multiple operations. Isn't this quite a bit limiting? How are we
supposed to set a bunch of AdParams for an entire AdGroup in one go?
Multiple calls to mutate() for each and every keyword would just kill
the backend. Or do I have to use the BulkMutateJob service, even if I
don't want to?

Or maybe (well, hopefully) I triggered a bug in the API. Any comments?

The data goes like this:
An array of AdParamOperations with 14 elements. Operator is SET. Each
AdParam with the same AdGroupId.
First 7 AdParams set the same paramIndex (1) and the same
insertionText (4) but each with different criterionIds.
Second 7 AdParams set the other paramIndex (2) and the same
insertionText (8 in this case) each with different criterionIds as
well. (Actually the order of criterionIds match the first 7
operations)

The result is an array of AdParamErrors:
[AdParamError.AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES @
operations[2].operand; trigger:'AdParam already defined at index 1',
AdParamError.AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES @
operations[3].operand; trigger:'AdParam already defined at index 1',
AdParamError.AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES @
operations[4].operand; trigger:'AdParam already defined at index 1',
AdParamError.AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES @
operations[5].operand; trigger:'AdParam already defined at index 1',
AdParamError.AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES @
operations[6].operand; trigger:'AdParam already defined at index 1',
AdParamError.AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES @
operations[9].operand; trigger:'AdParam already defined at index 8',
AdParamError.AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES @
operations[10].operand; trigger:'AdParam already defined at index 8',
AdParamError.AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES @
operations[11].operand; trigger:'AdParam already defined at index 8',
AdParamError.AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES @
operations[12].operand; trigger:'AdParam already defined at index 8',
AdParamError.AD_PARAM_CANNOT_BE_SPECIFIED_MULTIPLE_TIMES @
operations[13].operand; trigger:'AdParam already defined at index 8']

Best,
Kemal

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Can i use v2009 api in live mode

2010-03-26 Thread Devon Smith
Hi,

  I have tested all my code with sandbox mode. Now i want to use it
for live environment.
So is it possible ? I also want some reporting samples created in PHP
language. I don't have much idea about
reportService api. so if possible please post a sample report
generation code.

Any help would be highly appreciated.

Thanks
Devon.

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: Passing an Array of Country Language Codes to CountryTarget LanguageTarget

2010-03-26 Thread Devon Smith
Hello,

 Please put the following code.


  $country = array('US','GB');

  $geoTargetList = new GeoTargetList();
  $geoTargetList-campaignId = $campaignId;
  $countryArray = array();
  for($i=0;$icount($country);$i++)
  {
$obj = new CountryTarget(trim($country[$i]));
$countryArray[] = $obj;
  }
  $geoTargetList-targets = $countryArray;

  $geoTargetOperation = new CampaignTargetOperation();
  $geoTargetOperation-operand = $geoTargetList;
  $geoTargetOperation-operator = 'SET';

   $operations = array($geoTargetOperation);

  // Set campaign targets.
  $result = $campaignTargetService-mutate($operations);



This solution will work.

Thanks
David

On Mar 26, 9:59 am, Gek jawaharpra...@gmail.com wrote:
 Any Help ? :(

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Not agreed to latest AdWords Api terms and conditions.

2010-03-26 Thread Ellviz

Hi,


 I am getting this error when I Query

 Fault: 1 Code: soapenv:Server.userException String: Not agreed to
latest AdWords Api terms and conditions.

This is my new Adword api account, My Developer token is approved and
my Billing is also updated on the Billing preference section.

I am using SOAP.

Thanks

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: lastMonthSearchVolume != TARGETED_MONTHLY_SEARCHES

2010-03-26 Thread Andriy Kud
On Mar 26, 1:06 am, rick rick.kra...@gmail.com wrote:
 It doesn't look like you've specified any filters in your example, so
 I'm not
 sure why you're not seeing global and targeted searches being the
 same.
 Maybe it doesn't populate it unless you have at least one language or
 country selector.

Language and country filters I'm using.

v13:
$language = array('en');
$country = array('US');

v200909:
$lang = new LanguageTarget();
$lang-languageCode = en;
$langs = array($lang);
$languageTargetSearchParameter = new
LanguageTargetSearchParameter($langs);

$country = new CountryTarget();
$country-countryCode = 'US';
$countries = array($country);
$countryTargetSearchParameter = new
CountryTargetSearchParameter($countries);

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: AuthenticationError.CUSTOMER_NOT_FOUND

2010-03-26 Thread pollard_pi...@yahoo.co.uk
Hi Eric,

Production.  It works fine on sandbox, it is when we try to connect up
with the live service that we have a problem.

The request ID from the SOAP_xml.log file is
d5cc334945338399089e5638e67ff50b

This is the API being used:
ns2:ApiExceptionFault xmlns=https://adwords.google.com/api/adwords/
cm/v200909 xmlns:ns2=https://adwords.google.com/api/adwords/o/
v200909

Thanks

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: Operator.ADD not supported in CampaignTargetService

2010-03-26 Thread Pete Lavetsky (AdWords API Guru)
I don't know what the official response is going to be, but yea, we
always use Operator.SET for the CampaignTargets

Pete

On Mar 26, 9:13 am, dunia dun...@gmail.com wrote:
 Hi,
 according to the online 
 documentationhttp://code.google.com/intl/it-IT/apis/adwords/v2009/docs/reference/C...
 a list of targets can be added, set or removed, but I tried to add a
 targetList using Operator.ADD and I had the following error:

 OperatorError.OPERATOR_NOT_SUPPORTED @ operations[0]  ...

 I suppose the right way to add a list of targets to a campaign is to
 always use Operator.SET.

 Could anyone confirm this?

 Thank you

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API PolicyViolationKey

2010-03-26 Thread Pete Lavetsky (AdWords API Guru)
Found this thread:

https://groups.google.com/group/adwords-api/browse_thread/thread/2507fe501b3c5655/0274e084c8b13e5e?lnk=gstq=PolicyViolationKey#0274e084c8b13e5e

Does this mean in order to add an exemption request to a keyword, we
have to actually submit the keyword first, get the failed
PolicyViolationKey, and then resubmit the keyword with the added
exemption request?

Pete

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: Internal Server Error from InfoService request

2010-03-26 Thread Anthony - RKG
Eric,

Join the club.  After much pain and suffering getting the Sandbox
InfoService routines working (the clientEmail Request Header either
must not exist or be different from other Serivce requests and not
include 'client+1'), we made the changes live this morning.  No matter
what we send to the InfoService, we get back:

API-fault for InfoService-get: Internal Server Error(500), Fault
occurred while processing.

We are using our own Perl API.  Here is the original request:

[INFO] retrieve-quota-usage: POST 
https://adwords.google.com/api/adwords/info/v200909/InfoService
Content-Type: text/xml SOAPAction: #get ?xml version=1.0
encoding=utf-8?soap:Envelope xmlns:cm=https://adwords.google.com/
api/adwords/cm/v200909 xmlns:enc=http://schemas.xmlsoap.org/soap/
encoding/ xmlns:info=https://adwords.google.com/api/adwords/info/
v200909 xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://
www.w3.org/2001/XMLSchema-instancesoap:HeaderRequestHeader
xmlns=https://adwords.google.com/api/adwords/info/
v200909cm:authTokenXXX/cm:authTokencm:userAgentRimm-Kaufman
Group GAPI v200909, x...@rimmkaufman.com/
cm:userAgentcm:developerTokenXXX/
cm:developerTokencm:applicationTokenXXX/cm:applicationToken/
RequestHeader/soap:Headersoap:Bodyget xmlns=https://
adwords.google.com/api/adwords/info/
v200909selectorserviceNameAdGroupService/
serviceNamemethodNameupdateAdGroupList/
methodNamedateRangecm:min2010-03-25/cm:mincm:max2010-03-25/
cm:max/dateRangeapiUsageTypeUNIT_COUNT/apiUsageType/selector/
get/soap:Body/soap:Envelope

Note, Eric, that we had to set the namespaces for our RequestHeader
elements to the cm namespace, not info.  And least this works for the
sandbox.

I guess the point is, no matter what we send to the live InfoService,
it always returns the ISE.

Anthony

On Mar 25, 4:10 pm, Eric wetr...@gmail.com wrote:
 We are making the following SOAP request to the InfoServer.  The HTTP/
 SOAP response is given below and we are stumped as to the problem.  We
 are using the Java client jar.  Any insight would be appreciated.

 ?xml version=1.0 encoding=UTF-8?
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/
 envelope/ xmlns:xsd=http://www.w3.org/2001/XMLSchema;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
   soapenv:Header
     ns1:useragent xmlns:ns1=https://adwords.google.com/api/adwords/
 info/v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/actor/
 next soapenv:mustUnderstand=0XXX/ns1:useragent
     ns2:email xmlns:ns2=https://adwords.google.com/api/adwords/info/
 v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/actor/next;
 soapenv:mustUnderstand=0XXX/ns2:email
     ns3:clientEmail xmlns:ns3=https://adwords.google.com/api/adwords/
 info/v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/actor/
 next soapenv:mustUnderstand=0XXX/ns3:clientEmail
     ns4:developerToken xmlns:ns4=https://adwords.google.com/api/
 adwords/info/v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/
 actor/next soapenv:mustUnderstand=0XXX/ns4:developerToken
     ns5:applicationToken xmlns:ns5=https://adwords.google.com/api/
 adwords/info/v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/
 actor/next soapenv:mustUnderstand=0XXX/ns5:applicationToken
     ns6:authToken xmlns:ns6=https://adwords.google.com/api/adwords/
 info/v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/actor/
 next soapenv:mustUnderstand=0XXX/ns6:authToken
   /soapenv:Header
   soapenv:Body
     get xmlns=https://adwords.google.com/api/adwords/info/v200909;
       selector
         apiUsageTypeTOTAL_USAGE_API_UNITS_PER_MONTH/apiUsageType
       /selector
     /get
   /soapenv:Body
 /soapenv:Envelope

 HTTP/1.0 500 Internal Server Error
 Content-Type text/xml; charset=UTF-8
 Date Thu, 25 Mar 2010 19:46:10 GMT
 Expires Thu, 25 Mar 2010 19:46:10 GMT
 Cache-Control private, max-age=0
 X-Content-Type-Options nosniff
 X-Frame-Options SAMEORIGIN
 Server GSE
 X-XSS-Protection 0

 no Content-Length

 XML received:
 ---
 soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
   soap:Body
     soap:Fault
       faultcodesoap:Server/faultcode
       faultstringFault occurred while processing./faultstring
     /soap:Fault
   /soap:Body
 /soap:Envelope

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 

AdWords API Re: Operator.ADD not supported in CampaignTargetService

2010-03-26 Thread Peer Jakobsen (AdWords API Guru)
I think the reason is that a campaign always exist with all
targetlists there, even after newly creation. They might be empty, but
they are always there.

Cheers

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: NetworkCoverageType Stats

2010-03-26 Thread Raj
Thanks for your reply Eric.

Still one more question.

In our account, we have some campaigns for which we selected targeting
as google search
for some we set as content.

but when I call AdwordsTargetingService for some campaigns having
targeting type google search, I am getting Networktargeting type as
both GOOGLE_SEARCH and CONTENT_CONTEXTUAL

even the content option is unselected.

Why is this happening?


On Mar 25, 9:44 pm, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
 Hi Raj,

 More information on these values is available here:

  http://groups.google.com/group/adwords-api/browse_thread/thread/cff28...

 Best,
 - Eric Koleda, AdWords API Team

 On Mar 24, 4:12 pm, Raj rajanikant...@gmail.com wrote:



  I am sorry I corrected this bug.

  But I need some help in the following.

  I used CampaignTargetingService to get NetworkCoverateType.

  The thing is I am getting correct types for some campaigns and for
  some other I am getting three types GOOGLE_SEARCH, SEARCH_NETWORK,
  CONTENT_CONTEXTUAL

  which is unusual in my campaigns.

  I would like to know based on which parameters it is giving these
  types?
  like history, or dates...

  Thanks,
  Raj

  On Mar 24, 1:13 pm, Raj rajanikant...@gmail.com wrote:

   Hello adwords team,
   I have two questions.

   1. I am working on getting all campaigns.
   I need to get networktype.
   For this I used Campaign service where I am getting network type as
   ALL but actually it should be of GOOGLE_SEARCH

   then I saw one of your reply for one question and
   I used CampaignTargetService.
   Here I am getting
   [88] = NetworkTargetList Object
                   (
                       [targets] = Array
                           (
                               [0] = NetworkTarget Object
                                   (
                                       [networkCoverageType] =
   CONTENT_CONTEXTUAL
                                       [TargetType] = NetworkTarget
                                       [_parameterMap:private] = Array
                                           (
                                               [Target.Type] =
   TargetType
                                           )

                                   )

                               [1] = NetworkTarget Object
                                   (
                                       [networkCoverageType] =
   GOOGLE_SEARCH
                                       [TargetType] = NetworkTarget
                                       [_parameterMap:private] = Array
                                           (
                                               [Target.Type] =
   TargetType
                                           )

                                   )

                               [2] = NetworkTarget Object
                                   (
                                       [networkCoverageType] =
   SEARCH_NETWORK
                                       [TargetType] = NetworkTarget
                                       [_parameterMap:private] = Array
                                           (
                                               [Target.Type] =
   TargetType
                                           )

                                   )

                           )

                       [campaignId] = 46466421
                       [TargetListType] = NetworkTargetList
                       [_parameterMap:private] = Array
                           (
                               [TargetList.Type] = TargetListType
                           )

                   )

   If you see It is also giving three values means ALL
   But It is of GOOGLE_SEARCH type.

   2. One more thing is I am getting 35-40 campaign ids results for a
   given single campaign ID. Which don't exist in my adwords account.

   Please help me in this.

   Thanks,
   Raj

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Handling 'get'/'mutate' errors and exceptions (in PHP)

2010-03-26 Thread WallTearer
Hello everybody.

I've started migrating project from v13 to v2009.
An I'm wondering what is the best practice to handle errors in v2009?

As for the v13 apility there was a possibility to see errors that
happen by calling $adwordsUser-getFaultStack();
And for the v2009 I found that the only possibility to see the error -
is to catch the Exception that is thrown by the 'get'/'mutate'
methods.
Looking on the returned SoapFault object, the error message is kinda
[EntityNotFound.INVALID_ID @ selector; trigger:'CampaignId:
473078790'] - this seems to me not very usefull when showing error
message to the user.

So can someone please explain, what is the best (or at least
reasonable) way in new AdWords API to handle an errors and show them
to the user?

Regards,
Kirill

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Type of errors when max number of entities have been reached.

2010-03-26 Thread Peer Jakobsen (AdWords API Guru)
In adwords you have all kind of size limits:
Max number of campaigns in account
Max number of adgroups
Max number of criteria
Max number of ads
...

What error types can we expect to see when those limits are reached?

I can see this AdGroupAdCountLimitExceeded, but what about the other
limits?

For example if I am trying to create a new campaign and the account
limit has been reached, what error will I receive (not easy to
reproduce in sandbox)?

Thanks

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: Handling 'get'/'mutate' errors and exceptions (in PHP)

2010-03-26 Thread Pete Lavetsky (AdWords API Guru)
try Something
catch ApiException
for ApiError in ApiException
   log ApiError.FieldPath
   log ApiError.Trigger
   log ApiErrorType
   cast ApiError - SpecificApiErrorType
   log SpecificApiErrorType.Reason

It is kinda gnarly, but definitely workable ... when you pass in a
list / array of objects for mutating, you can parse any ApiException
coming back to get the index of the Object that failed through some
ApiError.FieldPath manipulation ... then remove that item from your
mutating list and rinse  repeat

Pete


On Mar 26, 1:18 pm, WallTearer walltea...@gmail.com wrote:
 Hello everybody.

 I've started migrating project from v13 to v2009.
 An I'm wondering what is the best practice to handle errors in v2009?

 As for the v13 apility there was a possibility to see errors that
 happen by calling $adwordsUser-getFaultStack();
 And for the v2009 I found that the only possibility to see the error -
 is to catch the Exception that is thrown by the 'get'/'mutate'
 methods.
 Looking on the returned SoapFault object, the error message is kinda
 [EntityNotFound.INVALID_ID @ selector; trigger:'CampaignId:
 473078790'] - this seems to me not very usefull when showing error
 message to the user.

 So can someone please explain, what is the best (or at least
 reasonable) way in new AdWords API to handle an errors and show them
 to the user?

 Regards,
 Kirill

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: Type of errors when max number of entities have been reached.

2010-03-26 Thread Pete Lavetsky (AdWords API Guru)
http://code.google.com/apis/adwords/v2009/docs/reference/CampaignService.QuotaError.Reason.html

Pete

On Mar 26, 2:01 pm, Peer Jakobsen (AdWords API Guru)
peer.jakob...@gmail.com wrote:
 In adwords you have all kind of size limits:
 Max number of campaigns in account
 Max number of adgroups
 Max number of criteria
 Max number of ads
 ...

 What error types can we expect to see when those limits are reached?

 I can see this AdGroupAdCountLimitExceeded, but what about the other
 limits?

 For example if I am trying to create a new campaign and the account
 limit has been reached, what error will I receive (not easy to
 reproduce in sandbox)?

 Thanks

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API 10+ second latency deleting criteria (v2009)

2010-03-26 Thread Maxim
We are seing very slow execution of deleteCriteria() even if only 1
criterion is being deleted. v2009.
This problem was reported in 2006 and early 2007, but seems to be back
again in v2009.

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


Re: AdWords API Re: Got this error Separate content keyword bids is only applicable in campaigns with keyword cpc bids.

2010-03-26 Thread AdWords API Advisor
Hi Harald,

From what I can tell this bug has not yet been fixed in the v13
version of the API.  Given the sunset of the v13 campaign management
services on April 22nd, I would urge you to migrate your code to the
v200909 version of the API which doesn't have this issue.

Best,
- Eric

On Mar 25, 6:43 am, HB harald.bar...@prozentor.de wrote:
 Hi Eric,

 the 
 link:http://www.mail-archive.com/adwords-api@googlegroups.com/msg02065.html

 Thanks,
 Harald

 On Mar 23, 5:39 pm, AdWords API Advisor adwordsapiadvi...@google.com
 wrote:



  Hi Harald,

  Can you link to the original thread so I can get more background
  information on this problem?  Do you have the SOAP XML from your
  request that generates this error?

  Best,
  - Eric Koleda, AdWords API Team

  On Mar 22, 2:41 pm, Harald Bartel harald.bar...@prozentor.de wrote:

   Hello,

   this bug seems not to be fixed.
   What shoud I do if I have this problem?

   best regards
   Harald

   On Mar 4, 1:44 pm, AdWords API Advisor adwordsapiadvi...@google.com
   wrote:
     Hello Xavier,
    
      This is a bug that the engineering team is going to have to resolve.
    
      I'll update this thread with more information when I have it, but
     they are actively looking into the issue.
    
     Cheers,
     -Jeff Posnick, AdWords API Team

   --
   Harald Bartel

   Prozentor GmbH |http://www.prozentor.de
   Brunnenstr. 4  | 10119 Berlin | Germany
   fon:+49 30 284459-42  fax:+49 30 284459-59

   Amtsgericht: Berlin-Charlottenburg HRB 70501
   Gesch ftsf hrerin: Stephanie Richter

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Keyword update using v2009

2010-03-26 Thread abhijat
I was wondering why is the text field required by the Keyword object
when we are trying to do a SET operation using the
AdGroupCriterionService.

Is this is a common use case that API users frequently modify the
existing keyword text?

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


Re: How can I signup to AdWords API

2010-03-26 Thread AdWords API Advisor
Hi,

The AdWords API Center menu is under the My Account tab in the MCC
(My Client Center) user interface.

Best,
- Eric Koleda, AdWords API Team

On Mar 25, 8:13 am, bcurtu bcu...@gmail.com wrote:
 I'm getting crazy. I want to use the AdWords API for the second
 profile (or anyone!) but I don't find the API Center menu anywhere.
 Please help

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: v13 TrafficEstimatorService queried via apility gives back: HTTP method POST is not supported by this URL

2010-03-26 Thread AdWords API Advisor
Hi Sean,

I'm not sure what changed recently, but the error is caused by trying
to post your SOAP request to the address of the WSDL.  As specified in
the WSDL, the URL endpoint of the service doesn't contain the ?wsdl
parameter.

  wsdl:service name=TrafficEstimatorService
wsdl:port binding=impl:TrafficEstimatorServiceSoapBinding
name=TrafficEstimatorService
  wsdlsoap:address location=https://adwords.google.com/api/
adwords/v13/TrafficEstimatorService/
/wsdl:port
  /wsdl:service

If you remove that parameter everything should work correctly.

Best,
- Eric Koleda, AdWords API Team

On Mar 25, 1:30 pm, sed sean-goo...@durak.org wrote:
 since february 2007, i've used two php scripts to query the adwords
 api TrafficEstimatorService via the @pility (apility) library. apart
 from upgrading the library to keep pace with each adwords api release,
 everything works unattended in a weekly cron job.

 sometime between march 9 and 15, the TrafficEstimatorService soap
 requests generated by apility started to fail with an error HTTP
 method POST is not supported by this URL, for a request that looks
 like:

  POST /api/adwords/v13/TrafficEstimatorService?wsdl HTTP/1.0
  Host: adwords.google.com
  User-Agent: NuSOAP/0.7.2 (1.1)
  Content-Type: text/xml; charset=UTF-8
  SOAPAction: 
  Content-Length: 13623

 did something change with respect to the way v13 api requests must be
 made going forward? get vs. post, new hostname, changed authentication
 method, etc. - or is this perhaps something unique to my environment?

 is anyone else still using apility to make their requests to v13 of
 the adwords api?

 i'm aware that many of the adwords api features are moving to v2009
 only next month, but expected v13 to remain available for features
 that are not yet ported to v2009 like the traffic estimator service.

 thanks very much if anyone can shed some light on the issue!

 -sean

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: Keyword update using v2009

2010-03-26 Thread Peer Jakobsen (AdWords API Guru)
On SET operations you can use the Criterion object instead of the
Keyword/Placement objects. That way you only have to pass the
criterion id.

Cheers

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: Adwords API traffic estimator service - several errors when campaign request includes a geotarget

2010-03-26 Thread AdWords API Advisor
Hi Guy,

I apologize for the lack of documentation for these limitations of the
TrafficEstimatorService.  As for your previous post about proximity
targets, I did respond to it, and and you can read the response here:

  
http://groups.google.com/group/adwords-api/browse_thread/thread/326b45bbddaf7897/

The only other documentation I am aware of for the
TrafficEstimatorService is this blog post:

http://adwordsapi.blogspot.com/2008/07/traffic-estimator-service-explained.html

On Mar 25, 1:30 pm, Guy Zucker gzuck...@gmail.com wrote:
 Hi,

 I'm using the traffic estimator service.
 I create a campaign request that has a geotarget that contains a country
 and a state (e.g. Canada and New York State).
 The estimation fails with the following messages: Cannot combine country
 and region/metro/city targeting.
 This does not appear as a limitation in the api docs.

 In addition, in a previous mail I sent (titled traffic estimation service -
 problematic results when using proximity targets) which has not received a
 response yet, I discovered the service does not work well with proximity
 targets.

 Are there any other limitations that are not published?

 Also, will this service continue to use v13 geotarget objects after the v13
 sunset?

 Thanks,

 Guy

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: TargetingIdea

2010-03-26 Thread AdWords API Advisor
Hi Andy,

This problem is normally seen when a client is using .NET without the
client library.  The cause is that the .NET wsdl to code generator
will under certain circumstances not generate certain classes.  More
information is available here:

  
http://code.google.com/p/google-api-adwords-dotnet/wiki/NoClientLibrary#b._wsdl.exe_doesn't_generate_some_types_properly.

It appears that you are using the client library however.  Did you
rebuild the classes at any point?

Best,
- Eric Koleda, AdWords API Team

On Mar 26, 8:25 am, Andy Precise andy.moul...@gmail.com wrote:
 oh come on API experts, you must have an idea what's going on here. i
 can't progress any further until i can use this class [TargetingIdeas]

 i've got an excel project to convert from v1.3 to v2009. it uses the
 existing getKeywordsFromSite method.

 i'm re-writing it to use TargetingIdeaSelector.

 It's been fine up until the point that i need to use TargetingIdea.
 and it is NOT recognised as a type. everything else is fine:
 TargetingIdeaPage, SearchParameter, Type_AttributeMapEntry, Attribute
 etc.

 this thing is declared in the WSDL along with all the other types. so
 it's there. why isn't it recognised ?

 this is the sample code i've been using from another posting on this
 site (see bottom of post). i've had to convert this to VB.NET, but
 everything starts going wrong with these lines:

             TargetingIdea[] keywords = mySiteKeywordGroups.entries;
             foreach (TargetingIdea keywordFromAPI in keywords)

 TargetingIdeas is not recognised as a type. why  i'm not doing
 anything out of the ordinary. i've added a web service, added an
 Imports statement at the top of the spreadsheet. all other types/
 methods etc. are regonised. but not this one !!! aag !!!

 could i be doing something wrong ? is this a bug ?

 PLEASE PLEASE PLEASE HELP !

 -- CODE BEGINS

 AdWordsUser user = new AdWordsUser();

             // Get the service.
             TargetingIdeaService service =

 (TargetingIdeaService)user.GetService(AdWordsService.v200909.TargetingIdeaS ­
 ervice);

             TargetingIdeaSelector selector = new
 TargetingIdeaSelector();
             selector.ideaType = IdeaType.KEYWORD;
             selector.ideaTypeSpecified = true;
             selector.requestType = RequestType.IDEAS;
             selector.requestTypeSpecified = true;
             selector.requestedAttributeTypes = new AttributeType[]
 { AttributeType.KEYWORD,
                 AttributeType.GLOBAL_MONTHLY_SEARCHES,
 AttributeType.COMPETITION };

             RelatedToUrlSearchParameter param = new
 RelatedToUrlSearchParameter();
             param.urls = new string[] { url };

             selector.searchParameters = new SearchParameter[]
 { param };

             Paging paging = new Paging();
             paging.startIndex = 0;
             paging.startIndexSpecified = true;
             paging.numberResults = 100;
             paging.numberResultsSpecified = true;

             selector.paging = paging;

             // Get a list of keywords for this site.
             TargetingIdeaPage mySiteKeywordGroups =
 service.getBulkKeywordIdeas(selector);

             TargetingIdea[] keywords = mySiteKeywordGroups.entries;

             foreach (TargetingIdea keywordFromAPI in keywords)
             {
                 foreach (Type_AttributeMapEntry entry in
 keywordFromAPI.data)
                 {
                     if (entry.key == AttributeType.KEYWORD)
                     {
                         //Code is entering here - and I can read the
 keyword text
                     }
                     else if (entry.key == AttributeType.COMPETITION)
                     {
                         //entry.key is never COMPETITION
                     }
                     else if (entry.key ==
 AttributeType.GLOBAL_MONTHLY_SEARCHES)
                     {
                         //entry.key is never GLOBAL_MONTHLY_SEARCHES
                     }
                 }
             }

 -- CODE ENDS

 On Mar 25, 6:06 pm, Andy Precise andy.moul...@gmail.com wrote:



  in addition ... i checked the wsdl file for this service and
  TargetingIdea is declared, along with other types
  Type_AttributeMapEntry, TargetingIdeaPage. etc. the latter of all
  which are recognised. but not TargetingIdea.

  would appreciate any ideas on this.

  thanks

  On Mar 25, 2:52 pm, Andy Precise andy.moul...@gmail.com wrote:

   hi,

     this is a strange one. i must be doing something wrong, but i can't
   figure out what.

     i'm migrating from v1.3 to v2009 as many others have been.

     i'm using the TargetingIdeaService service to get keywords for a
   given site.

     i'm updating an excel project (VB.NET)

     i've been looking for several code examples over the internet on how
   to migrate from the old getKeywordsFromSite service call to the new
   one and i've come across a problem.

     the code samples i've found all reference an 

Re: Getting data through AdWords API and .NET

2010-03-26 Thread AdWords API Advisor
Hi Haris,

There is no step-by-step guide available, but here is an example of
creating a keyword report using the C# client library:

  
http://code.google.com/p/google-api-adwords-dotnet/source/browse/trunk/Examples/v13/ReportServiceKeywordDemo.cs

Best,
- Eric Koleda, AdWords API Team

On Mar 25, 12:09 pm, haris haris.ke...@green-river-media.com wrote:
 Hi all, I'm quite new to AdWords API, and I would like to know how I
 could get data like campaign, keyword,  impressions, clicks,
 total cost and so on for a particular user (client) in a specified
 date range, using .NET (C#) and google API.
 Of course for testing purposes I would use sandbox.

 I read the API documentation, but for me it is still not clear how to
 do this.

 Could anyone explain it in a simple way? What do I have to do step by
 step? Is there an example?

 I already created an AdWords account using my existing email. So what
 is the next step?

 Please help.

 Thanks a lot.

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: Question with CaptchaRequired error code with ClientLogin authentication API

2010-03-26 Thread AdWords API Advisor
Hi,

Thanks for the clarification, and my apologies for the
misunderstanding.  As for question #1, I think you need to think of
CAPTCHA challenges as short lived and one use only.  As I mentioned
earlier, CAPTCHA challenges should resolve on their own after 10
minutes or so, assuming the offending traffic to the ClientLogin API
has stopped.  The purpose of solving the CAPTCHA challenge is to
unlock the account immediately instead of waiting.  This means you
probably shouldn't store CAPTCHA challenges for later, and if the user
decides not the solve the CAPTCHA challenge then it should be
discarded.  You can always get a new CaptchaUrl by making another
request to the ClientLogin API.

Best,
- Eric Koleda, AdWords API Team

On Mar 25, 2:40 pm, SEM sem...@gmail.com wrote:
 Eric:

 I think you may have misunderstood my original question although you
 did answer my next question :-)

 The two questions are..

 Original Question 1:
 a] User's account is locked due to captcha, we store the captcha URL
 and present him with an image sourced from the stored captcha URL
 b] User chooses to ignore the captcha unlock request by hitting the
 CANCEL button in our UI.
 c] User comes back a day later and re-invokes our UI which attempts to
 show the same image (retrieved from previously stored captcha URL) but
 the image fails with this error message:
 Sorry, we are unable to handle your request at this time. Please try
 again later

 Seems like the image URL only works once or a limited number of times
 when requested for and subsequently fails.
 This is what we need clarification on.

 Second Question:
 a] User's account is locked due to captcha, we store the captcha URL
 and present him with an image sourced from the stored captcha URL
 b] User attempts to unlock the captcha request by entering the
 characters shown in the image
 c] User enters invalid text and a new captcha URL is returned that
 must be presented in a subsequent attempt.
 If we did not store this new captcha URL then yes ... the original
 captcha URL image is probably invalidated and will not work.
 However, this is not the use case I am referring to.

 Thanks.

 On Mar 24, 2:21 pm, AdWords API Advisor adwordsapiadvi...@google.com
 wrote:



  Hi,

  CAPTCHA images cannot be reused, and for each CAPTCHA challenge you
  must use the returned CaptchaUrl value to get the new CAPTCHA image.

  Best,
  - Eric

  On Mar 23, 6:51 pm, SEM sem...@gmail.com wrote:

   Hi Eric,

   After the account is locked with Error=CaptchaRequired, as per the
   docs, we prefix the captcha url withhttps://www.google.com/accounts
   and we get the captcha image.

   e.g. we 
   usehttps://www.google.com/accounts/Captcha?ctoken=4MdDSDSmfdkmdsIazxK80f...

   (ctoken value changed for privacy reasons)

   However, after the first captcha url request, all subsequent requests
   return an image that displays an error message in red text:
   Sorry, we are unable to handle your request at this time. Please try
   again later.. Is this a bug or an intended feature?

   If a bug, when will this be fixed?

   If a feature, is there a limitation on the number of times the captcha
   image is available for manual unlocking? Is our application expected
   to cache the captcha image bytes or should the above captcha URL work?
   Assuming that we cache this captcha image and allow the user to re-
   enter his captcha text in a subsequent session, will his request
   succeed? This seems like a lot of overkill for application developers
   and a significant degradation of the end user experience.

   Please let us know how this should be handled.

   Thanks

   On Mar 19, 12:21 pm, AdWords API Advisor

   adwordsapiadvi...@google.com wrote:
Hi,

I followed up with our authentication team, and they said that if you
wait for about 10 minutes theCAPTCHAchallenges should be resolved on
their own.  Let us know if you have any problems.

Best,
- Eric Koleda, AdWords API Team

On Mar 18, 5:36 pm, SEM sem...@gmail.com wrote:

 Eric:

 We aren't assuming that 403/CAPTCHAerrors will resolve themselves
 automatically.
 Also, we understand that 403/CAPTCHAerrors could occur for a variety
 of reasons.

 Our situation is as follows:
 We rolled out a production update to v200909 withoutClientLogin/
 authtoken caching resulting in a lot of 403/CAPTCHAlocks for our
 customer base of several hundred customers (due to excessive logins).
 We would prefer not to subject our customers to this inconvenience due
 to this architectural change in authentication and unlock their
 accounts on their behalf.
 That said, if these specific 403/CAPTCHAerrors unlock themselves
 after a period of a few hours (by which time our caching code goes
 in), we can hold off on unlocking these errors manually.
 Could you let us know what the duration is for theseCAPTCHAerrors
 (for this specific reason - i.e. due to throttling 

AdWords API Re: getClientAccounts() returns an invalid e-mail?

2010-03-26 Thread AdWords API Advisor
Hi Joshua,

Can you provide the requestId of the getClientAccounts() and
getAccountInfo() requests the demonstrate this behavior?

Best,
- Eric Koleda, AdWords API Team

On Mar 25, 3:35 pm, Joshua J. Kugler jos...@eeinternet.com wrote:
 I have code like so:

     for account in ga.Account.getClientAccounts():
         # 'account' is an e-mail in the list of e-mails returned
         print account
         ga.set_client_email(account) # Sets the client e-mail header
         try:
             client = ga.Account.getAccountInfo()
             print client.descriptiveName

 This code works, but there is at least one e-mail that returns the
 error 'Invalid client email specified.' even though it is an e-mail
 returned by getClientAccounts() *AND* this e-mail *is* in the list of
 clients when I log in to the web interface.

 Any idea how to trouble shoot this?

 Thanks!

 j

 --
 Joshua Kugler
 Part-Time System Admin/Programmerhttp://www.eeinternet.com
 PGP Key:http://pgp.mit.edu/ID 0x73B13B6A

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API Re: Internal Server Error from InfoService request

2010-03-26 Thread AdWords API Advisor
Hi,

It looks like you are getting the same error, but for different
causes.

Eric,

You need to ensure you wrap your headers in the RequestHeader
element.  That element must be in the info namespace, while the fields
must be in the cm namespace.  See Anthony's XML as an example.

Anthony,

In your case the error is due to improperly formatted date strings.
There are no dashes in v200909 date strings, and they should look like
20100325.

Best,
- Eric Koleda, AdWords API Team

On Mar 26, 11:02 am, Anthony - RKG anth...@rimmkaufman.com wrote:
 Eric,

 Join the club.  After much pain and suffering getting the Sandbox
 InfoService routines working (the clientEmail Request Header either
 must not exist or be different from other Serivce requests and not
 include 'client+1'), we made the changes live this morning.  No matter
 what we send to the InfoService, we get back:

     API-fault for InfoService-get: Internal Server Error(500), Fault
 occurred while processing.

 We are using our own Perl API.  Here is the original request:

 [INFO] retrieve-quota-usage: 
 POSThttps://adwords.google.com/api/adwords/info/v200909/InfoService
 Content-Type: text/xml SOAPAction: #get ?xml version=1.0
 encoding=utf-8?soap:Envelope xmlns:cm=https://adwords.google.com/
 api/adwords/cm/v200909 xmlns:enc=http://schemas.xmlsoap.org/soap/
 encoding/ xmlns:info=https://adwords.google.com/api/adwords/info/
 v200909 xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
 xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;soap:HeaderRequestHeader
 xmlns=https://adwords.google.com/api/adwords/info/
 v200909cm:authTokenXXX/cm:authTokencm:userAgentRimm-Kaufman
 Group GAPI v200909, x...@rimmkaufman.com/
 cm:userAgentcm:developerTokenXXX/
 cm:developerTokencm:applicationTokenXXX/cm:applicationToken/
 RequestHeader/soap:Headersoap:Bodyget xmlns=https://
 adwords.google.com/api/adwords/info/
 v200909selectorserviceNameAdGroupService/
 serviceNamemethodNameupdateAdGroupList/
 methodNamedateRangecm:min2010-03-25/cm:mincm:max2010-03-25/
 cm:max/dateRangeapiUsageTypeUNIT_COUNT/apiUsageType/selector/
 get/soap:Body/soap:Envelope

 Note, Eric, that we had to set the namespaces for our RequestHeader
 elements to the cm namespace, not info.  And least this works for the
 sandbox.

 I guess the point is, no matter what we send to the live InfoService,
 it always returns the ISE.

 Anthony

 On Mar 25, 4:10 pm, Eric wetr...@gmail.com wrote:



  We are making the following SOAP request to the InfoServer.  The HTTP/
  SOAP response is given below and we are stumped as to the problem.  We
  are using the Java client jar.  Any insight would be appreciated.

  ?xml version=1.0 encoding=UTF-8?
  soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/
  envelope/ xmlns:xsd=http://www.w3.org/2001/XMLSchema;
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
    soapenv:Header
      ns1:useragent xmlns:ns1=https://adwords.google.com/api/adwords/
  info/v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/actor/
  next soapenv:mustUnderstand=0XXX/ns1:useragent
      ns2:email xmlns:ns2=https://adwords.google.com/api/adwords/info/
  v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/actor/next;
  soapenv:mustUnderstand=0XXX/ns2:email
      ns3:clientEmail xmlns:ns3=https://adwords.google.com/api/adwords/
  info/v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/actor/
  next soapenv:mustUnderstand=0XXX/ns3:clientEmail
      ns4:developerToken xmlns:ns4=https://adwords.google.com/api/
  adwords/info/v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/
  actor/next soapenv:mustUnderstand=0XXX/ns4:developerToken
      ns5:applicationToken xmlns:ns5=https://adwords.google.com/api/
  adwords/info/v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/
  actor/next soapenv:mustUnderstand=0XXX/ns5:applicationToken
      ns6:authToken xmlns:ns6=https://adwords.google.com/api/adwords/
  info/v200909 soapenv:actor=http://schemas.xmlsoap.org/soap/actor/
  next soapenv:mustUnderstand=0XXX/ns6:authToken
    /soapenv:Header
    soapenv:Body
      get xmlns=https://adwords.google.com/api/adwords/info/v200909;
        selector
          apiUsageTypeTOTAL_USAGE_API_UNITS_PER_MONTH/apiUsageType
        /selector
      /get
    /soapenv:Body
  /soapenv:Envelope

  HTTP/1.0 500 Internal Server Error
  Content-Type text/xml; charset=UTF-8
  Date Thu, 25 Mar 2010 19:46:10 GMT
  Expires Thu, 25 Mar 2010 19:46:10 GMT
  Cache-Control private, max-age=0
  X-Content-Type-Options nosniff
  X-Frame-Options SAMEORIGIN
  Server GSE
  X-XSS-Protection 0

  no Content-Length

  XML received:
  ---
  soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
    soap:Body
      soap:Fault
        faultcodesoap:Server/faultcode
        faultstringFault occurred while processing./faultstring
      /soap:Fault
    /soap:Body
  /soap:Envelope

-- 

AdWords API Re: 10+ second latency deleting criteria (v2009)

2010-03-26 Thread Maxim
also seeing huge delays in execution of
adGroupCriterionService.mutate(ADD) operations.

Are you guys throttling us down?

On Mar 26, 1:26 pm, Maxim mse...@gmail.com wrote:
 We are seing very slow execution of deleteCriteria() even if only 1
 criterion is being deleted. v2009.
 This problem was reported in 2006 and early 2007, but seems to be back
 again in v2009.

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


AdWords API No data return when AdGroupCriterionIdFilter set to adGroupId

2010-03-26 Thread Dave L
Hi,

I have experienced a strange problem, I am not sure if this is my
account issue or a common problem, hope someone can help.

When I tried to use AdGroupCriterionService to retrieve keywords, if
I set the AdGroupCriterionIdFilter to campaignId or criterionId,
it works fine. But if I set the AdGroupCriterionIdFilter to
adGroupId, there is not data return back from Google server after 3
or 5 minutes and it will simply timeout.

I don't think there is nothing wrong with my code because when I set
the AdGroupCriterionIdFilter to campaignId or criterionId, it
works fine. So, I am pretty sure my code is correct. The only
different is I pass the adgroup ID to adGroupId, then no data return
from Google.

Please HELP !!

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.


Re: How can I signup to AdWords API

2010-03-26 Thread Devon Smith
Hello,

  My client has recently registered for adwords account. He has
granted me the 'STANDARD' account access.
Now he is registered with My Client Center. So when i pass
authentication information in the SOAP header, which email and
passwrod
should i use. My client's email  password or my own email  password
to which the client has granted 'STANDARD' account access or
email  password of 'My Client Center'. Please help me.

Thanks
Devon Smith.

On Mar 27, 1:56 am, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
 Hi,

 The AdWords API Center menu is under the My Account tab in the MCC
 (My Client Center) user interface.

 Best,
 - Eric Koleda, AdWords API Team

 On Mar 25, 8:13 am, bcurtu bcu...@gmail.com wrote:

  I'm getting crazy. I want to use the AdWords API for the second
  profile (or anyone!) but I don't find the API Center menu anywhere.
  Please help



-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
REMOVE ME as the subject.