Open neilkakkar opened 12 months ago
related to (1): https://github.com/PostHog/posthog/issues/16681
Option (3) that works better for some use cases:
Whenever a user responds, we should add a $survey_response/<surveyID>
property to the user. This way, we can target users who don't have this property set for surveys.
It's a bit rougher than the above two, specially around the UX, (because the property needs to exist before we can target) but much faster & can unblock long running surveys for now.
Related issue : https://github.com/PostHog/posthog/issues/22099
I think both of these can be combined and the motive here is to give people the ability to repeat a survey and track survey responses on each of those "iterations".
Here's what we need to do to solve this :
Column name | type | description |
---|---|---|
survey_frequency |
||
survey_max_iteration_count |
integer |
survey_frequency
(cron like syntax for interval between iterations), survey_max_iteration_count
. so a user can say, repeat this survey 4 times, once every 3 months
, they can also just leave the survey_max_iteration_count
as zero to have an infinitely repeating survey `repeat this survey, once every 3 months
Once we have the above properties, we can show the user an interface to set the frequency of the survey and how many times it should repeat. These two properties are nullable and we need to make our work backwards compatible to make existing survey responses function without issues to show NPS scores etc.
$survey_response/${survey.id}/${survey.iteration_start_date}/
$survey_response/${survey.id}/${survey.iteration_count}/
Bug description
We’re not dealing well with long running surveys where the same survey can be shown to the same person again and again as they browse incognito / clear cookies / etc. etc..
For example, if you have a churn survey that targets on whether a user churned from product X property.
Two things that would help here I think:
Both would work, but (2) currently is too hard for end users to implement because we don't have https://github.com/PostHog/posthog/issues/17392