Customers will enter a series when they match the filters in any of the entry rule blocks. Any rule block at the start of a path is automatically set as entry rules:

You can have multiple rule blocks, which will allow customers to enter more than one path at a time.

There are multiple ways for a customer to leave a series, they can exit according to your exit rules, become disengaged, or finish a path.

In your series settings, you can define a set of rules that if matched, will cause a customer to exit the series. Exit rules can be based on any attributes or events you track about your customers or their companies:

If a customer’s data is updated to match the rule they will exit the series.

For a simple way to remove specific customers from a series, just add an exit rule for all customers with a certain tag, then you can apply it as needed to anyone who should exit the series:

Once users hit the exit rule, they will exit the series and will no longer receive any messages from that Series. Users that exit the Series from the exit rules can re-enter the Series again as long as the Series allows re-entry, they no longer match the Exit rules and they still match the entry rules.

You can add multiple exit criteria now and those users can follow the and/or flow, too.

Content events like If the user clicks the message will be matched if the customer has clicked any of the versions of that message they received previously, not just in this individual entry and journey through the series.

For example in the series below, if the user enters on Monday and straight away clicks a link in Email 1, they will then match the second rule block and receive Email 2.

However, if they then re-enter series on Tuesday, they will receive Email 1 again, and the If clicked rule will automatically be true as they had previously clicked a link within Email 1 when they received it on Monday.

After you make an edit to prevent users from prematurely disengaging, new users will go through the original path the way you intend, however, a new path would need to be created to get disengaged users that message.

It is important to note that in any disengagement situation, if the user is in other paths in the Series, they will continue down the path. You can use this to your advantage to make sure users are sent the right messaging moving forward.

If you head to your list of disengaged users, you can apply a tag to all of these users ⤵️

From here you can duplicate the rule block where the users disengaged in the series. When duplicated, you can add the new tag you created for your disengaged users to this rule block.

Then, we'll connect this duplicated rule block to the block after the user disengaged. This will re-enter the user to the pathway that they were already on ⤵️

The only caveat here is that messages would still not deliver to folks who disengaged due to an email or push notification failure, however, this would ensure that those who may have disengaged before you wanted them to are able to receive the messaging located further along in the Series.

If a customer reaches a rule block they do not match, or a message they can't receive, they’ll wait for the period specified in the block:

After this period, if they still haven’t received the message or matched the rules, they’ll be marked as disengaged and leave this path.

This can happen for a number of reasons:

In any of these situations, if the user is in other paths in the series, they will continue down them.

If they match the rules to enter a different path in the future, they will enter at this point.

If there’s a fallback path in place for customers who don’t match a rule block, or receive a message, they’ll proceed down this path instead, and won’t be marked as disengaged:

If a customer reaches the end of a path in the series and have no other content to receive (in another path for example), they’ll be marked as ‘Finished’ and leave the series:

Customers re-enter a series when you are using scheduled or event-triggered entry rules. You can allow customers to re-enter the same series multiple times. It’s useful when you’ve got a set of messages you want to send to customers when a recurring event happens such as a subscription expiring, or a purchase being made.

You’ll find options to allow users to Enter more than once:

They can still re-enter if:

Whenever a customer logs in to your app, or visits your website, and is tracked by Intercom, they’ll enter any series where they match the entry rules for a path.

If they haven’t logged in or visited your website, entry rules are checked once an hour for anyone who should enter. Rule blocks in the middle of a path (when the customer has already entered the series) are checked approximately every 30 minutes.

To target customers based on their interaction with another series, you can add series engagement rules in a rule block.

Example: “If a customer has started series A, don’t send them series B”.

Just select the event to base your rule on:

Then, select the condition (has or has not) and the specific series:

If you have wait blocks inside a series such as Wait to come online, the same user can get stuck at that wait block multiple times for multiple entries/journeys. Then when they finally do come online, they will get delivered that message that they were waiting for multiple times.

In the example above, a user is entering daily. As the user has not come online yet, each entry will get stuck waiting to show the post message. Then if on the 8th day, the user finally comes online, they will get shown the same post 8 times all at once.

To solve this and avoid a build up of new users at each block, update Wait up to rules to be the same period as the multiple entry period.

Hitting a series goal will not automatically exit a customer from your series, if you’d like them to exit upon hitting the goal, you must add this as an exit rule too.

For company goals, the list does not include a user name, or buttons to tag or message users.

If you have a live series, where customers have already entered there are some things to consider before editing it.

If you delete a live series, all customers will exit, and they’ll receive no further content.

Yes, this is to ensure that every series is simple to manage, and works smoothly. Current limits in place:

Hard limits are important product limits to protect infrastructure and the ability to process Series efficiently.

Hard limits are outlined below:

An edge connects two nodes in a Series.

A node represents a block within a Series. The are associated to a Ruleset, which determines what happens at that Node. They can also control behavior, such as waiting before progressing down the appropriate Edge(s).

It’s not possible to create a series with infinite loops, where a customer returns to a previous point in the series and receives the same content again. You’ll see the following warning if you attempt to do so:

There are a couple of options available if you only want to send your Series to people who match the criteria going forward.

You could base the entry rule on an attribute that people will only match after today - for example, if this is an onboarding Series, you could use "Signed up after [today's date]":

Or, if it's not a criteria you can easily pin down with an attribute, you could instead *tag* all of your current users from the Contacts list, and then exclude that tag from your Series entry rule.

If you group your users by company in Intercom, there are some things to keep in mind when creating rules in a series.

If you use company data in a rule block like ‘Company size is greater than 50’ your users will be checked against the rules once per company.

For example, if you have a user who is a member of two companies of different sizes:

This user will be treated as two distinct combinations of user and company:

Each of these ‘versions’ of the user can match the rules individually and proceed down different paths accordingly. So ‘User at company 1’ would match this rule, and proceed down ‘Path 1’:

And ‘User at Company 2’ would not match, so would proceed down ‘Path 2’:

This means, a single user can be in more than one path, and receive messages from each of them.

If a user matches a rule with more than one company, multiple ‘versions’ of that user will proceed down the same path, and receive each message once per company.

So if you changed the rule in this example to ‘Companies with 20 people or more’ both ‘User at Company 1’ and ‘User at Company 2’ would proceed to the message in ‘Path 1’, and the user would receive it for each company that matched the rules:

If there is no company variable added to the body (content) of your message, it is expected behaviour for the Series to send that message multiple times to a user if they are associated with more than one company. This occurs because of the fallback we use when there are no company variables added.

I would recommend adding a company variable to the body of your message to avoid duplicates to resolve this issue. With a variable added, a copy of the message will send only for each of the user’s companies that matches the rule block.

If you'd like to test a series before you set it live for your customers, add a specific entry rule for your email address and only you can enter:

For example, if you're testing an onboarding series, you should sign up as a new user and complete the same actions they would take in your product to receive the messages in your series.

Then when you're happy with how it performs, you can remove the specific email address rule, and it will start matching other users.

To set a start date for your Series, you can add a wait block after the entry rules for "Wait until [X date]", before your first messages send.

We don't have a feature to set a stop date for a Series currently, but one option would be to set up a separate path in the Series with the same entry rules and a wait block that waits until the date you want it to stop, and a tag block to tag the users at that date, then set that tag as your Series exit criteria, so that all users in the Series after that date are tagged and immediately exited.

​

Yes, you can consume your Series metrics using the content_stat.series Webhook. Subscribe to the Series content stat topic along with any of the content types which can be included in a Series, and you'll receive notifications on your endpoint URL when an event occurs.

You can set up all your messages in a single path from their entry rules, with “If matched” arrows leading to the next block, making your messages always send in a consecutive order. You can add “If not matched” arrows leading to later blocks if you want them to send in order, but have the option to skip some if the user doesn’t match for it. Or, you can have multiple messages and paths links to your chosen entry rule to allow all messages to send at any time, in any order.

“Try to match once” is useful for rules that check user attributes, but don’t rely on the user to take an action. For rule blocks that need the user to take an action (e.g. come online to receive an in-app message, or open an email message), they’ll want to use “Try to match for X days/hours/minutes” to give the user some time, otherwise it would immediately check for that action and move on.

If you see an error message that say "A multi entry series must have a single starting point", this indicates that your Series has multiple entry rules, and allows customers to re-enter the Series, which isn't supported.

Customers can re-enter a Series multiple times but when using this feature, you can only have one Entry Rule Block for the Series.

To resolve the error, remove the extra entry rule blocks from the Series, or update the entry rules so a customer can only enter it once.

To find out why users who shouldn't have entered the Series did so, check the timestamps of when the users entered the Series and when they unsubscribed from emails.

If they entered the Series before unsubscribing from your emails, they would have still matched the Series entry rules block at that time.