Hi Albin,
Thank you for reaching out. I think you have misunderstood the two concepts
here. The login_customer_id has to be set in the configuration file and it
eventually will be used in the request header. For the resource, you have to
use the client customer id in the format of
customers/{customer_id}/adGroups/{ad_group_id} to trace down to the lowest
level entity. The client customer id could be set in a way such as in this
example.
Thanks and regards,
Xiaoming, Google Ads API Team
Xiaoming
Google Ads API Team
ref:_00D1U1174p._5004Q2CQKJZ:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/IReLi000000000000000000000000000000000000000000000QOFNLM00Hu1BarfqToONCPoUy32afA%40sfdc.net.
