Hi Peter,
Thank you for the response! 
I still do not understand a few things:

1. In the Parallel Report Download 
<https://developers.google.com/adwords/api/docs/samples/python/reporting#parallel-report-download>
 example 
you provided, the authentication in still being done using a yaml file. 
Doesn't it require a customer ID? I don't understand how you can 
authenticate via a yaml file and then provided different customer IDs.. 
does it override the original customer ID set in the yaml file?

2. "automatically refresh your access tokens 
<https://developers.google.com/adwords/api/docs/guides/authentication#access_token_expiration>"
 
- means that it will generate a new refresh token? We're using a hard coded 
refresh token in the yaml file and don't want it to change...

3. 
https://developers.google.com/adwords/api/docs/guides/conversion-tracking#importing_click_conversions
 
- Found this:
"When uploading click conversions for multiple accounts, you can specify 
the clientCustomerId of a common manager account and include operations 
with GCLIDs from across multiple accounts. A conversion is attributed to 
the proper account based on the origin of its GCLID."
Can this apply for my needs? Can I set the customer ID in the yaml file to 
be the MCC one and send gclids of it's child accounts and it will find the 
match?

Thanks,
Liron


On Thursday, March 22, 2018 at 7:12:05 AM UTC+2, Peter Oliquino wrote:
>
> Hi Liron,
>
> In order to avoid using multiple OAuth2 credentials and yaml files for 
> each of those client accounts under your MCC, I would recommend that you 
> generate 
> new OAuth2 credentials 
> <https://developers.google.com/adwords/api/docs/guides/authentication> using 
> an email address that has access to your MCC account. This way, the 
> generated OAuth2 credentials would have access to all the client accounts 
> under the said MCC's hierarchy. Afterwards, you may then refer to the 
> Parallel 
> Report Download 
> <https://developers.google.com/adwords/api/docs/samples/python/reporting#parallel-report-download>
>  example 
> and see how you can iterate through the client accounts of your MCC then 
> trigger a request for uploading conversions.
> This said, this should address your number 3 question.
>
> As for your number 1 and 2 questions, by using the supported client 
> libraries of the AdWords API, it will automatically refresh your access 
> tokens 
> <https://developers.google.com/adwords/api/docs/guides/authentication#access_token_expiration>
>  and 
> you will no longer have a need to manually trigger the refresh. I hope this 
> helps and feel free to write back if you have any further clarifications.
>
> Best regards,
> Peter
> AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/552dd5f6-7a42-4713-afe6-445bde04f222%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to