Ján Mikláš: Hi Jan, great last update on Automations with the IF/Else option, the plugin did a huge step. I would like to know where to publish new requests for automations, should we use this thread? For example, would be great on the Abandon Cart triggers be able to filter and use the IF/Else conditions based on cart amount. Thanks keep pushing!

Ivan Martinez: we do plan to release a couple more improvement before we remove the "beta" badge, at which point I'll close this request so we can better track each individual automation-related request separately. Feel free to already create a new request for cart amount filter (I'll share, that this is on our roadmap, hopefully by the end of this year, but likely only after out-of-beta).

Hi Carlos Divas, thanks for the feedback, we really appreciate it!

Yes, this is planned! As a next major upgrade we plan to start working on supporting conditional logic branching in automations. This would enable customers to exit the drip campaign early if they've completed a purchase, and not get any subsequent emails. E.g. after sending the first email the system could check if the customer purchased any/specific product, stop the automation if they did, or send a follow-up email if they didn't.

Would that fit your needs?

Unfortunately, I don't yet have an ETA, but we're currently getting close to releasing trigger filters, which will enable you to run campaigns for first time or repeat customers, and will explore branching next.

Tautvidas: Hey! Thank for the reply. This sounds amazing and exciting. Knowing this is planned makes it cool, even if there is no ETA yet.

I think it does fits my needs yes, at least partially.

In the plan you got, what conditions have you thought about exploring in the initial stages? I ask because it would be great if those conditional branches are able to check if the user has another automation in the processing stage. For example, the user has joined the Prospects automation feed, then buys the service in question and starts the Onboarding automation feed. At this stage, he should not get any remaining Prospects feed emails, as it is not required anymore. Hope this is included hehe.

I would even take it one step further and allow admins to manually terminate an automation for a specific client.... but this can wait a bit longer haha.

Thank you!

Tautvidas: Hi! Do you have now more clear ETA for conditional logic? I think its the only thing that its missing on automations to start a robust tool and start working more in advance with it. Good job!

Ivan Martinez: we aim for October-November.

Tautvidas: Great Tautvidas, we see how slowly the automations are becoming more useful, keep pushing! there are some really needed, abandoned cart trigger, conditionals to create different routes on the automations, etc ,etc. Thanks!

Hey Ivan Martinez: Thanks for highlighting these! The abandoned cart trigger, trigger filters and an action to send an email notification to the admin are coming soon.

Conditionals are planned, but we don't yet have a more detailed update.

Tautvidas: Without having any idea of development here, maybe its easiest to have a condition just for checking if an user belong to a segment, so we can use segments to do all the conditions we need to be used and then the user will be there or not, (for example users with 1 order -> Segment 1 order group) and the automations will only check that... just idea :). Thanks for the update :)

Tautvidas: I am confused—I could already assign a tag to a subscriber after a welcome series simply by having the tag wait for the series to be over to be applied. Same for choosing to trigger automation once or every time—this was already present in the plugin prior to the update. So what exactly has been gained functionality-wise with this update related to automations?

I really wish you guys would stop focusing on Woo Commerce at the expense of basic functionality. Not being able to create even simple split-path automations, or have triggers based on their behavior is a huge issue, and its frustrating because those feature requests have huge amount of votes, while you guys seem to be focusing on Woo Commerce stuff with much smaller pool of interested users.

Are you a wordpress email platform, or a woocommerce mail platform? Because you guys seem to be prioritizing the latter at the expense of the former. I have a whole automated marketing strategy that i can't implement because I didn't realize when I signed up that MP can't do 90% of the stuff that other email marketing services can do—even though you guys have been in development for several years now. If it wasn't so time consuming to switch services I would just go to something else, but since I do my own development it's a PITA. It would be worth waiting if it seemed like this functionality was in the near future, but it seems like its not your priority at all, and you're focused on this WC stuff that is completely irrelevant to a portion of your users.

Tautvidas: Thank you, automations are really working great! The only thing is missing for me, is adding a possibility to schedule e-mails up to some specific date (eg. my end of sale date is end of july, I would like to schedule automated e-mails week before end of sale, two days before end of sale etc.) Is it possible to be implemented as automation enchance?

Hi Benjamin Ballinger: thank you for sharing, your feedback is really helpful to hear!

Recently the team added the ability to add/remove subscriber tags in Automations, so I hope these would help with any manual sends or segmentation in the meantime.

We'll consider exploring adding/removing tags triggering automations in latter phases. At the moment the team is focusing on expanding trigger filters, such as whether or not a contact is part of a segment.

Hello Ryan Murphy, yes, it does indeed appear that the end result MailPoet is building will offer tools for similar email marketing strategies to grow your store that ShopMagic does.

What types of transactional emails do you currently use? Or do you focus more on customizing the transactional email content?

The additional context would help inform which options we focus on first.

We have recently launched personalized discount coupons, and are currently focusing on enabling post-purchase and abandoned cart sequences, with more key options like review requests and upsells following next.

Ivan Martinez: Hi Ivan, thank you for your feedback!

We're currently working on expanding the set of ecommerce triggers, e.g. product purchases, and some may include conditional trigger filters.

To help us better understand your needs, could you please share one or two examples of what business outcomes you would like to achieve with conditions in your business?

Tautvidas: For example:

Automation:

Trigger: User go to subscriber list Woocommerce (when buy a product)

Condition: If ordered products categories is ANY on Category: "Juice"

Action: Assign Tag "Juice lover"

In combination with Latest post mails

Send newsletter with new products only in the Category Juice to the user with tags: Juicy lovers

Every 15 days.

Ivan Martinez: Got it, thank you for sharing an example!

If I may rephrase, it sounds like you'd like to tag customers based on their interests (and the types of products they purchase), and then periodically share with them new arrivals based on their past purchases.

Does this sound like a fair rephrasing of what you had in mind?

Tautvidas: Yes, for this quick example. But there are more tasks that can be implemented based on customer conditions, its like adding the Segmentation capabilities as a Condition criteria on the Automations.

Tautvidas: Any update regarding automations soon? Also i forget to add that is critical to add the condition based on email actions. meaning if the email was open follow one path, if not follow a different path, basically customer journeys.

Ivan Martinez: Hi Ivan, thanks for following up and sharing helpful feedback!

We're actively working on automations. Currently we're adding additional WooCommerce triggers like Abandoned cart, and the team will be looking next into filtering triggers based on customer properties - using options similar to what Subscriber Segments already offer.

Conditionals are on the roadmap as well, but will take a bit longer to get to, and will likely be preceded by a more detailed automations statistics view.

Adrian: Hello Adrian, we've explored goals, but don't yet have them in our near-term roadmap. Could you please a bit more details about your specific problem you're looking to solve with goals?

Tautvidas: Hi Tautvidas, an example would be an email sequence with a goal that triggers when a subscriber purchases a WooCommerce product, gets added to a list, or gets a tag applied.

If there are 3 emails in the sequence, and the subscriber completes the goal after the first email, then MailPoet would skip the remaining emails/steps in the sequence.

In this example, the subscriber would stop receiving irrelevant emails because they already took the desired action.

Adrian: Thank you for sharing the additional context - early stoppage is a great use case!

We do indeed plan to look into Goals as part of the Automations roadmap, but it might happen in later phases. Currently, we're working on adding some of the other basics, like additional ecommerce triggers for Automations (e.g. abandoned cart or post-purchase), but are surely moving towards it.

When we know more - we'll be happy to share an update.