API token - basic access

2024-06-10 Thread Analytics Account
Hello, I have applied for basic access to my api token but I have not heard back. This should be very simple. Please approve my application MCC: 554-719-5592 If there is a reason it's not getting approved please tell me what that reason is -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=

Re: api token - basic access

2024-06-11 Thread Analytics Account
sure - Google Ads Manager Account (MCC) ID: 554-719-5592 - No Case ID Thank you for the help On Monday, June 10, 2024 at 1:56:04 PM UTC-5 Google Ads API Forum Advisor wrote: > Hi, > > Thank you for contacting the Google Ads API support team. > > The access requests ar

Re: api token - basic access

2024-06-12 Thread Analytics Account
I've reached out to the API compliance team and I still haven't heard back. Why is this so hard? It's such a simple request! On Tuesday, June 11, 2024 at 6:59:24 AM UTC-5 Google Ads API Forum Advisor wrote: > Hi, > > Thank you for reaching out to the Google Ads API support team. > > I understan

Token Auth

2024-06-26 Thread Analytics Account
A few months ago I created an MCC and developer token for my business. I didn't realize we already had an MCC for our business. Now I've created a token within the correct MCC but Google will not allow me to use it in the same GCP project as the original token because they have the same corporat

Re: token auth

2024-07-01 Thread Analytics Account
No! The Google Ads Compliance team told me to reach out to you. Stop sending me in circles. This is stupid. It's a simple request On Monday, July 1, 2024 at 4:40:27 AM UTC-5 Google Ads API Forum Advisor wrote: > Hi, > > As the issue is related to the developer token, I would recommend you > r

Re: token auth

2024-07-01 Thread Analytics Account
You can ignore that non-English message. But PLEASE delete my MCC: 549-884-6662 And grant MCC: 554-719-5592 token to be authenticated for GCP project: 452988213376. I know this isn't a hard request for you. Please stop sending me in circles. I've already reached out to the API compliance team an