cds-snc / cds-snc/platform-forms-client
Explore options for research funnel data capture and analysis
- Dominant language
- TypeScript
- Stars
- 46
- Forks
- 16
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 85
Description
# Problem statement
There is a need to understand the full customer journey from initial awareness to activation, retention (and possible churn). Current visibility covers only part of the journey and does not include awareness data. A structured approach is required to clarify what is already possible, what would require identifiable information, and how a continuous end‑to‑end funnel could later be integrated into the [Platform CRM](https://airtable.com/appqflckiY4UkLqUT/tblDK5kuBj17drbFf/viwvnWhbB6mmIqEpp).
## Step 1: Use existing Superset data
Superset already provides anonymized product data through userID. This allows the creation of a first funnel that covers product activation, retention and churn.
Available events include:
- Account creation
- Request to publish
- First published form
- Last login
This step relies only on existing data and does not require identifiable information.
## Step 2: Integrate awareness data
Awareness data is currently collected through demo attendance. This data contains identifiable information such as email addresses. To connect awareness to product activation, identifiable information must be linked to database fields such as account creation date, request to publish date,and first form publication date.
The source of awareness data may evolve in the future.
Step 2: Explore continuous flow into the Platform CRM
Once identifiable information is available, a continuous flow into the CRM could support a complete and up to date funnel from awareness to retention. This would allow ongoing monitoring of the customer journey.
This step is exploratory and depends on alignment across teams.
# Purpose of this issue
The purpose of this ticket is to trace the work and ensure alignment before moving beyond Step 1. The intention is to clarify the scope, confirm the sequence of steps and avoid any change to current sprint priorities. Feedback from stakeholders is welcome when time permits.
https://docs.google.com/document/d/1X6e5RMBH83gEwbB4yAiCA6OQcfoM6An02qBTuEgw2jY/edit?tab=t.0#heading=h.q1x5sqfc4bbu
Contributor guide
Assessment
This issue has not been assessed yet.