Hi @haan, welcome to the community.
A Klaviyo custom hosted page, is a more advanced way to customize the preference/consent pages since it gives you free access to build that with HTML/CSS and Javascript, with access to the identified users’ custom profile properties (to prefill their settings on the form).
You can see sample code here which is a bit hidden on the following page:
So theoretically, you can build it however you want it to look and behave, including your own approach to capture all the data via forms. So it’s definitely one approach.
I would offer a better approach is to revisit your embedded page option. So long as Klaviyo has the user identified, when they complete the Form it will be submitted to the correct user. There are edge cases where this doesn’t work (user has some cookie ad/security blocking plugin, etc), but for the vast majority of users is will submit to the identified profile without an issue. So leading a user (from an email to click on “Update Your Birthday”) to a landinge page with a Signup Form that simply asks for the Date of Birth will be associated to the correct user (without them having to enter the email address again.)
Lastly, perhaps you should look at the multi-step options of a Signup Form. I’m not sure if this is for some other use case, but you can start the email capture with a clean and simple form, then lead them down ‘multiple steps” where you can ask for date-of-birth and other profile information in subsequent steps so it doesn’t seem overwhelming to the user at first. And if they decide to skip the subsequent steps, their email address has already been captured. I’m not sure if this is overly simplistic, but just throwing it out there in case you weren’t aware.
Hope this helps!
Hi @haan, welcome to the community.
A Klaviyo custom hosted page, is a more advanced way to customize the preference/consent pages since it gives you free access to build that with HTML/CSS and Javascript, with access to the identified users’ custom profile properties (to prefill their settings on the form)...
Hi @retention,
This is very helpful, thank you. I clearly haven’t looked at identity resolution enough (thanks for that link) - looks like Klaviyo is a lot smarter about that than I assumed. If not having to include a field for the email address still allows us to ask for something like a date of birth, then embedding a form might be the way to go indeed.
Plus, like you suggested, a multi step signup form could very well give users the opportunity to leave data behind without being scared off by a huge form to start with. That’s an interesting thought.
Thank you so much, this really helps.
