A trigger split is useful when you want to make sure that activities within an automation are triggered by a certain action—such as a product purchase. If the action isn’t performed, you can wait up until a certain time has passed, for example seven days, before sending the customer forward in the automation.

The trigger split is, just as it sounds, a combination of a trigger and a split. It works similar to a conditional split in that it separates the flow based on a set of conditions. The difference is that it won’t evaluate whether the statement is true/yes or false/no immediately but waits for a specific event to occur.

It can also be compared to a time delay, which simply postpones the next action with your chosen time regardless of the customers’ actions.

How to use it

A common use case for a trigger split is adding it to an automation promoting some type of product or promotion where you want to see if the included contacts make a purchase.

For each trigger split you first need to set a maximum amount of time to wait for the specified event. If the event occurs before the specified time, the contact will proceed down the “yes” path; otherwise, it will take the “no” path.

In our example we’ve used the Product purchase trigger. If no other conditions are set, contacts that make a purchase will proceed down the “yes” path, but you can be more specific. You can, for instance, configure the trigger split to only accept purchases of a specific article group. This allows for a more precise communication and a more personalized experience.

Example use case

For customers that purchase a specific type of product, we want to remind them of complementary products. If they do not purchase any such item within 7 days, we send a reminder.

Article last reviewed 06 October 2025 06:25