PostHog / PostHog/posthog

Global customer journeys

Open
#44,007 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

concept
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Feature flag: customer-analytics-journeys

Use case idea:

  1. Track a main known customer journey in the product
  2. Find upsell/cross-sell opportunities from the main journey
  3. Branch out journeys out of the main one, as a upsell/cross-sell happens, connecting multiple journeys together
  4. Find net-new customer journeys, based on autocapture/pageview/pageleave events

Wishlist:

  • Executive report: How a given feature launch impacted revenue/outcome/conversion?
  • Track dropoffs: Categorize users that dropped off each stage of the funnel, so they can be targeted as a group (behavioral cohorts?)
  • Experimentation on journeys: make it easy to compare variants in a journey, showing conversion per variants

Questions:

  • Can we identify what are the main journeys?
    • Potentially yes, using data-mining algos such as alpha algorithm that @fercgomes brought up

To do

Global

  • Instrument journeys
    • Create
    • Toggle
    • Delete
    • View (journeys)
    • View (profile)

Profile

  • Show filters in flow nodes
  • add timestamp to completed funnel steps
  • add # of times the funnel was completed by the customer
  • scope selectable journeys in profile by entity (person/group type)

Tab

  • Creating a funnel is not showing results right away
  • path calculations should honor builder settings (time window, etc)
  • select two nodes to see the conversion rate over time between those two steps
  • Expand breakdowns as nodes
  • Can't change time window
  • Time window does not reflect what is saved in the insight

Builder

  • Paginate existing insights list

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by mapping the existing journeys work across the Profile, Tab, and Builder areas, then clarify which unchecked item is in scope; done cannot be determined until one item has defined acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, python, react, typescript
Domain
analytics, backend, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.