How to implement a post-signup onboarding process for Zapier-created members in Wized? Answered
I'm trying to build an onboarding process for new members joining, but since new members are created through Zapier I can't set up a sign-up redirect.
So instead I want to have an element on the first screen (check image) that's only for members who haven't completed the onboarding.
I'm using the premium course template, and I want that when they click the complete button on the last step - it means that the onboarding is completed.
How could I set this up, would it be through custom fields?
Fixed the conditional visibility. Now I just need to add "Done" to the "Onboarding" custom field I have created once the button is clicked.
Comments
4 comments
Hey Nicolai Amirzadeh, I believe if sign-up redirects for your website (irrespective of what plan they choose) is gonna be the Onboarding page, you can set the default redirect on signup / purchase to be the Onboarding page in your case.
But if you have different sign up redirects planned for some specific plan and that overrides the default settings, then you can have a look at this memberscript which will give you an idea to hide / show and also how to about updating the custom field, in your case you won't need the user to input any value, so you can have that custom field input hidden and work with the button as a form which updates the custom field.
Found how to set the custom field as well 😅
Guess I'll keep the thread in case someone else needs help
Hey A J! yeah the problem is that members never sign up, we create the account for them on Zapier so they just have to login.
Ah okay got it, yes then the custom code modified as per your use-case or the memberscript linked above should do the trick for you.
Or if they are just gonna login, you could set the login redirect to be onboarding page and update it to some other generic page once they are done with the onboarding as well.
All approaches should help solve your use-case.
Hi, I personally prefer to solve the problem of requiring users to fill up the onboarding form by using gated content based on plans than using custom fields. I think it's more flexible because you can block all the premium content and also show warnings like announcement bars to encourage users to complete the onboarding based on that plan, and wouldn't require writing custom code.
Let me explain, for this example, I would assign the user recently signed up a plan that would indicate the user hasn't fulfilled the onboarding yet, so I'll call it onboarding plan.
And also, I would have a plan that would have more permissions, that would be my main plan. All users that have this plan means they completed the sign up. I'll call it account plan.
So based on this setup. If you want to hide content to this user you can easily gate the urls (so user that have the onboarding plan cannot access your premium content. And also you can hide components easily using data-ms-content=!onboarding or configure it depending on your preferences.
The account plan gets assigned when the onboarding form is successfully submitted (you have to set up the automation). And you can set Memberstack to remove the old plan by using advanced plan logic settings when assigning the new plan.
Please sign in to leave a comment.