Hi,

Using the PHP library, the customerService.mutate call keeps returning 
CLIENT_CUSTOMER_ID_IS_REQUIRED - even though the clientCustomerId header 
field is set. This is verified by calling any other service that requires 
the clientCustomerId - for instance, adGroupAdService.get or reporting 
service, etc. - immediately before the request. The first request goes 
through successfully, while the second one returns the error mentioned 
above.

Looking in the soap logs, the clientCustomerId field is present in the 
header of the adGroupAdService request, but not in the 
customerService.mutate request. We are happy to share the relevant request 
IDs.

Adding the following line of code to the AdWordsSoapClient.php file just 
before the GenerateSoapHeader function returns solved the problem:
$headerObject->clientCustomerId = 
$this->GetAdsUser()->GetClientCustomerId();

However, we would love to see a cleaner solution.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/7a21f219-c38f-4f1f-9cb0-f2fe2435cd6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • customerService... OMCC
    • Re: custom... 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum

Reply via email to