---
title: "How to Fix a Bad Request Error in Looker Studio"
description: "Why cant I create a report on Looker Studio"
url: https://help.portermetrics.com/en/articles/168-how-to-fix-a-bad-request-error-in-looker-studio
collection: "Troubleshooting"
updated: 2026-10-27
language: en
alternates: [es]
---

# How to Fix a Bad Request Error in Looker Studio

Why cant I create a report on Looker Studio

If you're seeing a "Bad Request" error when trying to connect a data source in Looker Studio, it’s likely due to conflicting Google account permissions. This guide will walk you through resolving the issue step-by-step.

**Step 1: Identify Your Logged-In Accounts**

At the top-right corner of your Chrome browser, check which Google accounts are currently logged in.  
In this example, we see two accounts:

-   **manuela@portermetrics.com**
    
-   **support@portermetrics.com**
    

One of them is active in **Looker Studio**, the other in **Chrome**.

![](https://staticfiles.gleap.io/ghelparticle/4oFKMXUgSA3KPlvizV8hR03qnlKpBihuFQyQlfvZqpfV0OjlDe3grAaD3M8d3xaeEIMCRgW1S9U.png)

**Step 2: Attempt Authorization**

**If you try to connect the data source while connected to two different emails and authorize the connection**

you’ll likely encounter the **Bad Request** error.  
This happens because Looker Studio is unsure whether to authorize via the account connected to Chrome (**Support**) or Looker Studio (**Manuela**).

**Step 3: Switch to the Correct Account**

To fix the authorization conflict:

1.  Go back to Looker Studio.
    
2.  Click on your profile icon (top-right).
    
3.  Switch to the Google account that matches the one logged into Chrome — in this case, **Manuela**.
    

![](https://staticfiles.gleap.io/ghelparticle/xa34VXJuAjc0B47O2zXgoPiu0c3mQNj0EhYXcnQ0f3ngY1FlRxBEl9phd0d477ePKPcE3DiM4q9.png)

**Step 4: Ensure Account Consistency**

Once switched, double-check that the same account is now active both:

-   In Chrome
    
-   In Looker Studio
    

This ensures there’s no permission mismatch.

![](https://staticfiles.gleap.io/ghelparticle/k60Qkr4L7YPQgURUyo7eYH62Vv1S2OqqEAhvQa49FbDV1qT9GX2d9oFJ749iijsFRQUFc8qGbM5.png)

**Step 5: Revoke Old Permissions**

Before retrying, revoke previous access:

1.  Go to **Looker Studio → Resources → Manage added data sources**
    
2.  Click the **three dots** next to the Instagram Insights connector.
    
3.  Select **“Revoke access”** and remove all permissions tied to the wrong email.
    

![](https://staticfiles.gleap.io/ghelparticle/ur87MTukg6MYD5C1iGkN8hc4ZFwTmMiscbVbOAPS0zpwNaf0zhwFfVY2zAToviiv2WGGJA4vYmp.png)

Now, try again:

-   Click **Add data**
    
-   Select **Instagram Insights**
    
-   Click **Authorize**
    
-   Choose the correct account (now aligned across Chrome and Looker Studio)
    

This time, the authorization should go through without errors.

### Step 6: Finalize Your Setup

1.  Select the correct **Facebook profile** (if prompted).
    
2.  Grant all requested permissions.
    
3.  Click **“Add to report.”**
    
4.  Insert a **table or chart** to confirm the data source is working.
    

[Link tutorial](https://app.supademo.com/demo/cm6ikvf1o0ggko60pcbxxqi3a)