Approved token claiming 0 campaigns

38 views
Skip to first unread message

semrep...@gmail.com

unread,
Sep 20, 2016, 4:35:13 PM9/20/16
to AdWords API Forum
I have a question that I suspect is for Customer Service, but Google's CS has insisted that the question must be directed to this forum.  Perhaps someone here can get it routed to someone who can help.

We had a developer token several years ago.  It was approved, and we were using it normally.  Then we discontinued it because we wished to use an outside vendor's software, and they had their own token so ours was no longer needed.

Now we wish to stop using said outside vendor's software.  We applied for a "new" token, and were approved last week, but the only token we can find associated with our account is the same old string of characters.  When we attempt to regenerate it, it winds up as the same string.

We have attempted to use it, using exactly the code from Google API: https://github.com/googleads/googleads-perl-lib/blob/master/examples/v201607/basic_operations/get_campaigns.pl copied and pasted.  It runs, but it claims we have 0 campaigns (verified by outputting the SOAP response) - which is clearly false: we have many campaigns that have been running for years.  (I can confirm that OAuth authentication is working, because if I mess with the client ID or other settings, I get an authentication error instead of a response claiming we have 0 campaigns.)

Again, we are running a copy and paste from https://github.com/googleads/googleads-perl-lib/blob/master/examples/v201607/basic_operations/get_campaigns.pl - so if you want to see all of our code, just read what's at that link.  This is code that Google provided.  It is not our code.

I am posting from the account approved to use this token.

If I print $client->get_last_soap_request(), I get this SOAP request:

<?xml version="1.0" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ><SOAP-ENV:Header><RequestHeader xmlns="https://adwords.google.com/api/adwords/cm/v201607"><clientCustomerId xmlns="https://adwords.google.com/api/adwords/cm/v201607">891-884-4919</clientCustomerId><developerToken xmlns="https://adwords.google.com/api/adwords/cm/v201607">REDACTED</developerToken><userAgent xmlns="https://adwords.google.com/api/adwords/cm/v201607">unknown (AwApi-Perl/4.9.0, Common-Perl/3.2.0, SOAP-WSDL/3.003, libwww-perl/6.15, perl/5.016003, Logging/Enabled, PageProcessor)</userAgent><validateOnly xmlns="https://adwords.google.com/api/adwords/cm/v201607">false</validateOnly><partialFailure xmlns="https://adwords.google.com/api/adwords/cm/v201607">false</partialFailure></RequestHeader></SOAP-ENV:Header><SOAP-ENV:Body><get xmlns="https://adwords.google.com/api/adwords/cm/v201607"><serviceSelector><fields>Id</fields><fields>Name</fields><ordering><field>Name</field><sortOrder>ASCENDING</sortOrder></ordering><paging><startIndex>0</startIndex><numberResults>500</numberResults></paging></serviceSelector></get></SOAP-ENV:Body></SOAP-ENV:Envelope>

(Yes, the code redacts the developer token.  I believe this to be a good thing.)  And if I print $client->get_last_soap_response(), I get this response:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201607"><requestId>00053cf543e7c0c80a626688fe0f0210</requestId><serviceName>CampaignService</serviceName><methodName>get</methodName><operations>1</operations><responseTime>226</responseTime></ResponseHeader></soap:Header><soap:Body><getResponse xmlns="https://adwords.google.com/api/adwords/cm/v201607"><rval><totalNumEntries>0</totalNumEntries><Page.Type>CampaignPage</Page.Type></rval></getResponse></soap:Body></soap:Envelope>

That “totalNumEntries” appears to be the salient part.

What we suspect is the case is that the (re)activation somehow messed up, and that this is a configuration error specific to our account but in Google's databases.  We, obviously, can not fix such a thing.

Anthony Madrigal

unread,
Sep 20, 2016, 4:59:24 PM9/20/16
to AdWords API Forum
Hello,

There does not appear to be anything wrong with your token. The reason you are not getting any campaigns returned is because the clientCustomerId in your request is a manager (MCC) account. Most AdWords API services do not work on the MCC level. In order to get campaigns, you will need to make the request using a client level account Id.

Regards,
Anthony
AdWords API Team

semrep...@gmail.com

unread,
Sep 21, 2016, 1:17:27 PM9/21/16
to AdWords API Forum
We tried it with the client level account ID too.  That didn't work until late yesterday, though now it does.  So whatever the issue is, appears to have been fixed.  Thanks.

Anthony Madrigal

unread,
Sep 21, 2016, 1:40:28 PM9/21/16
to AdWords API Forum
Hi,

I'm glad to hear it's working now. Please let me know if this issue occurs again.

Cheers,
Anthony
AdWords API Team
Reply all
Reply to author
Forward
0 new messages