In an effort to simplify our newsletter signup process (no extra calls to "Double_Opt_In" and "Confirmed" data extensions) - and have 1 database for all things newsletter/double opt-in, let's configure Basket to handle the double opt-in subscriber process. Scenario: * Subscriber signs up * Basket checks Master_Subscribers for subscriber * If found - FLGs are updated. * If not found, their fields are passed into Basket for holding, and a triggered confirmation email is sent. * When subscriber confirms, fields are passed into Master_Subscribers. This will keep our calls to ET to check for subscriber's existing records much simpler and faster - AND - only confirmed subscribers are passed through to your email database. Goal to launch: Q4
We'll also want a holding period of 48 hours of unconfirmed emails in case there are errors in the call that need to be retried, or it takes awhile for the user to confirm. After 48 hours from the time of signup, we should clear these waiting people from the holding place.
Still valid and on roadmap list - but currently on hold. It's being blocked by Bug 742951 and depends on ability to send email to someone without adding them to a Data Extension.