Hi,
I've found some weird behaviour trying to apply some conditions to an
AdGroupSelector.
I've attached a script to show this weird scenario :-(
Here is the output of the script ( Removing Campaign & Adgroups names for
the sake of privacy) , but feel free to execute in your own accounts:
Thanks for confirm it,
As a Workaround, (If anyone is interested )
We can use *ManagedCustomerService.get *, to achieve info about all
Accounts Managed by and MCC . ( If you are implementing webFlow , be sure
you include the clientCustomerId of your MCC in the SOAP Headers ) .
It would be
It seems that doesn't matter if you add your clientCustomerId(MCC) in the
soap headers or not .
>From our side , we always get only the ClientCustomerId of the MCC account.
As other people said in this thread , when you omit ClientCustomerId of
your MCC on SOAP Headers, it should return a
