Sprint 1.27.0 2/2 - Jun 21 to Jul 2 (Funnels #1)

[timgl]

We want to really lean into improving funnels. This is the first sprint planning for #4785. Full context on why funnels, here (internal).

Approach

For this sprint (27 2/2 from Jun 21 to Jul 2), we'll follow this approach (from sync discussion on Jun 16),

1. Core Analytics Team will work on "no regrets" tasks that we know we'll absolutely need (see below).
2. Spend ~1 week designing and specing out the whole product functionality.
3. Core Experience Team will mostly work on bug fixing and more fluid priorities until (2) comes along (end of week 1) and we're ready to tackle specific tasks.

support hero
Marius + Karl

Extensibility

• Take over PHP feature flags Feature/support feature flags posthog-php#12
• Flutter Web issues Don't import implementation files from another package in generated plugin registrant. posthog-flutter#12
• Get as far as possible with metrics on event deliverability Metrics on event deliverability #4577 (potentially Phase 3?)

Side Quests

1. • Ruby + Plugin Docs Make Plugins docs world-class posthog.com#1396
2. • Automatic cohorts plugin Plugin Ideas integrations-repository#9
3. • Investigate BQ issues BigQuery is very flakey on local / self-hosted bigquery-plugin#10
4. • Databricks plugin Plugin Request: Databricks export plugin-repository#25
5. • Batch plugin logs Console.log slow query warning plugin-server#424

Core analytics
Buddy

• API for clicking on a step and getting people Funnels - API for getting persons on a step or drop-off #4818
• API for clicking on dropoff of step and getting people Funnels - API for getting persons on a step or drop-off #4818

Michael/Neil

• Validate and fully integrate funnel trends query into backend Validate funnel trends data #4814
• User paths

Eric

• Rewrite funnel steps query Rewrite funnel steps query #4817

Warrants a rewrite of base funnels step query

• Breakdown by event/user properties (stacked bar chart style) for steps Allow breaking down in funnels #3409
• Timing between steps of funnel Funnel conversion time #4847
• Filtering conversion window for steps Done
• Support event exclusions and “exact” funnels (i.e. no other events happened)
• Support unordered funnels Funnel Unordered Steps #4868
• Make sure repeat events are handled properly Handle repeated event steps in funnel #4813

Core experience

1. Bugs
2. Funnel-related stuff for Core Experience Team that isn’t blocked (by neither design, product or core analytics):

• Allow deeplinking to specific sessions, events & recordings in a person page. Allow deeplinking to specific sessions, events & recordings in a person page. #4820
• Allow setting and persisting custom names on funnel steps. Setting and persisting custom names on funnel steps #4821
• Implement updated PersonModal for funnels and wire API. Implement new PersonModal for funnels #4819
• Build time conversion analysis UI (will be unblocked on Wed CET EOD) Time conversion analysis - new view #4855
• Implement new UI or changes to current UI (will be unblocked on Wed CET EOD) Improved funnel visualisation #4535

Infra & deployments

[paolodamico]

EDIT: We're taking this approach, working on no regrets stuff and taking ~1 week to spec out the rest of the stuff.

While some functionality here is pretty straightforward and could be built right away (e.g. conversion window for steps, avg. time to convert, ...), I think it might be worth taking a step back and maybe spend some time with the specs and mockups for this before building? With the wireframes I think it'll be a lot easier to plan what to build first and make sure we end up with a more solid outcome. For instance, make funnels more prominent, breakdown, visual drop off, ... could use more clarity.

[paolodamico]

@EDsCODE @buwilliams I think we could specifically include these issues for this sprint? #4067, #2121

[paolodamico]

FYI @timgl updated the issue description with what we discussed yesterday (feel free to edit). The list of things to spec out I moved to #4785 to have a single place with all the ideas/features to include.

[buwilliams]

@paolodamico I'll pick those up.

[yakkomajuri]

Extensibility Team (me :D):

Top priorities

• Take over PHP feature flags Feature/support feature flags posthog-php#12
• Flutter Web issues Don't import implementation files from another package in generated plugin registrant. posthog-flutter#12
• Get as far as possible with metrics on event deliverability Metrics on event deliverability #4577 (potentially Phase 3?)

Side Quests

In order of likelihood of getting accomplished:

1. • Ruby + Plugin Docs Make Plugins docs world-class posthog.com#1396
2. • Automatic cohorts plugin Plugin Ideas integrations-repository#9
3. • Investigate BQ issues BigQuery is very flakey on local / self-hosted bigquery-plugin#10
4. • Databricks plugin Plugin Request: Databricks export plugin-repository#25
5. • Batch plugin logs Console.log slow query warning plugin-server#424

Post-Sprint Edit

Other relevant things accomplished:

• Small updates to libraries (e.g. posthog-node and posthog-js)
• Fixes for S3 plugin and GeoIP plugin, RudderStack plugin revamp shipped

[paolodamico]

@yakkomajuri I think this issue was originally intended for the specific sprint on funnels only, but it may actually be useful to have it as the issue for sprint planning?

[yakkomajuri]

@paolodamico I think @timgl was thinking of using this issue for planning?

Happy to move it though

[EDsCODE]

Core Analytics Tasks

To start (further tasks pending rewrite of funnel steps query):

Buddy

• API for clicking on a step and getting people
• API for clicking on dropoff of step and getting people

Michael/Neil

• Show related session recordings on person modal
• Validate and fully integrate funnel trends query into backend

Eric

• Rewrite funnel steps query

Warrants a rewrite of base funnels step query

• Breakdown by event/user properties (stacked bar chart style) for steps
• Timing between steps of funnel
• Filtering conversion window for steps
• Support event exclusions and “exact” funnels (i.e. no other events happened)
• Support unordered funnels
• Make sure repeat events are handled properly

Performance improvements (long running/backburner tasks)

• properties flattened
• person_id and props on event table
• precalculate actions

[fuziontech]

Team Infra and Deploys

https://github.com/orgs/PostHog/projects/10

[mariusandra]

Core experience

1. Bugs
2. Funnel-related stuff for Core Experience Team that isn’t blocked (by neither design, product or core analytics):

• Allow deeplinking to specific sessions, events & recordings in a person page.
• Allow setting and persisting custom names on funnel steps.
• Invite team members by sharing a funnel (will be unblocked on Monday CET EOD)
• Implement updated PersonModal for funnels and wire API (will be unblocked on Monday CET EOD)
• Build time conversion analysis UI (will be unblocked on Wed CET EOD)
• Implement new UI or changes to current UI (will be unblocked on Wed CET EOD)

[paolodamico]

@EDsCODE / @timgl after finishing the draft product specs some questions came up,

1. Are we still doing the flatten user properties thing and is this blocked by the rewrite of the query?
2. Are we working on paths or on session recording? See https://github.com/PostHog/product-internal/issues/86#issuecomment-864865059 for details.
3. If we're working on paths, @timgl are you working on the product specs?

[Twixes]

🔚