Closed joethreepwood closed 1 year ago
OK, I have now set up three campaigns.
This is the same as it was before, albeit focused on Cloud (EU and US) users and with a few extra language and link tweaks to send users to better resources.
We're sunsetting, so this is mainly redundant. However, it is mostly the same as the Cloud workflow, with a few changes to accomodate the self-hosted experience (e.g. not sending users to app.posthog.com)
This is a very small segment and I've shortened it to two emails only.
For the open source onboarding, is that for people on the Docker Compose version? If so, probably the biggest appeal of Cloud is the scalability? I'd swap that in for 'less cost' given the open source version is already free! (Unless we're going to start wiring them money...)
What's the problem?
The onboarding flow currently mostly directs users to resources on the site, such as tutorials. We do this in part because we cannot direct users to specific parts of the app, because we have to accomodate for self-hosted users and cannot predict their URL. In some cases (for example) this means we direct people to odd places.
We can fix that.
What's the change?
I'm going to split the onboarding flow into three variants -- one for US Cloud users, one for EU Cloud users, and one for self-hosted users.
Links in the self-hosted campaign will remain basically as they are now. We'll, for example, direct people to resources about feature flags when we discuss feature flags.
Links in the Cloud campaigns will direct to the apps instead, enabling us to push users more directly to the features we want them to engage with. We'll continue to push the resources as secondary CTAs.
What benefit will this have?
Obviously this will mean we're pushing people back into the app, promoting better engagement.
Additionally, we could potentially build this into an app experience -- so that users arriving in the app from these links will be served onboarding content within the app that drives further engagement. But that's just an idea for now.