Looker Studio Connector - known issues and ETAs

Hello,

Suddenly the report where I was using the official 1.3.3 version of the connector asked me to re-authorise the connector. I followed the steps. In the first step, Looker Studio appears to be already authorised, but in step 2, it keeps giving me the same error, telling me that the login data was correctly sent but they are not valid. I get the exact same error message regardless if I try to re-authorise the connection I was previously using or just create a brand new data source in Looker Studio. Please help, this is impacting a lot the work we do for our client.

Hi @ralucaSD,

Is this error also popping up when you use a new pair of API credentials?

Yes. Both for my old API credentials and new ones (generated last week on 09.01.2025).

I’ll reach out to you in a private message as this looks like an API issue rather than a Looker Studio connector issue.

1 Like

Sorry for bothering here, but my original thread was closed and I cannot answer there anymore: How do I manage multiple clients with the same native Looker Studio Connector 1.3.3?
I tried again now, but it is still impossible to use the connector for more than one client unless I create a separate Google Account for Looker Studio for each client… This is such a nuisance and blocks us from doing anything because once the thing is fixed, we would have to create yet another Connector with yet another Google Account (and then re-do most of the dashboards again).

When can we expect this major problem to get fixed?

The feature is ready, we are testing it and few other things that will be in the release. Around 2-3 weeks but I’ll notify the thread in case we release it earlier.

1 Like

The v1.3.4 update has just been released:

  • Fixed incorrect data parsing when Week and Quarter dimensions are used in charts such as time series or sparkline.
  • Added new ISO Week and adjusted Week dimensions to support different types of week enumeration.
  • Provided support for filters and transformations based on “Custom channel groups” dimensions.
  • Fixed a bug where filters based on transformations would show “Metric may not be used here” error.

Note: make sure to refresh the data source fields:

We are going to release the v1.4.0 update this Friday, around 8:00 AM CET. The update will allow users to connect Piwik PRO API credentials from different instances/accounts without having to create a new Google Account for each one. If you experience any problems with connector authentication, please let me know in a private message. In the event of major problems, we will be prepared to roll back the update and fix any issues. We will add a short guide on how to use the new feature to the Looker Studio connector help center article.

The v1.4.0 update has just been released:

  • You can now associate the Looker Studio connector with multiple pairs of Piwik PRO credentials. This allows you to use different Piwik PRO instances/accounts without the need for having separate Google user accounts. We have updated the help center article to reflect those changes. (cc @loldenburg & @David_Culbertson)
  • We have added a data caching mechanism to speed up the loading of data that has already been requested before. The cache lasts up to 15 minutes and can hold up to 100MB of data.
1 Like

getting this error while trying to connect

@dave,

I got the same error. If it makes any difference, this is for an account with three instances.

Thanks for this important notice! Much appreciated. Do we still need to upgrade the connector (with the usual work associated with upgrading), or is this no longer necessary because you no longer are just a Community Connector?

Hi @dave,

Please provide me with authentication details in a private message. This looks like an incorrect set of API credentials is used.

Make sure you are not entering the username and password but the client ID and client secret as described in the help center article. I know that the labels are misleading but this is something we cannot change because of Looker Studio limitations :frowning: .

The community connector updates itself automatically, just make sure you are not using the “unverified” ones that we’ll try to deprecate as soon as possible.

The multi-instance support feature should not ask you to reauthenticate unless you edit the connection. Even at that point you will be prompted to select the Piwik PRO instance and not enter the API credentials.

1 Like

Ah sorry, I mixed up the terms. Community = officially approved connector, right! Thanks!

AFAIK the proper name is “partner connector”, so also a mistake on my side :sweat_smile: .

Please validate whether the second part applies.

Please provide me with authentication details in a private message. This looks like an incorrect set of API credentials is used.

Make sure you are not entering the username and password but the client ID and client secret as described in the help center article. I know that the labels are misleading but this is something we cannot change because of Looker Studio limitations :frowning: .

@anthonybartczak,

Ah, I see my error and will try again. do i need to generate new credentials or should I re-use the credentials that I put in Looker for connector version 1.0.7?

You can use the same Piwik PRO API credentials.

There isn’t enough clarity in Looker Studio (Google Data Studio) integration | Piwik PRO help center. What happens to an existing connection if I choose it? I’m moving very cautiously because I’ve got more than 60 reports associated with my 1.0.7 connectors!

You can add the v1.4.0 connector as a separate data source, meaning it will be there waiting for you to use it but it won’t automatically replace the data source currently added to your dashboard. This way you can gradually replace the old version, even on chart level. We often use 2+ versions of the connector on a single dashboard for testing purposes.