Improve onboarding demo data

[paolodamico]

After the last PR of the series (#3174) of #2822, we still need to do a significant improvement to demo data & dashboards. Right now we drop the user into a very basic environment that's lacking a ton of more useful data, we particularly need to leverage the information from the personalization screen to show information that will be most relevant for the user.

EDIT: Rest of improvements to the new onboarding experience spun out to #3351. This issue now only pertains to improving the onboarding demo data.

[macobo]

For improving demo data, let's mock up (e.g. on paper) a couple dashboards/graphs we want to show and reverse-engineer the demo data generation from that. @paolodamico or @yakkomajuri would you be up for doing the mock graphs?

[paolodamico]

As discussed on Slack, @yakkomajuri is helping us out mock up the different dashboards we'll show as part of the demo data generation. Yakko as additional context, I think it's important to consider which dashboards we want to show depending on which type of user / products the user selected (e.g. we wouldn't show you a mobile app dashboard if you don't have mobile apps, etc.), as well as maybe which dashboards we want to highlight/pin.

[yakkomajuri]

Ok so a prelude here:

The demo data generation I built was made to allow the creation of nice dashboards from it. I just didn't put as much focus (lack of time) on dashboard panel generation when I built it, but manually built dashboards on the playground. I'd suggest you check them out.

Completely agree with you @paolodamico on making sure different profiles see what's most relevant to them. The current data essentially covers 3 main areas: mobile, web, and sales.

Another point is that we should make sure users see all chart types, different colors, different sizes, etc. It's also worth having some cohorts, feature flags, etc.

Inspiration Screenshots

EDIT: Just noticed with these screenshots that we might have a problem with our annotations UI!

Further Panel Examples

To prevent repetition with multiple screenshots of the same thing with different labels, here are some descriptions of panels I'd like to see for different user types that cannot already be found on the playground's dashboards:

Engineer

Exceptions over time

• Linear graph
• Weekly or monthly
• Showing some sort of clear trend (up or down)
• Dependency: Need to generate some $exception events

Exceptions breakdown by type

• Table
• A frequency table of exceptions by type using breakdown
• Dependency: Need to generate some $exception events

Marketing

Marketing conversion funnel by source

• Two funnels side-by-side measuring conversion across 2 or 3 steps
• Step 1: Pageview with UTM tag like utm_source=twitter
• Step 2: Looked at pricing page
• Step 3: Sign up
• Dependency: UTM tags in events

Breakdown of signups by initial referrer

• Table form
• Breakdown of 'active users' by user property 'Initial referring domain'
• Dependency: 'Initial referring domain' in user props

Customer Success

Some retention metric (e.g. Hogflix watched movie)

• Can be based on the purchase retention already available from the demo data
• Recurring retention on a monthly basis for 'purchase' events on the playground is quite a nice table
  • You can also do retention by plan (e.g. plan = premium), which gives another nice table
• I'm thinking here first time retention with 'pageview' and 'watched movie' could do well

Will continue adding more ideas and mockups here. We can and should iterate here.

[paolodamico]

Thanks @yakkomajuri, looking pretty good! Some raw/random thoughts on things we could improve,

• Add more steps to the funnels, 2 steps doesn't seem particularly helpful.
• I think retention for mobile app analytics should be relevant.
• Maybe we're missing some more universal holistic metrics? E.g. active users, sign ups, ...
• For different roles thing, I'm thinking that maybe we can create all dashboards but only pin the ones that are relevant? Bc if you have other persons in your team with other roles, we want to make sure they see those too, right?
• Some web analytics that do something similar to GA would be pretty useful too.

As a side note I also think that we could check out Amplitude's demo to get some more ideas too.

[Twixes]

Closing this as it doesn't seem we'll be doing demo data in onboarding, definitely some useful inspiration for my demo data project though.