There are two ways to connect Google Ads. Most people sign in with Google from their Property: choose Connect Google, sign in, approve access, then pick your ad accounts. If signing in gets in the way, you can give us manager access instead.
Most Google connect problems come from a stale Google sign-in, not from your Ads account. Before you start, sign out of every Google account (not just switch accounts), open a private or incognito window, sign in to Ads Arsenal there, and choose Connect Google while your Google sign-in is fresh.
You choose Connect Google, Google asks you to confirm with your passkey (fingerprint, face or device PIN), and instead of the approval screen you land on a Google page that says something like "You're all set". Nothing connects, and trying again repeats the loop. This happens when your Google sign-in session is stale, most often right after your Workspace admin changed sign-in rules. Work down this list, cheapest step first:
Do not delete and recreate your passkey. It feels like the obvious reset, but a new passkey can restart Google's security hold on your account and make the loop worse.
The person who connects must sign in with a Google account that can open your Google Ads account, either directly or through your agency's manager account. Read-only access is enough to connect; applying the changes you approve needs Standard or Admin access. Being an admin of your company's Google Workspace is not needed and is not enough on its own. Not sure who that is? In Google Ads, open Admin, then Access and security, and look at the list of users.
Ads Arsenal asks Google for one permission only: access to your Google Ads account. It never asks for your email, your files or anything else. One person connecting is enough for everyone in your organization.
Until Google finishes reviewing Ads Arsenal, Google may show a screen that says "Google hasn't verified this app". To continue, choose Advanced (bottom left of the warning), then Go to Ads Arsenal. The next screen shows the single Google Ads permission you are granting, and you can take it back at any time at myaccount.google.com/permissions. If there is no Advanced link and Google says access is blocked, your Workspace restricts outside apps; see the next section.
If your company uses Google Workspace, your admin may limit which outside apps can use company Google accounts. Then Google stops the connect on its own screen with a message like "Access blocked" or "admin policy prevents you from signing in", and Ads Arsenal never hears about the attempt. Your admin can allow it:
259663602950-vpo98cion0vavrc4t5njc1c618c2gju1.apps.googleusercontent.comGoogle says this can take up to 24 hours to apply, though it is often much quicker. Then connect again from a fresh window.
The connect is an ordinary redirect to Google and back in the same tab, so it usually works with strict browser settings. If Google never appears, or you bounce straight back with an error, try once in a private window with extensions off. If that works, allow this site and accounts.google.com in your usual browser.
If approval works but your Ads account is not in the picker, the Google account you signed in with cannot open that Ads account. Check by signing in to Google Ads as that user. If you cannot see the account there, ask an Ads admin to invite you (in Google Ads: Admin, then Access and security), accept the invite, and connect again. Accounts under a manager account are listed with the manager's ID beside them. Cancelled and suspended accounts are not listed.
If you would rather not sign in with Google here, we can connect through Google's manager account link:
You can remove the link at any time from the same Managers tab.
Email bishop@battlebridge.com with the step you are on and the exact words of any error (a screenshot is perfect). A person reads it.