π Problem Statement
As a Pelcro platform engineer, there is no cross-client aggregation of funnel event data, which makes percentile benchmarking impossible.
π‘ User Story
As a Pelcro platform engineer, I want a backend pipeline that aggregates anonymized funnel conversion rates per step across all sites, so that benchmark percentiles can be computed and served per client.
π― Definition of Done (DoD)
β Given sites emit standard events (paywall_displayed, registered, subscription_created, renewal_attempted, etc.), when the pipeline runs, then per-step conversion rates are computed per site and stored in an aggregate benchmark table.
β Given the benchmark table is populated, when queried, then it returns p25, p50, p75, p90 percentile values per funnel step, excluding any site below minimum event volume threshold.
β Given a site_id, when GET /analytics/funnel-benchmark is called, then it returns that site's conversion rate per step alongside benchmark percentiles for the same step.
β This change will impact API / Data, specifically a new GET /analytics/funnel-benchmark endpoint and a scheduled Laravel job for aggregation.
Please authenticate to join the conversation.
In Progress
Pelcro Product
19 days ago

Rana Haleem
Get notified by email when there are changes.
In Progress
Pelcro Product
19 days ago

Rana Haleem
Get notified by email when there are changes.