Overview As a marketing executive I'd like to build workflows using the "Marketing email activity" of draft or scheduled Regular emails as the enrollment trigger so that I can build an automated campaign in advance of start date. Specific use case I am building a campaign that has 3 different emails, each being sent on specific dates. Depending on the actions a user takes with each email, they may receive different variants or be removed from the campaign - the logic of this is being handled by a workflow around each email send and list memberships. Only Regular emails can be scheduled on a date, so I would like to use "Contact Received Email" within the Marketing email activity as an enrollment trigger. However, currently only published Automated and sent Regular emails are available options. Benefits This would enable users to achieve two things: Build more advanced automated campaigns the benefit of using a scheduled email (rather than a workflow centred around a date to send an Automate email) is that the workflow actions of Delay for set amount of time, Delay until a day or time, and Delay until event happens are all still available Build campaigns in advance of sending emails this is the same benefit as the scheduling emails / social post features; being able to "schedule a workflow" I can do all my work in advance, let the campaign run without intervention, and concentrate on my other projects in my specific use case, I'm effectively scheduling a workflow by building it off the back of a scheduled Regular email, which in my mind is the most efficient way Workarounds for others If you've stumbled upon this looking to do the same thing, here's what I've done as a (admittedly rather cumbersome) workaround. This is for a 3 email campaign example, with each email sent on a specific date. If anyone has a better workaround that'd be great! You only need to use this approach if you're using different types of delay and looking to send on specific dates. Publish Emails 1, 2, and 3 as automated emails Build Workflow 1 centred around a date Workflow sends Email 1 Workflow enrols in Workflow 2 Build Workflow 2 Workflow 2 handles the logic for user behaviour following Email 1 and other follow-on actions (e.g. any tasks, list adds / removals you may have) Workflow 2 enrolls in Workflow 3 Build Workflow 3 centred around a date Workflow sends Email 2 Workflow enrols in Workflow 4 Build Workflow 4 Workflow 4 handles the logic for user behaviour following Email 2 and other follow-on actions (e.g. any tasks, list adds / removals you may have) Workflow 4 enrolls in Workflow 5 Build Workflow 5 centred around a date Workflow sends Email 3 That's essentially 2 workflows per email; one "centred around a date" to send the automated email, another to handle the logic of your campaign activity. Alternative feature suggestions to solve same problem The use case could also be solved by letting users access the 4 types of Delay in a single workflow: Delay schedule and timing Delay for set amount of time Delay until a day or time Delay until event happens Currently, you can either get 1, or 2-4, but not all. Of course, you could deliver both suggestions and that'd be smashing, as they each bring their own benefits.
...その他を表示