Atlas L6ynztjd84

Stay updated on the status of all your company's support tickets.

Customer portal

Loops let you send emails based on something happening, like a contact property updating, a new contact being created or an external event happening in another platform.

To start building your Loop, select a template or start from scratch.

Templates are added often and we're always open to taking suggestions!

A Loop is an email sequence that can be triggered by different events, and containing emails, delay timers and branches.

You can add new nodes to your loop by hovering over an arrow between nodes and clicking the 

There are five types of nodes available in loops:

The first node to add to a loop is the trigger. This is what will send new people into the loop.

: Triggered whenever a contact has been added to your audience. Only contacts who have been added via a [form](/forms/simple-form), the [API](/api-reference/intro) or an [integration](/integrations) will be added based on this trigger. Contacts uploaded via CSV or added individually to the audience table will not be included.

 Triggered whenever a contact property changes from one value to another. Can also conditionally trigger only if the previous property matches the inputted value.

 Triggered whenever a contact is added to a 

 is sent to Loops by the API or an integration. This this trigger you can start a loop based on interactions in your app. Common custom events are 

You can add emails at any location inside your loop, giving you flexibility to send mail immediately after the trigger or after a delay. You can also send to specific contacts by adding an audience filter, or by branching your loops.

You can add unliited emails to each loop.

To edit an email, click on the email node, then 

When a loop is active, you cannot edit the email. Click 

 to pause the loop and make changes to your email (and any other nodes). While paused, new contacts will be queued for up to 24 hours; they will enter your loop as soon as you save your email by clicking 

A timer adds a fixed time period between two nodes in the loop.

For example, you could add a "3 day" timer after a "Contact added" trigger to send an email three days after a signup.

You can select the “Immediately” option to bypass the timer or any increment of time to extend the duration of the Loop.

You can add multiple timers to your loops, to add delays in different parts of your workflow.

 with a loop trigger, you can create fine-tuned Loops to target specific contacts.

For example, you can check in with contacts that have not signed up as a paying user 3 days after signing up by setting the Custom Event to 

 the Timer duration to 3 days and the audience filter to 

By combining events, timers and the audience filter, you should be able to target contacts at any stage of the lifecycle.

 tab to view simple metrics inline within the builder.

 to view detailed metrics for your Loop.

You can test if a Loop works as expected by using email addresses with 

First, add these as contact in your audience, then depending on how your Loops are set up, you can add and update properties, or send events to these email addresses to see how contacts move through your Loops.

 email addresses so this is a good method to test emailing contacts without affecting your sending domain’s reputation.

You can also send test emails for each of the emails in a loop. Click on an email node and then the 

 airplane icon above the preview tha appears.

Guide

Learn how to trigger a Loop to start sending emails.

A Loop trigger is an event, contact update or contact addition that starts a Loop. For example, if you create a Loop that sends a welcome email to new contacts, the trigger would be when a new contact is added to your audience.

There are currently four types of triggers that you can use to start a Loop: 

 trigger will start a Loop when a contact is added to your audience. This trigger is useful for sending welcome emails to new contacts or sending a series of onboarding emails to new customers. This trigger works for contacts added via an integration, a form, or an API call. Contacts uploaded via CSV or added individually to the audience table will not be included. As long as the contact is added to your audience with an automatic method the Loop will start.

This trigger requires no additional setup. Once you create a Loop with this trigger, you can start adding contacts to your audience and contacts will enter the Loop.

 trigger will start a Loop when a contact is updated in your audience. This trigger is useful for sending emails to contacts based on their actions or behavior. For example, you can send a series of emails to contacts who change their subscription plan from free to paid or from paid to canceled.

You can also set the trigger to only start the Loop when a specific field is updated from a specific value to another specific value. For example, you can send a series of emails to contacts who change their subscription plan from free to paid but exclude contacts who have updated their subscription plan from paid to canceled.

 trigger will start a Loop when a contact is added to a 

. It triggers every time a contact is added to a list (so if the contact is removed from a list and then re-added, it will trigger again).

When using this trigger, make sure to select the mailing list from the menu icon top right of the editor window.

 trigger will start a Loop when a contact receives a specific matching event sent via API, Integrations or a form. This trigger is great for events like payment received, order placed, or a new message received.

You can choose to trigger a Loop just the first time a contact matches the trigger settings or every time the contact matches.

For example, if you want to send to a contact every time they update their subscription plan, you can choose to trigger the Loop every time the contact is updated (select "Every time").

However, if you want to send a welcome email to a contact just the first time they are added to your audience, you can choose to trigger the Loop once when the contact is added (select "One time").

You can change the trigger type at any time. For example, if you create a Loop with the Contact Added trigger, you can change it to the Contact Updated trigger at any time.

Triggering Loops

Learn how to pause and stop a Loop to control the sending of emails.

Both pausing and stopping a Loop will prevent any emails from sending until you resume the Loop, but there are a few key differences.

When you pause a Loop, you can resume the Loop at any time.

During the pause, all contacts that were scheduled to receive an email will receive it once you resume the Loop. However, this assumes that these contacts still meet the necessary criteria to receive the email (e.g., they are subscribed and match any audience filters or other conditions you've set).

New contacts that match the Trigger conditions while the Loop is paused will enter the Loop but only within the first 24 hours. Contacts that qualify for the Trigger after the 24-hour mark will not enter the Loop.

We will notify you via email once the 24-hour period has elapsed, reminding you that contacts will no longer queue to enter the Loop if you resume it.

The 24-hour limitation prevents contacts from entering a Loop that has been paused for an extended period and receiving irrelevant emails. For instance, if your Loop sends a welcome email to new contacts, you wouldn't want a contact to join the Loop three months after signing up and receive a welcome email.

Stopping a Loop will not queue any new contacts to enter the Loop. Any contacts that were queued to enter the Loop will not enter the Loop. That's the key difference between pausing and stopping a Loop.

Pausing Loops

Branching loops allow you to send different emails based on a contact's properties within a single Loop.

A common use case for crafting a user journey is to send different emails based on whether a contact has completed an action or not.

For example, you may want to send a different email to users who are free users versus users who are paid users.

You can do this by creating a branching Loop.

To create a branching Loop, you just need to add a new node and select 

 as the node type. Two audience filter nodes are automatically created for you and you can edit the audience filter settings for each node to send to different contacts based on their properties.

The audience filter nodes created after a branching node can be toggled between two settings:

 The audience filter will apply to all nodes downstream of the Loop.

 The audience filter will only appy to the next node in the Loop.

A common use case for the "All following nodes" option is creating a global Audience Filter. You can add an Audience Filter node after a Trigger node which will ensure that contacts who do not match the audience filter will not remain in the Loop. This is useful for sending a welcome email to new free contacts and then removing them from the Loop when they become paid contacts.

Loop builder

Guide

Triggering Loops

Pausing Loops

Branching Loops