What’s the use case for including a hash of the email in the URL? If you have click tracking enabled, Klaviyo will append a _kx param to links, which includes a profile identifier, and which will cookie the browser with the profile.
What’s the use case for including a hash of the email in the URL? If you have click tracking enabled, Klaviyo will append a _kx param to links, which includes a profile identifier, and which will cookie the browser with the profile.
Would you be able to guide me on how to addapt the site script on site, that extracts the information for the form, so that it is then converted back to the correct email? :)
The _kx param sets a __kla_id cookie is a base64 encoded JSON block that includes an $exchange_id property. You can use the Get Profiles call server-side to filter on this _kx value and get back the profile and its plain-text email address.
You could use base64_encode but it’s effectively the same as sending the email in plain-text, it’s not encrypting anything.
