Hi Everyone,
We’re currently experiencing an issue with the Piwik pro connectors in Looker Studio. None of the charts are showing any data anymore for many of my customers.
The issue is only existing for our Lookers based on piwik connectors.
Everything was working fine before, and no changes were made on our side concerning the looker.
Is anyone else facing the same issue ?
Any help or insight would be appreciated.
Regards,
Arthur
Hi,
Same here, we’re experiencing a lot of errors (not on all components/dimensions/metrics) not recognising some basic dimensions such as Page URL, Source/Medium, Custom event, etc.
Ex:
Community Connector Error
There was an error caused by the community connector. Please report the issue to the provider of this community connector if this issue persists.
Connector details
Invalid field name: “event_url” is not a valid choice.
Error ID: 25f11c27
Any help or insight would be appreciated.
Best regards,
Lisa
Hello @PixalioneData and welcome to the community
Do you remember when connector was established? Few weeks ago we updated our plugin and unfortunately it required migration to new version.
hello @LisaBlanchard, do you remember when did those errors show up? What was changed in report at that moment?
I have the same issue, running the latest connector and since yesterday get the same error messages - no changes to the report setup.
Same issue here. All 30+ dashboards are broken. Happened yesterday PM.
Didn’t do anything, the dashboards just suddenly looked like this with same error message but different dimension name:
problem exist for our looker dashboards with old 1.3.2 and new 1.4.2 connectors, since 2025-05-26.
only if there is an active filter, we get error messages like:
Invalid field name: “source_medium” is not a valid choice.
Fehler-ID: 410cbcd9
Hi,
We also experience the same errors. All our reports that uses Piwik shows data, but as soon as we add a filter or want to see data of a specific page we’re getting errors.
Ex: Community Connector Error
There was an error caused by the community connector. Please report the issue to the provider of this community connector if this issue persists.
Connector details
Invalid field name: “event_title” is not a valid choice.
Error-ID: 08aefe87
Ex: Community Connector Error
There was an error caused by the community connector. Please report the issue to the provider of this community connector if this issue persists.
Connector details
Invalid field name: “custom_event_category” is not a valid choice.
Error-ID: acddf7e1
Hello @jfidala
Everytime I want to update the new piwik connector version V1.4.2, this error appears :
Do you know what to do in this case ?
Thank you again for your support,
Arthur
Same here. Problem exists for multiple clients, several panels in the dashboards show “See details” errors, and when you click on the error, it gives you a misleading error message, as the custom dimensions that supposedly cause the problem are not even used in the widget nor anywhere else on the dashboard.
My issue is resolved. Filters on reports are working again.
I have the same problem with the dataset in Looker Studio. When I apply a filter, I get the following error message:
Error in community plugin
An error has occurred that was caused by the community plugin. Report the issue to the community plugin provider if it persists.
Connector data
Invalid field name: “event_url” is not a valid choice.
Error ID: 31407395
Hi Everyone,
First of all, I would like to wholeheartedly apologise for the inconvenience caused. We tried to pinpoint the issue today, but it turned out to be quite time-consuming.
What’s more, Google Apps Script — the platform used to run the connector — introduced restrictions to version management, meaning that only one of our developers could introduce fixes. Unfortunately, I could not find any details about this change in the official changelog.
What was the core issue? The most probable scenario is that, when we decided to deploy a new version of our Looker Studio connector, a platform update was running in the background. By “platform”, I mean Looker Studio. The connector update went through without any errors being thrown. However, we have since discovered that while some of the connector files were updated, others remained on the same version.
We’ll definitely look into additional methods of identifying such cases, but this is the first time this has happened to us and it wasn’t picked up by either Looker Studio or our connector. We have also looked through the Looker Studio community forum while debugging the issue. It looks like something was indeed happening to the platform, as different related issues popped up (example 1, example 2).
