Skip to main content
New Welcome Automation Presets
Ira avatar
Written by Ira
Updated over 3 months ago

Please note that on July 24, 2024, we launched new Welcome presets.

Any new welcome automations created from these presets will include a fresh set of trigger & trigger filters, which we plan to roll out to other platforms in the future.

If you've got a welcome automation set up already, there's no need to make any adjustments—it will still work just fine. We'll update your automation with the new trigger logic later unless you want to test our latest addition yourself.


This user guide provides instructions on configuring new welcome workflows using the Subscribed to Marketing trigger.

About Subscribed to Marketing Trigger

  • From now on workflows created from Welcome presets will have Subscribed to marketing as a trigger.

  • With this trigger, you have more flexibility and control over welcome email automation. It provides a more comprehensive view of new subscribers entering your marketing funnel.

  • This new trigger will fire whenever a contact subscribes to receive marketing communications, regardless of the subscription method (email, SMS, push notifications, etc.).

  • You can apply trigger filters to target specific subscription methods, such as only those who signed up via an Omnisend form, SMS (text-to-join), push notifications, checkout, and more. This allows you to personalize the welcome experience based on how the subscriber joined your list. Read further to learn more about available trigger filters.

Setup Process

To create the Welcome workflow, proceed to the Automations tab → click on the Create workflow button and pick one of the suggestions for the Welcome automation.

From here, you can pick the workflow using one email, three emails, or one email + 1 SMS. Regardless of the chosen preset, you can modify the workflow structure by adding or removing messages.

Trigger & Trigger Filters

Once you have created an automation from a preset, you can see the list of trigger filters automatically applied to your automation within the selected preset. 

By default, everyone who completes the action specified in the trigger will qualify to enter your flow. This means your customers will qualify to enter the flow as soon as they meet the trigger and trigger filters.

Trigger filters allow you to focus on a specific group of contacts by filtering out only a portion of them. They work by analyzing the data from the event that triggers the flow, effectively narrowing down the target audience.

For instance, you might choose to restrict your welcome automation to a particular subscription channel, ensuring that notifications are only sent to individuals who have subscribed via the SMS channel or any other available channels, depending on the combination you prefer.

Below, you will find a list of available trigger filters and their meanings.

Trigger filter

Available values

Explanation

Core filters ⤵️

Channel subscribed to

  • Email

  • SMS

  • Push

Indicates the channel through which the contact subscribed.

First subscription

  • True

  • False

Indicates that this is the first subscription event for this contact through this channel.

Language

Browser language of the contact.

Origin

  • Omnisend

  • API

Origin of the subscription event either Omnisend form or contacts passed via API (including 3rd party apps).

Previous subscription status

  • subscribed

  • unsubscribed

  • non-subscribed

Indicates the previous channel subscription status when the event results in its change.

Previous subscription status date

Date when the previous channel subscription status had been assigned.

Subscription method

  • Signup form

  • Text to join

  • Browser notification

  • Preference page

  • Checkout

  • Imported as subscribed

  • Was manually subscribed

  • Other

Indicates how the contact subscribed.

  • Signup form: contact subscribed via Omnisend or 3rd party form.

  • Text to join: subscribed via texting the JOIN keyword.

  • Browser notification: subscribed to push channel via browser prompt.

  • Preference page: subscribed to email or sms via the preference page.

  • Checkout: consented to receive marketing when placing an order.

  • Imported as subscribed: this happens if you import contacts to Omnisend with opt-in dates or select that they have consented.

  • Was manually subscribed: this happens if you change the contact's status from non-subscribed to subscribed in Omnisend Audience.

  • Other: subscribed externally, outside Omnisend, and we cannot determine the method.

Subscription method details

Any additional information related to the subscription method, like import ID and file name, Order ID, SMS keyword, etc.

Form filters ⤵️

Discount

Discount code that was displayed for the subscriber in the signup form.

  • Wheel of Fortune discount code;

  • Code that you entered in the discount block in your form.

Form Name

Omnisend form name which a contact submitted to subscribe.

Form Settings

Possible form settings:

  • Wheel of Fortune

  • Teaser

  • Discount block

  • Subscribed button

  • Link button

  • etc.

Identified blocks that were added to the Omnisend form,  through which the subscription happened.

Form Type

  • Popup

  • Landing page

  • Embedded

  • Flyout

Omnisend form type, which the subscriber used.

Just remember, if you come across an empty value option in your automation, it's because you need a subscription event to occur after enabling the automation for it to begin gathering data.

Let's say you turn on the automation and then subscribe using one of your forms. After that, you'll start to see options like Language, Form type, and other trigger filters appearing in the list since the subscription event has taken place.

Note that an additional filter, 'Origin is API, ' is available. It targets subscribers added via third-party integrations or API calls.

This is particularly useful for those who collect contacts through multiple platforms (e.g., Omnisend forms and third-party apps) and want to apply different welcome logic for different subscriber groups.

Trigger Filter vs Trigger Filter Groups

Trigger Filters

Trigger filters are individual criteria used to determine when a specific action should be initiated. They are the basic building blocks for creating targeted marketing campaigns. They can be connected with either 'AND' or 'OR' logic; different logic cannot be combined within a list of varying trigger filters.

The GIF illustrates how three distinct trigger filters are linked through a single logic. If you apply' AND' logic, the setup will trigger only when every condition is fulfilled, whereas with 'OR' logic, the automation kicks in if any of the specified criteria are met.

Trigger Filter Groups

Trigger Filter Groups expand on the concept of individual trigger filters by allowing multiple filters to be combined into groups. These groups can be connected using either 'AND' or 'OR' logic, providing greater flexibility and precision in targeting subscribers.

  • 'AND' Logic: All conditions within the group must be met for the trigger to activate.

  • 'OR' Logic: Any condition within the group can activate the trigger.

Example of Trigger Filter Groups

Imagine you want to create a targeted marketing workflow with the following criteria:

  1. Subscribers must have signed up for the email channel.

  2. It must be their first subscription.

  3. They must either be added through an API (3rd party app) or have used a sign-up form.

Group 1 (AND Logic)

  • Channel subscribed is Email

  • The first subscription is true

Both conditions must be met in this group for the trigger to fire. This means that only subscribers who have signed up via email and for whom it is their first subscription will be targeted.

When combining two groups with 'AND' logic, the trigger must fire if all conditions across both groups are met.

Group 2 (OR Logic):

  • Origin is API

  • The subscription method is a signup form

If either condition is met in this group, the trigger will fire. This means that subscribers added through an API (3rd party apps) or those who used a sign-up form will be targeted.

With the setup above, the trigger will fire only if all these conditions are met. With this setup, you can simultaneously target new email subscribers from the Omnisend form and any new subscribers added through third-party integrations or APIs.

If you're new to Omnisend and need details on how to set up Automation and explore other features, please check out this user guide ⤵️

Troubleshooting

When setting up your welcome email workflows, it's essential to ensure that your subscribers receive a relevant experience based on their channel preferences. Below are guidelines for troubleshooting common scenarios related to sending welcome emails:

Understanding Subscription Settings:

  • When you start a workflow with the 'Subscribed to marketing; trigger and do not add any specific trigger filters, the system defaults to sending welcome emails whenever a contact subscribes to any channel: Email, SMS, or Push notifications.

Rule of Thumb for Single Message Types:

  • To avoid this issue, it’s crucial to use trigger filters in your workflow. If your workflow consists solely of welcome emails, make sure to configure the trigger filter to specify the channel through which the contact subscribed.

  • Example: If your workflow contains only email messages, set the trigger filter to Channel subscribed to = Email. This ensures that the welcome email is sent only when a subscriber opts in through the email channel.

Still have questions? Feel free to chat with our support team in-app or send us an email at [email protected] 💛

Did this answer your question?