So my concern is usability and over-complication of applications using the new API for end users.
Please correct me if I am wrong, but as of the new Google Ads API, for any 3rd party tool where users authenticate their own Google Ads logins and then select Google Ads accounts to manage by the tool, the original workflow was: 1. Have a simple button to authenticate through OAuth2 modal window with your Google login 2. Application lists out all Google Ads accounts that the login has access to so user can select which accounts to manage in the tool *In the new Google Ads API:* 1. Have a simple button to authenticate through OAuth2 modal window with your Google login 2. Enter manually all customer IDs of all top MCCs this login has access to, one by one (have a good documentation explaining to a regular Google Ads user that they should only use the top MCC IDs, where they find it in the Google Ads interface and why it is needed) 3. Then list out all Google Ads accounts the login has access to Either I am misunderstanding how to use *loginCustomerId *or it is quite a step back in usability for all users using tools utilizing Google Ads API. *Migration to the new API* If the above is correct, this also means that if you have 500 Google logins in your database currently for your tool, you have to ask all 500 logins to go and manually enter all top MCCs' customer IDs for their Google login. They will have to map them manually, switching between the tool and Google Ads interface and copy pasting each customer ID. It is hard to understand why in the old AdWords API we could just list all accounts a Google Ads login has access to, just using its refresh token, while in the Google Ads API this is not possible anymore and users are required to enter data manually in order to use the API. On Tuesday, 27 October 2020 at 07:20:45 UTC+1 adsapiforumadvisor wrote: > Hi Ales, > > For general information on migration to the Google Ads API, you can refer > to this guide > <https://developers.google.com/google-ads/api/docs/migration>. As for the > login-customer-id > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#cid>, > > this should be the customer ID in which the user (email address) you used > to generate the OAuth2 credentials is associated to. > > To elaborate, if your access to the customer account is through a manager > account (OAuth2 credentials created using a user that has access to your > manager account), this header is required and must be set to the customer > ID of the manager account. You will then need to specify this in your > *ads.properties* file, where your other credentials are placed. You may > refer to this client library setup guide > <https://developers.google.com/google-ads/api/docs/client-libs/java/oauth-installed#step_2_-_setting_up_the_client_library> > for > more information on the said properties file. > > That said, referring to your scenario, there is no way via the API to > extract this programmatically. You will need to identify which account you > used to authenticate and you will have to specify it in your configuration > as discussed in the above. > > Thanks, > > [image: Google Logo] > Peter Laurence Napa Oliquino > Google Ads API Team > > > ref:_00D1U1174p._5004Q274dVu: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/1e5c1ff6-4569-4c99-99d7-b98756a72651n%40googlegroups.com.
