Hi Langfei,
The client ID/client secret are generated specific to one's email address.
If you use an existing client ID/client secret to make an API call, the
email address who owns this will be recorded in your change history.
Hope that clarifies your concern.
Regards,
Luis
AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
On 01/24/19 14:13:36 langfei...@gmail.com wrote:
Thank you for your response. Why is it necessary to replace client id and
client secrets?
On Wed, Jan 23, 2019, 21:11 googleadsapi-forumadvisor via AdWords API and
Google Ads API Forum <adwords-api@googlegroups.com wrote:
Hi Langfei,
To make sure that developer B is using its own credentials, you must make
sure that developer B generates its own OAuth2 credentials
<https://developers.google.com/adwords/api/docs/guides/authentication> using
its own email address that has access to your Google Ads account. This
said, developer B should have its own email address, client ID/client
secret and refresh token.
Thanks and regards,
Luis
AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Was your question answered? Please rate your experience with us by taking a
short survey.
If not -- reply to this email and tell us what else we can do to help.
Take Survey
<https://support.google.com/google-ads/contact/survey_transactional?caseid=3-1367000025107&hl=en&ctx=1>
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
On 01/24/19 08:35:20 langfei...@gmail.com wrote:
We have a tool making changes to our campaign through Adwords API. These
changes show up in the change history tagged with developer A's
account/email. Now we want to change that so that changes made by this tool
will be tagged with developer B. We are now making API calls with developer
B's token while client id/secret stayed the same. However, the new changes
made the tool still gets tagged with developer A's email.
What would it take to make the changes show up tagged with developer B?
Thank you!
Langfei
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
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/859592f6-905a-45d6-b83e-a7a22e3fa656%40googlegroups.com
<https://groups.google.com/d/msgid/adwords-api/859592f6-905a-45d6-b83e-a7a22e3fa656%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
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/ijlio49e6o0000008sh78a005h4t54w6cmj2cpm6so30c1g68qj2c1n%40mail.gmail.com
<https://groups.google.com/d/msgid/adwords-api/ijlio49e6o0000008sh78a005h4t54w6cmj2cpm6so30c1g68qj2c1n%40mail.gmail.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
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/ijlio49e6o0000008v48eg005hh5fuz6cmj2cpm6so30c1g68qj2c1n%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
