Skip to content
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

Web Analytics Public Beta To-Do List #18547

Open
18 of 37 tasks
robbie-c opened this issue Nov 10, 2023 · 0 comments
Open
18 of 37 tasks

Web Analytics Public Beta To-Do List #18547

robbie-c opened this issue Nov 10, 2023 · 0 comments
Assignees

Comments

@robbie-c
Copy link
Collaborator

robbie-c commented Nov 10, 2023

This is the list of work to be done before Web Analytics is to move from opt-in beta to default-on beta, appearing in the UI for all or most customers.

This list is open to change, and I'd love any feedback.

Must-haves

  • Performance good enough for large customers
    • Design session table
    • Write session table backfill script
    • Run session backfill
    • Use hogql to limit date range of session queries
    • Update web analytics queries to use sessions
    • Add session-based filters
  • Any architectural changes that break data continuity
  • Make it easier to separate sites - Create a new "My Sites" scene #12181
  • Make decision on whether we want to continue to call it "web analytics"
  • Fix async queries (internal thread https://posthog.slack.com/archives/C05LJK1N3CP/p1707844028504349 )

Should-haves

  • Live online users count
  • Show time of last refresh, rate-limit refreshing
  • Visual regression tests

Could-haves

  • Add chart showing time of day that users visit (two tabs, one for your TZ, one for user TZ)
  • Set all queries to use the exact same time period
  • Group devices by width/height tuples
  • Add % of total for devices and geography tab
  • Add link to definitions in the docs
  • Help people figure out if they have their internal / test filters set up incorrectly
  • Top clicks for people with autocapture set up
  • Solve the technical difficulties prevent us from filtering on channel type
  • Improve UX on mobile devices e.g. https://posthoghelp.zendesk.com/agent/tickets/10625
  • LCP/page load for paths

Won't-haves (possibly will be done in the future)

  • Integration with google search console
  • Add Conversion goals
  • Hide incomplete periods from graphs
  • Improve the UX around searching for a path
  • Add a flag to posthog-js to enable sensible defaults for web analytics
  • Use the paths insight, shows which paths are best at converting
  • Ad attribution postback
  • Pulling in data from ads to measure CAC
  • Exporting data (e.g. as CSV)
  • Figure out how to make sessions span domains, see https://github.com/PostHog/product-internal/pull/531
  • Public dashboards

Historical

Feedback form feature requests

  • Convert to a "real" dashboard
  • Be able to open urls
    * Path cleaning
  • Sites
  • Ability to schedule reports, as you can do with dashboards.
  • Ability to add a link to a filtered view to a notebook or dashboard.
  • Ability to save a snapshot of the web analytics page as a PDF.
  • See user information (e.g. have the visitors count be clickable)
  • More time period options, like YOY or MOM
  • see the exact(or exactish) location of users pinpointed on a world map., like Shopify Black Friday
  • Comparisons of Month over Month of the different categories like UTM source, etc
  • See cost of customers in posthog through ad integration
  • Add example session replays

Previous issue: #18177

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant