When someone fires the event that is included in your Inclusion Rule they will enter your flow, as long as they are not excluded by another Event or Property

Inclusion Rules allow you to define when someone should be included in a Flow, based on a user Event that is tracked by ShopMessage. Right now, Inclusion Rules are limited to one event.

When someone fires the event that is included in your Inclusion Rule they will enter your flow, as long as they are not excluded by another Event or Property

First you'll want to chose the event that will set your flow into motion. Some Event options are ViewProduct, UpdateCart, MessageSent, MessengerOptin, QuickReplyReceived or PurchaseComplete.

By default, your Event selection will default to ALL Events of that type, this is defined by the "has any properties". This means that any user who has triggered the view product event will be entered into your flow.

You can further define your audience by choosing Event Properties. The properties available here are "has" and "does not have".

For example, you may want to choose to target all users who viewed product_type shoes.

Exclusion Rules allow you to define when someone should be excluded from a Flow so that they do not receive messages from this Flow. Exclusion Rules can be based on one or more Visitor Property or Event. You can add as many exclusion rules as you would like. 

Exclusion Rules work with AND/OR filters. When you select an And Filter, your users must match both the initial and Exclusion Rule AND the secondary rule. When you select an Or filter your users must match one rule OR the other to be excluded from a filter.

By default, ShopMessage has added two Exclusion Rules to every custom template. These rules will exclude any user who has previously selected a button with the action set to "unsubscribe" or any user who has clicked a "No Thanks" button in the past 30 days (this is our "snooze" feature).

Here's what these two rules look like:

When creating a custom Flow, you'll likely want to add an Or rule to the two default Exclusion Rules. 

For this example, we'll want to exclude any user who has fired a PurchaseComplete event when the product_type is shoes.