Interconnect more analytics features
@EDsCODE is already working on this.
Since Apr 15, 2021.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Is your feature request related to a problem?
We have quite a few features which directly relate to analytics
- Insights
a. Trends
b. Funnels
c. ... - Sessions
- Cohorts
- People
- Events
- Actions
- Feature flags
Quite a few of them are already directly interconnected:
- You can jump from most trend graphs to sessions
- We list events, sessions and now cohorts in persons pages
- Can jump to person page from insights, cohorts, sessions and events
- Can jump from events table to insights for that event
However a lot of interconnections are missing, for example:
- Being able to define a cohort from a trends graph
- Going to people/sessions in some trend visualizations: "Bar charts by value" and "table/pie" charts (#3825)
- Jumping to a session (recording) from funnel to see who dropped off
- Jumping from feature flags to insight graph showing how the feature is doing when the flag is on vs off or to sessions. Might be "A/B testing" land but still
- Jumping from sessions to graphing the "same" filter in insights (#4038)
- Defining a cohort from people who completed/dropped off in funnel step X
- Jumping from cohorts to sessions (#4008)
- Viewing person activity in insights (#4033)
- Jumping to insights from action definition (#3996)
- ...
Each of these interconnections make going from "hmm that's weird" to insights much easier, currently it's too much work to jump between all these different things.
Describe the solution you'd like
Universal way to represent "view/analyze in X" in different views.
Ideally one that's mostly consistent throughout different parts of the app - we currently have a mixture of tabs, popups when you click on things and tables underneath things.
Additional context
Not sure what the way is (cc @corywatilo, @lottiecoxon) - this is an interesting design challenge.
cc @paolodamico and @EDsCODE - we've discussed this in the past
cc @kpthatsme - you're working a lot with data, do you think this would make sense/improve both your usage and no of learnings?
Screenshots
Some ideas from other products:






Thank you for your feature request – we love each and every one!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.