Data Studio troubleshooting

Data Studio OAuth Error: Redirected Too Many Times

If the browser keeps redirecting during authorization, one possible cause is being signed into several Google accounts in the same browser session. Google's Apps Script platform, which Adzviser's community connectors use, has known limitations with multiple Google accounts.

For a related report, see this Google Docs Editors Community discussion about the “Redirected too many times” error in Apps Script.

Try a separate Chrome profile

A separate profile lets you retry with a fresh browser session and keep a dedicated place for Data Studio. Your existing profiles and their saved data remain available.

1. In Chrome, select the profile icon in the browser toolbar, then Add Chrome profile. Give it a recognizable name, such as Data Studio.
2. In the new profile, open Data Studio and sign into only the Google account you use for Data Studio. For an existing report, use an account that has access to that report. Keep other Google accounts in your original profile.
3. Open the Adzviser connector you need in this profile and start authorization again. Start from the connector rather than copying an old authorization or callback URL from the failed attempt.
4. When Adzviser opens, sign into the Adzviser account containing your workspaces. Follow the authorization steps and select Complete authentication with Data Studio. Keep the entire flow in this profile.
5. When you see Success! You can close this tab., return to the Data Studio tab and continue the connection.

If this works: You can keep using the dedicated profile for Data Studio. The result suggests the original browser session or settings contributed to the problem; it does not prove which setting caused it. You do not need to delete your other profiles or recreate your reports.

Optional quick test: Incognito

Google also recommends trying a private window with only the intended Google account signed in. With no other Incognito windows open, start a new Incognito session and repeat the authorization flow there.

Chrome blocks third-party cookies in Incognito by default, which can affect sites that rely on them. A failed Incognito attempt does not rule out a browser-session issue; try the separate regular profile above if you have not already.

Optional: Remove unused Chrome profiles

If you prefer to remove extra Chrome profiles you no longer use, follow the steps below before retrying the connection. Removing another profile does not sign extra Google accounts out of the profile you keep, so this is not a confirmed fix for the redirect error.

Before deleting: Chrome removes that profile's bookmarks, history, saved passwords, and settings from the computer. Back up anything you need, or verify that it is saved in your Google Account and accessible elsewhere, before proceeding. Unsynced data can be lost. See Google's profile-removal guidance.

1. Select the profile icon in Chrome's browser toolbar.
2. Open Manage Chrome profiles. Older Chrome versions may call this Manage People.
3. Find an unused profile you own and want to remove. Check its name carefully so you keep the profile you use for Data Studio.
4. Open that profile's three-dot menu and select Delete. In older versions, this may be labeled Remove This Person. Review Chrome's deletion warning and confirm only if you have saved the data you need.
5. Open the profile you are keeping. If it is signed into several Google accounts, use the Google website's account menu to sign out of all of them, then sign back into only the account you use for Data Studio.
6. Reopen the Adzviser connector and restart authorization in that profile.

You can also try step 5 on its own to address multiple Google sign-ins without deleting a Chrome profile.

If authorization still fails

If the redirect loop also happens in a fresh regular profile with one Google account, contact Adzviser support before reinstalling the connector. Include:

• The connector you selected, such as Facebook Ads or Shopify.
• The exact error message, or a screenshot of it.
• Whether it fails before the Adzviser sign-in page, during Adzviser sign-in, or after completing authorization.
• The hostname shown on the error page, such as script.google.com or adzviser.com. Send the hostname only; authorization URLs can contain temporary sign-in information.
• Whether the same error occurs in the new Chrome profile and, if tried, Incognito.

These details help us identify which part of the connection is failing. A redirect error alone is not enough to confirm an account conflict or a connector problem.