You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 28, 2024. It is now read-only.
Though we should fix the Data Studio dashboard, in the short term I've been exporting to Excel every time I look at my page feedback so I know I'm not seeing repeats/duplicates and I can sort on multiple levels.
The text was updated successfully, but these errors were encountered:
We can embed fully interactive page into datastudio but when you do this it gives you a warning that this content is not part of datastudio and you have to click a proceed button before viewing the dataset.
This warning is easy to bypass but makes the whole experience seem unprofessional. We may want to use this method to improve the experience in the short term for our internal team but shouldn't use it on dashboards for partners.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I saw some of the content team discussing workarounds they had to go through in order to get the per page feedback in the datastudio report.
Would using a different data embed strategy like creating our own widget and embedding it with this technique https://support.google.com/datastudio/answer/9132022?hl=en improve things?
Some complaints:
From @thepegisin:
Talk about per-page feedback in the ca.gov design system meeting reminded me of this thing I wanted to memorialize:
How @m-sullivan7 is working around this:
Though we should fix the Data Studio dashboard, in the short term I've been exporting to Excel every time I look at my page feedback so I know I'm not seeing repeats/duplicates and I can sort on multiple levels.
The text was updated successfully, but these errors were encountered: