-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grouping Failure in Looker Studio with Matomo Connector #29
Comments
@njoyhwsm What version of Matomo are you connecting to? |
We use Matomo Cloud. So I guess it is the latest version. |
I see, yes, this is a known issue with the connector and Matomo at present. More details on the work needed to add this and details on a workaround are here: #3 |
Thank you for these links, they have helped me understand that by re-aggregating the appropriate metric, the values will indeed be grouped as desired. :) |
There is a critical issue with the Matomo Connector used in Looker Studio where identical values from calculated fields are not being grouped as intended across all visualizations, including pie charts, tables, and others. This bug disrupts data analysis, as each instance of a value is treated as unique, leading to a fragmented and misleading representation of the data.
Steps to Reproduce:
Expected Behavior:
The visualization should consolidate identical values into single groups for clear and accurate data representation, irrespective of the type of visualization used.
(see Screenshot: left: Matomo Connector right: GA4 Connector)
Actual Behavior:
Despite the use of calculated fields designed to group identical values, the visualizations treat each instance as unique. This results in an inflated number of groups and an erroneous depiction of the dataset. This issue is observable in pie charts, where it generates an excessive number of slices, as well as in tables, where rows that should be combined are instead displayed separately.
Impact:
This bug severely affects the usability of Looker Studio with the Matomo Connector for meaningful data analysis and visualization, as it prevents accurate aggregation of data points.
Additional Information:
The problem persists regardless of the visualization format.
This is not an isolated issue; it has been replicated with various data dimensions.
The text was updated successfully, but these errors were encountered: