Forum Discussion

pawankarki23's avatar
pawankarki23
Frequent Visitor
1 year ago
Solved

PowerBI Service Scheduled refresh error for Google Analytics

Hi Everyone,    I am connecting to Google Analytics from PowerBI using GA connector v2. The connection works fine when I use the PowerBI Desktop to create the report.    But, one I upload the rep...
Need Help
  • COS019970's avatar
    COS019970
    1 year ago

    Hi all, this has been resolved by devs it seems. I went to check if I could put my report back on scheduled refresh just there and it is now working again. So, the token issue that I am assuming was preventing the connection from Google Analytics to Power BI is now working fine. 

Anonymous's avatar
Anonymous
Not applicable
1 year ago

Hi pawankarki23,

As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.

If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.


If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.

COS019970's avatar
COS019970
Frequent Visitor
1 year ago

Hi , 

I am after encountering the same issue. I have Power Bi connected to Google Analytics too.  The connection works fine when I use the PowerBI Desktop to create the report and it publishes to the web fine. It was working fine too with the Scheduling refresh on the web service of Power BI up until last Wednesday. It stopped connecting on Data source credentials part and I am getting this error:

 

Failed to update data source credentials: We found an unexpected character in the JSON input.Hide details

Activity ID:7da358fb-3efb-414d-9fab-0dd7af2ed6c1
Request ID:b71e5b5e-c5ab-8cd6-cd7a-bf229353c122
Status code:400
Time:Thu May 08 2025 16:46:17 GMT+0100 (Irish Standard Time)
Service version:13.0.25830.39
Client version:2504.4.23986-train
Cluster URI:https://wabi-north-europe-k-primary-redirect.analysis.windows.net/

 

I have tried all of these suggested solutions and none of them have worked: 

✅Suggested Fixes

1. Re-authenticate GoogleAnalytics Connector

  • In the Power BI Service, go to:
    Settings > Datasets > [Your Dataset] > Data source credentials.
  • Next to GoogleAnalytics, click Edit credentials.
  • Use OAuth2 as the authentication method.
  • Re-enter your Gmail credentials and ensure that the correct permissions (e.g., analytics.readonly) are granted.

    2. Use Organizational Account (Not Anonymous/Web API)

    Ensure you're not using the “Anonymous” or “Web API” options during authentication. These may generate incorrect request payloads that include invalid JSON headers.

    3. Clear & Reset Credentials

    Sometimes Power BI caches problematic tokens. Do the following:

    • Remove credentials by choosing Clear permissions.
    • Reconnect with the correct authentication method.

      4. Check Gateway Configuration (if used)

      If you're using a Power BI Data Gateway, ensure:

      • The gateway is online and up to date.
      • You’ve correctly configured the data source mapping in the gateway for GoogleAnalytics.

        5. Validate Dataset JSON Config

        If you have access to the PBIX file:

        • Open it in Power BI Desktop.
        • Go to Transform Data > Data source settings, and ensure the URL or query you’re using for GoogleAnalytics is correct and does not contain invalid characters.
        • Re-publish the dataset.

          🛠Additional Debugging

          • If the problem persists:
            • Test a clean Gmail connector setup in a new Power BI report to isolate the issue.
            • Ensure your Google Analytics account is still active and hasn’t been transitioned to GA4 (which may require different connector logic).
            • Check the Google API Console for any blocked API requests or permission errors.

pawankarki23