# Looker Studio Connector - known issues and ETAs **URL:** \ **Category:** API & integrations\ **Created:** [October 20, 2023, 3:18am UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068 "2023-10-20T03:18:17Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Emilia](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/emilia/32/2361_2.png) [@Emilia](https://community.piwik.pro/u/Emilia)\ **Post date:** [October 20, 2023, 3:18am UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/1 "2023-10-20T03:18:17Z")
Hello Guys! I’m a Product Manager at Piwik PRO, now responsible for the maintenance and development of the Looker Studio Connector for Piwik PRO Analytics. In order to meet our client’s needs and expectations, we’ve just launched a project that aims to greatly improve the quality and usability of the Looker Studio data connector. To ensure access to information, transparency and to make our lives easier, I’d like to publicly share a list of known issues connected with Looker Studio, along with their statuses. I’ll be posting updates, adding estimated times of delivery when we set one. Thank you very much for all your patience and understanding! In progress: 1. Google Ads - Using Google Ads metrics/dimensions crashes connector **(mid-November 2023)** (Related posts: [No Google Ads Campaign ID in Looker Studio / other Google Ads data breaks as soon as it is filtered](https://community.piwik.pro/t/no-google-ads-campaign-id-in-looker-studio-other-google-ads-data-breaks-as-soon-as-it-is-filtered/2813)) 2. Average page views in session shows wrong numbers **(mid-November 2023)** ([Average page views in session does not work in Looker Studio](https://community.piwik.pro/t/average-page-views-in-session-does-not-work-in-looker-studio/1954)) 3. Conversion rates on scorecards show wrong numbers **(mid-November 2023)** ([Conversion rate issue in Looker Studio](https://community.piwik.pro/t/conversion-rate-issue-in-looker-studio/2993)) 4. Sum of product quantity, sum of product revenue show different numbers in LS and PPAS **(mid-November 2023)** ([Sum of Product Revenue and quantity not the same in Looker Studio - #6 by joao](https://community.piwik.pro/t/sum-of-product-revenue-and-quantity-not-the-same-in-looker-studio/2290/6) 5. IN\_LIST filter operator should handle exclusions **(mid-November 2023)** 6. Dashboards for Meta Sites show slightly wrong numbers (investigation pending, ETA unknown). In the queue: - Pie charts show wrong numbers/Limiting the number of slices by filtering breaks the charts ([Device type data shows "other" on Data Studio chart](https://community.piwik.pro/t/device-type-data-shows-other-on-data-studio-chart/2768)) - Using the “Country” dimension with pie charts causes issues ([Chart is adding total as a value - #5 by dave](https://community.piwik.pro/t/chart-is-adding-total-as-a-value/2432/5)) - Date/timestamp handling - improve/extend options ([Piwik & Looker Studio - Breakdown per month - #2 by Ralf](https://community.piwik.pro/t/piwik-looker-studio-breakdown-per-month/2538/2)) - Breakdown dimensions break the connector - Transformations/aggregations - extend the number of available options, document limitations - Filtering by City name and Region name - Issue with filtering by Website name in Meta sites - Better error handling, client-side validation of the request (before actual execution) - New end-user documentation - Partial RegEXP matches - ([Looker studio REGEXP issue](https://community.piwik.pro/t/looker-studio-regexp-issue/1643), [Looker Studio Connector: Regexp Matches don't work - #10](https://community.piwik.pro/t/looker-studio-connector-regexp-matches-dont-work/1472/10)) Waiting for changes in the product: 1. Add the connector to the official Google Gallery and make updates smooth and easy (Q1 2024) (Change of authentication method required) Known facts that are not bugs: - All metrics and dimensions appear as green fields in the Looker Studio connector for Piwik PRO - Google changed the way they treat data sources like Piwik PRO, and now lists both metrics and dimensions as “green” fields, which were previously reserved only for dimensions. After dropping any metric listed as a green field into the “Metrics” definitions, it will change the color to blue and become a proper metric. ---
**Author:** ![loldenburg](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/loldenburg/32/965_2.png) [@loldenburg](https://community.piwik.pro/u/loldenburg)\ **Post date:** [October 20, 2023, 6:33am UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/2 "2023-10-20T06:33:27Z")
Thanks. Please keep us updated. ---
**Author:** ![Emilia](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/emilia/32/2361_2.png) [@Emilia](https://community.piwik.pro/u/Emilia)\ **Post date:** [November 24, 2023, 3:59pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/4 "2023-11-24T15:59:46Z")
Hello Guys! I know there’s a lot of you waiting for an update here. We were working hard to meet the deadline and your expectations, and we’re finally ready to announce that a new version of the connector is ready. It will be published publicly on Monday, November 27th. Here’s the list of changes that we managed to deliver: - Fixed Google Ads metrics/dimensions - Improved date/timestamp handling, added support for all date groups in reports like hour of day, day of week, week, month etc. - Fixed ‚Average page views in session’ metric - Fixed exclusion filters for is null/empty/equals to 0 conditions - Added support for exclusions with IN\_LIST filters - Added handling complex conditions with IN\_LIST filters (Example: Exclude Country in Denmark,Germany unless Device Type in Smartphone,Tablet) - Added support for all transformations for eCommerce metrics (Like Sum of product revenue (Orders), Average Revenue, Sum of product quantity, Median product quantity etc.) - Removed the product scope dimensions which are not available in Queries API and were breaking the connector (Like Product revenue (Array)) - Fixed bounce rate showing wrong numbers. We’re not stopping here - the next versions will now be released regularly. Stay tuned! ---
**Author:** ![Emilia](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/emilia/32/2361_2.png) [@Emilia](https://community.piwik.pro/u/Emilia)\ **Post date:** [November 27, 2023, 5:17pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/5 "2023-11-27T17:17:43Z")
Hello! A new version of the Looker Studio connector is already [here](https://lookerstudio.google.com/datasources/create?connectorId=AKfycbyZ_UqL9hB9qTsDtyN9Zkp0K8lJSgl8mmrb5soohN3CAUjkAvNRwMWnSmywQGhPl9dgiQ) ✨ 🎉 🎊 The final changelog: - Fixed Google Ads metrics&dimensions - Improved date/timestamp handling, added support for all date groups in reports like hour of day, day of week, week, month etc. - Fixed ‚Average page views in session’ metric - Added filters for ‘is null’/empty/‘equals to 0’ conditions (for both metrics and dimensions) - Added support for exclusions with IN\_LIST filters - Added handling complex conditions with IN\_LIST filters (Example: Exclude Country in Denmark,Germany unless Device Type in Smartphone,Tablet) - Added support for all transformations for eCommerce metrics (Like ‘Sum of product revenue (Orders)’, ‘Average Revenue’, ‘Sum of product quantity’, ‘Median product quantity’ etc.) - Removed the product scope dimensions which are not available in Queries API and were breaking the connector (Like ‘Product revenue (Array)’) - Fixed bounce rate showing wrong numbers. Enjoy! 😊 ---
**Author:** ![Emilia](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/emilia/32/2361_2.png) [@Emilia](https://community.piwik.pro/u/Emilia)\ **Post date:** [December 21, 2023, 5:15pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/6 "2023-12-21T17:15:55Z")
Hello! I’d like to drop a little holiday gift 🎅 and share a new [Looker Studio connector version 1.2.0](https://lookerstudio.google.com/datasources/create?connectorId=AKfycbxNxIuiMXEbmMIIjbTOpBw2HbpQ5sGgxal1rtxVpPhv4lsk8Scz_xfFyk-TASjkJ7efCg&authuser=0) with you. Here’s a list of changes we managed to introduce: - Added support for filters with ‚Equal to (=)’ and ‚Contains’ operators for enum type fields (Disclaimer - Location dimensions (Country, City) will work like ‚Starts with’ filter when the ‚Contains’ operator is chosen in Looker Studio. This limitation will be resolved in Q2 2024) - Added ‚Goal ID’ and ‚Goal UUID’ dimensions (Disclaimer - Those fields support only the ‚equal to’ operator due to API limitations) - Fixed pie/donut charts showing wrong numbers - Fixed calculations after changing the number of pie/donut slices in charts - Fixed using dimensions like ‚Country’, ‚Browser name’, ‚Device type’ with pie/donut charts - Fixed Breakdown dimensions breaking the connector - Fixed filtering by Website name (and other enum type fields) in Meta sites - Added end user messages for a group of known limitations (Like [mixing some specific Google Ads metrics&dimensions with specific Analytics metrics&dimensions](https://help.piwik.pro/support/reports/about-metrics-and-dimensions-from-google-ads/)) - Added support for more than 1000 websites/meta sites in the Site selector - Added limit of 100 results for enum type fields. Additional important info for the above change log (which will also be included in the [official connector manual](https://help.piwik.pro/support/integrations/looker-studio-integration/)): - The RegExp and ‚Starts with’ (which in fact is also a RegExp) filter types are still not supported. Our Analytics team is running research on the possibility of implementing it in our API, which would open the way to add it in Looker Studio. - Please, bear in mind that filters in Looker Studio are case sensitive (so to reflect some operators marked as ‚case insensitive’ in Piwik PRO UI, you’ll have to add additional conditions in Looker Studio). - When using filters on enum type fields, we have introduced a limit of 100 results. This performance enhancement helps to provide faster load times and a more efficient browsing experience. If you encounter a message indicating that too many values matched the filter, please refine your search criteria to continue. And last but not least, this is another batch of fixes but we still have some points in our backlog that we’re going to take care of in the upcoming releases. If you find something that is still not working properly and it hasn’t been mentioned in this post, please report it here in the community forum or to our support. We would highly appreciate also positive comments, so if you have any thoughts on the new connector, don’t hesitate to share. Thank you very much! ---
**Author:** ![Emilia](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/emilia/32/2361_2.png) [@Emilia](https://community.piwik.pro/u/Emilia)\ **Post date:** [June 11, 2024, 12:53pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/7 "2024-06-11T12:53:26Z")
Hello! I’m pleased to share that we have released a new [Looker Studio connector version 1.3.0.](https://help.piwik.pro/support/integrations/looker-studio-integration/#update-looker-studio-integration) Here’s a list of changes we’ve added this time: - Improved the data and charts loading performance - Added API token caching to reduce the number of token requests - Added support for specific goal metrics (instead of filtering out a specific goal while looking for example at the 'Goal conversion rate’ metric, you should choose a metric 'XYZ goal conversion rate’) - Added support for ‘Unique count of’, ‘Min’, ‘Max’, ‘Average’, ‘Sum of’ and ‘Median’ transformations for all eligible columns - Improved calculations of some aggregations for scorecards (they’re now less prone to user errors) - Increased the current limit of 100,000 returned rows to a 1,000,000 returned rows (Looker Studio limitation - [Community Connector API Reference  |  Community Connectors  |  Google for Developers](https://developers.google.com/looker-studio/connector/reference#getdata)) - Added support for RegExp Contains (RegExp partial match) and RegExp Match (RegExp exact match) filters (Note - Those filters are not supported for enum type columns (like Country, City etc.)) - Fixed filtering for transformed fields (e.g. Page Path). You should also be informed that we are actively working on bringing the connector to a state where all Google’s requirements would be met and we could publish it as an official connector in the Looker Studio Gallery. This would allow for more smooth updates. Now, you should still remember [to follow this instruction for each of your dashboards](https://help.piwik.pro/support/integrations/looker-studio-integration/#update-looker-studio-integration) if you want to start using the new version of our connector. I would also like to emphasize that Looker Studio users should be aware that in complex dashboards there might occur errors caused by exceeding the limitation put on Looker Studio by Google. The limitation is for simultaneous request executions per user and we have no influence on that limit. As a solution, Google provided the following recommendations: ![image.png](https://mail.google.com/mail/u/0?ui=2&ik=8c5b3c2878&attid=0.1&permmsgid=msg-a:r5302685459844155397&th=19007e7935940d72&view=fimg&fur=ip&sz=s0-l75-ft&attbid=ANGjdJ97PyceergLrzHARRSgMYx30cRW5Vrn7k07nREootdX9oS-LszegDGU-pxI0CPONAgCYsyyYgqjxZxP0bQhoNoh3dSyW5KzBbw9lFiQ_I5ezRksrvGy2e2Hujg&disp=emb&realattid=ii_lxajw2wc0) I hope you’re going to enjoy the new features. We would appreciate your feedback and suggestions for further improvements 😊 Thank you very much! ---
**Author:** ![David\_Culbertson](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/david_culbertson/32/1479_2.png) [@David\_Culbertson](https://community.piwik.pro/u/David_Culbertson)\ **Post date:** [June 13, 2024, 10:55pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/8 "2024-06-13T22:55:31Z")
This is good news but… Does this mean that I have to redo all of data connections in Looker? Most of my Piwik Pro data sources have custom metrics or dimensions. Will I have to redo those? ---
**Author:** ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)\ **Post date:** [June 14, 2024, 9:58am UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/9 "2024-06-14T09:58:53Z")
> [@David\_Culbertson](#): > > Does this mean that I have to redo all of data connections in Looker? Most of my Piwik Pro data sources have custom metrics or dimensions. Will I have to redo those? Hi David, Yes, in most cases the data sources would have to be reconnected. Once the connector becomes official, this should happen automatically. ---
**Author:** ![David\_Culbertson](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/david_culbertson/32/1479_2.png) [@David\_Culbertson](https://community.piwik.pro/u/David_Culbertson)\ **Post date:** [June 14, 2024, 12:25pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/10 "2024-06-14T12:25:33Z")
Ugh, I’ve got TONS of blended data metrics and they’d all have to be redone. Will the old version continue to work? ---
**Author:** ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)\ **Post date:** [June 14, 2024, 12:44pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/11 "2024-06-14T12:44:34Z")
> [@David\_Culbertson](#): > > Will the old version continue to work? Yes, it’s just missing the new features and fixes. ---
**Author:** ![Martin](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@Martin](https://community.piwik.pro/u/Martin)\ **Post date:** [August 12, 2024, 12:26pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/12 "2024-08-12T12:26:25Z")
There is still a massiv error using Looker with the Piwik connector. Still the revenue differs from Piwik and Looker. On a yearly scale I am missing 4 million € that are not shown. I just updated the connector 10 min ago. Best part … the bar charts show higher revenue than the overview boxes … still not the correct value. ---
**Author:** ![Martin](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@Martin](https://community.piwik.pro/u/Martin)\ **Post date:** [August 12, 2024, 1:00pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/13 "2024-08-12T13:00:21Z")
Edit : I put a solution in this post [Sum of Product Revenue and quantity not the same in Looker Studio - Reports and working with data - Piwik PRO Community](https://community.piwik.pro/t/sum-of-product-revenue-and-quantity-not-the-same-in-looker-studio/2290/8) Really should not be a users job to fix basic stuff ---
**Author:** ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)\ **Post date:** [August 12, 2024, 1:17pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/14 "2024-08-12T13:17:31Z")
Hi @Martin! We are currently working on a fix for this. It’s a result of an additional aggregation made by Looker Studio: > [@Looker Stuido Visitor count aggregation error?](https://community.piwik.pro/t/looker-stuido-visitor-count-aggregation-error/4173/5): > > Hi @Dave_Wyborn! Just FYI - we’re still looking into this issue but it looks like it’s connected to how we pull metrics that are later aggregated (e.g. avg, min, max) inside Looker Studio. I will probably add more context once we confirm the theory. And you are correct - this issue is indeed limited to certain metrics. ---
**Author:** ![muttley90](https://avatars.discourse-cdn.com/v4/letter/m/7cd45c/32.png) [@muttley90](https://community.piwik.pro/u/muttley90)\ **Post date:** [August 30, 2024, 8:14am UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/15 "2024-08-30T08:14:07Z")
New version 1.3.1, and still visitors total in Looker and Piwik is different: same range, no filter, looker shows 80K visitors while in Piwik only 65K. Version 1.2 at least showed the same value as Piwik interface. ---
**Author:** ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)\ **Post date:** [August 30, 2024, 8:57am UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/16 "2024-08-30T08:57:57Z")
Hi @muttley90, you are correct - we have not yet updated this behaviour as it will most likely require some changes to the core product and its API. Sorry for the inconvenience. I will update this thread when the fix is released. In the meantime, you can use the “count distinct” aggregation on visitor ID: > [@Looker Stuido Visitor count aggregation error?](https://community.piwik.pro/t/looker-stuido-visitor-count-aggregation-error/4173/7): > > In the meantime, you can try using the visitor ID dimension and “Count distinct” aggregation, it should show the proper value. ---
**Author:** ![Martin](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@Martin](https://community.piwik.pro/u/Martin)\ **Post date:** [September 11, 2024, 1:35pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/17 "2024-09-11T13:35:13Z")
Here are some more issues with 1.3.1 [Looker Connector 1.3.1 Dashboard Issues - API & integrations - Piwik PRO Community](https://community.piwik.pro/t/looker-connector-1-3-1-dashboard-issues/4395) ---
**Author:** ![JanS](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@JanS](https://community.piwik.pro/u/JanS)\ **Post date:** [September 19, 2024, 6:10am UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/18 "2024-09-19T06:10:11Z")
Is it only me or is there a problem regarding goal conversion rates? I have an account with two goals. Looking into conversion rate in piwik it’s for 3 days of testing 0.06% and when looking in LS it’s 0.16% (same amount of sessions and conversions both places when I look at those numbers). Any suggestions to why? ---
**Author:** ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)\ **Post date:** [October 30, 2024, 2:45pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/19 "2024-10-30T14:45:46Z")
Hi Everyone, The 1.3.2. and 1.3.3 versions introduced changes to the querying mechanism for some of the metrics/dimensions available in the connector. This should resolve issues with unnecessary aggregations (e.g. Visitors, Goal conversion rate, Bounce rate) and therefore discrepancies between LS reports and Piwik PRO Analytics UI for these cases. ---
**Author:** ![Toon\_iO](https://avatars.discourse-cdn.com/v4/letter/t/6bbea6/32.png) [@Toon\_iO](https://community.piwik.pro/u/Toon_iO)\ **Post date:** [December 11, 2024, 11:37am UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/20 "2024-12-11T11:37:19Z")
I’m running into issues with the dimensions “Goals converted in session” and “Goals converted in session (uuid)”. The “Goals converted in session” dimension always seem to give an error (ID e407b1cd) and the “Goals converted in session (uuid)” dimension massively underreports the amount of sessions compared to the goal report in Piwik. ---
**Author:** ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)\ **Post date:** [December 11, 2024, 1:23pm UTC](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068/21 "2024-12-11T13:23:54Z")
Hi @Toon_iO, Would you mind sharing a screenshot of the Piwik PRO report that you are trying to replicate/comparing Looker Studio to? Either here or in a private message. [Next page](https://community.piwik.pro/t/looker-studio-connector-known-issues-and-etas/3068.md?page=2)