Google Workspace Email Redirected to 404 When Creating a Google Ads Account

Has anyone had a similar situation and resolved it?
I’m having a problem accessing Google Ads with my Google Workspace email.

“404 - The requested URL was not found. Let’s get back to business.” - This is the error I get, and researching this shows it is a google workspace glitch

So far, I have:

• Cleared the browser cache and cookies
• Tried accessing Google Ads through an MCC
• Tried to login incognito
• Created a separate OU for the email, confirmed Google Ads and “Additional services without individual control” are enabled

Every step I've taken so far still returns the same 404 error.

I know another workaround is to create the Google Ads account using a personal Gmail address and then invite the Workspace email. I would prefer not to involve a personal email at this point.

Has anyone experienced a similar situation and how did you resolve it?

This is what the error looks like

Bad antidetect browser plus or bad proxies

I've changed antidetect and it was solved. In old antidetect I need to have strong session with a lot of cookies to pass 404

That's very odd, could you try to contact google or would it be too risky? What are your goals?

Fostack said:

That's very odd, could you try to contact google or would it be too risky? What are your goals?

Click to expand...

I wouldn’t contact google but from what I have seen, people have had this error for years and there is still no fix

I went ahead and created a temporary workspace with a new domain and it got access to google ads.

Not the solution I need so I'm still open to hearing from those who've experienced something similar and how they resolved it

bwman said:

I wouldn’t contact google but from what I have seen, people have had this error for years and there is still no fix

I went ahead and created a temporary workspace with a new domain and it got access to google ads.

Not the solution I need so I'm still open to hearing from those who've experienced something similar and how they resolved it

Click to expand...

How can such a company still have stupid bugs like that..