I’m working on migrating to Klaviyo from another system.
I understand that I can set the consent for “EMAIL” easily via CSV upload. I also understand that consent = [“EMAIL”] does not mean double-oped-in in Klaviyo Logic. (What is the difference between double-opted-in and Email-consent?)
I understand that when migrating my contacts I’ll definitely lose the double-opt-in information from the previous system and that the workaround would be to resend a double-opt-in Email to the list of imported users - which is not workable as I would lose some of my contacts simply due people not replying (open-rate / click-to-open). Alternatively I could add custom properties to the imported users and stitch together my newsletter segments from the two types:
- newly joined people who have received a Klaviyo-nativ DOI mail and opted in
- imported users where the custom properties indicate that the this person gave us at some point in the previous system their double-opt-ed in
Is that correct? This appears to be a fairly big shortcoming of Klaviyo leading to a weirdly stitched together list of “old” and “new” users with DOI as an property at different placed of a profile.
Is the above correct? Is this something that only I’m struggling with? :D
I did see a couple of other posts / conversation around this topic but they appeared a bit non-conclusive for me.
Best answer by ebusiness prosView original