Often, a user seemingly “needs” to do perform off-site action(s) before they can experience your product.
For example, a lot of services inherently require the installation of tracking tokens or getting the rest of the “team” invited (etc.) before the value proposition is really communicated.
We concentrate a lot on optimising landing pages (for good reason), but if a newly-registered user never installs your client, they will never turn into a paying customer.
Here are some existing resources:
One immediate question I have: Should these tasks be strictly required before allowing the user to click around the app?
Seem to be positive arguments either way, but disadvantages too (empty apps communicate value poorly, even with example data). Does anyone have some concrete experience here?
Some things that I have noticed elsewhere:
- “Email this tracking code to a developer” button (PerfectAudience)
- Sending specific and very clear “You have not done X. Please do X. [instructions]” emails after signup - not sure where I read it now (patio11?) but “for each task you need to get the user to do, send exactly one email about that” etc.
- Sending followups to the above
- Sending personalised followups to the above, etc.
Anyway, it would be great to get your onboarding tips and tricks.