Great video Jason, and understood about using a custom tag to track DOI confirmation for what ConvertKit will consider a SOI list. Is there any way in CK automation to set the actual Confirmed flag other than in the incentive email that your method turned off? Or do “SOI” subscribers no matter how engaged remain on the Unconfirmed list in CK?
@@earlwilliams7406 if you set the form to single optin then any and all subscribers coming into that form will be marked as Confirmed so you don’t have to do anything to in CK to make that distinction.
This is great! I've just implemented it and have some subscribers moving through already. Custom actions are new to me, but I'm figuring them out. Thank you so much!
Awesome -- do you mean custom fields? I use custom fields for anything that's a one-to-many relationship or for statuses that will change. Specifically in this case, it's easier to use custom fields because then you don't have to worry about managing tags that denote status. Custom field set to confirm and done.
Hey, Jason! Great tutorial-thank you! I just used it to set up an enhanced opt-in automation for one of my lists and plan on doing the same for my other one. Thanks for making this. I liked and subscribed, btw. Looking forward to learning more. 👊🏼
Hi Jason , Thank you for the valuable content . I have a question - In the second method, since we have a double optin incentive turned on with a confirmation link to Lead magnet already. Are we still keeping the automation confirmation on and resending the same email series you describe for single option? ( LM in the email series to all single optin + double option subscribers) to further filter users who haven't been engaging for 30d ?
You don't have to re-send the lead magnet as a part of the delivery. It couldn't hurt, but I would word it differently so that it's in context as the second time.
Great question -- I'm not a lawyer, so definitely consult one for your particular case. CAN-SPAM Act does not require double opt-in, but it is important (and best practice) to prove that you have a subscriber's implicit or explicit consent. How you view that is fuzzy. For me, a double opt-in is a click. So that's the basis for consent here. As far as I'm aware, Germany, Norway, Greece, Switzerland, Luxembourg, and Austria are the only countries where Double Opt-In is required.
This works especially with the latest update because you are sending them multiple emails with the intention for them to click. Which driver tag are you referring to?
@@NurtureKit Thank you so much for the reply! RE the driver tag: I see this automation starts with the NurtureKit tag. Should this tag be removed after the "set onboard status to confirmed"?
I bookmarked this months ago and finally got back around to watching it. Great tutorial Jason, setting this up now!
exactly the kind of info i was searching for
Great video Jason, and understood about using a custom tag to track DOI confirmation for what ConvertKit will consider a SOI list. Is there any way in CK automation to set the actual Confirmed flag other than in the incentive email that your method turned off? Or do “SOI” subscribers no matter how engaged remain on the Unconfirmed list in CK?
@@earlwilliams7406 if you set the form to single optin then any and all subscribers coming into that form will be marked as Confirmed so you don’t have to do anything to in CK to make that distinction.
This is great! I've just implemented it and have some subscribers moving through already. Custom actions are new to me, but I'm figuring them out. Thank you so much!
Awesome -- do you mean custom fields? I use custom fields for anything that's a one-to-many relationship or for statuses that will change. Specifically in this case, it's easier to use custom fields because then you don't have to worry about managing tags that denote status. Custom field set to confirm and done.
@@NurtureKit How do I access the information in custom fields, though? I can't figure out how to search for it...
@@ArtfulMath if you want to build a list of people, use segments and search on the Custom Field in the filter.
Hey, Jason! Great tutorial-thank you! I just used it to set up an enhanced opt-in automation for one of my lists and plan on doing the same for my other one. Thanks for making this. I liked and subscribed, btw. Looking forward to learning more. 👊🏼
Thank's Mike -- how's it working for you?
Hi Jason , Thank you for the valuable content . I have a question - In the second method, since we have a double optin incentive turned on with a confirmation link to Lead magnet already. Are we still keeping the automation confirmation on and resending the same email series you describe for single option? ( LM in the email series to all single optin + double option subscribers) to further filter users who haven't been engaging for 30d ?
You don't have to re-send the lead magnet as a part of the delivery. It couldn't hurt, but I would word it differently so that it's in context as the second time.
Jason - does this method run afoul of the anti-spam laws in the US? I thought compliance required double opt-in. Thanks.
Great question -- I'm not a lawyer, so definitely consult one for your particular case. CAN-SPAM Act does not require double opt-in, but it is important (and best practice) to prove that you have a subscriber's implicit or explicit consent. How you view that is fuzzy. For me, a double opt-in is a click. So that's the basis for consent here.
As far as I'm aware, Germany, Norway, Greece, Switzerland, Luxembourg, and Austria are the only countries where Double Opt-In is required.
Implemented this for one of my lists. Will see how it goes and then maybe implement it across the board :)
Fantastic Kevon - let me know how it goes
Fantastic tutorial! I could use some more guidance on why this is important (not having cold people on the list).
Absolutely! There will be more to come on Cold Subscribers
If we want the Tag to kick off a Sequence, where does it go? Under the "Confirmed" Condition?
What value do you choose for the custom field step? I think you edited that out.
If you mean the custom field of onboarding_status at the very top of the Visual Automation, that’s set to pending.
Does this automation still work well with the new iOS privacy settings? Also, should we remove the driver tag at the end?
This works especially with the latest update because you are sending them multiple emails with the intention for them to click.
Which driver tag are you referring to?
@@NurtureKit Thank you so much for the reply! RE the driver tag: I see this automation starts with the NurtureKit tag. Should this tag be removed after the "set onboard status to confirmed"?
Oh I see - no, you don't need to unless you plan on using it in the future for something else.