In automation campaigns you can segment your contacts based on the criteria of a triggering event - also known as the ‘entry trigger’.
See also: Automation campaign triggers
You can only segment by triggering event for the following entry conditions:
- The contact has placed an order
- The contact has visited the website
- The contact had abandoned a basket
Filter conditions
The following conditions are available when you segment on a triggering event:
| Triggering Event | Filter condition |
|
Contact has placed an order
Note: These filter conditions are checked against the triggering order's most recent status at the time the contact reaches the segment node. E.g. If the order status changes from 'complete' to 'shipped', before the contact enters the campaign (and before the entry wait time has expired), the condition will check against the 'shipped' status.
|
...which includes a product that matches |
| ...which does not include a product that matches | |
| their last order | |
| their nth order (e.g. 2nd order) | |
| an order with a grand total | |
| an order using a coupon code | |
| an order in a store | |
| an order with status | |
|
an order via a channel
Note: Order channels (e.g. online store, mobile app, in store, phone) must be defined in your API call.
|
|
|
Contact visited the store website
Note: You can also include visits made via your mobile app.
|
viewed a product |
| viewed a product with an attribute | |
| viewed a product for a time period | |
| visited from a source | |
| visited a store | |
|
Contact has abandoned a basket
Note: You can also include visits made via your mobile app.
|
A basket which includes a product that matches |
| A basket which does not include a product that matches | |
| A basket created in a specific store | |
| A basket with specific quantity of items | |
| A basket with a total value | |
| A basket with a currency | |
| A basket with a specific quantity of the same product | |
| A basket with a total spend for the same product |
How to segment on triggering events
Go to your automation campaign and select any of the triggering events listed above.
Define your wait note and exit condition as required.
Select the + icon to add a segment node, then select Configure (cog icon) and Triggering Event.
Select your triggering event, then click +ADD CONDITION and set the filter conditions for the segment.
Create the rest of your campaign flow as usual.
Including traffic from your mobile app
If you have a mobile app integrated with Ometria there's an extra step to include contacts who visited your store or abandoned a basket via your app.
You need to add a second condition under your triggering event condition:
- made a visit on - which is - App
If you don't specify 'App', Ometria only includes contacts who visit via the web in the segment.
For campaigns where you want to include both types of visit, add the filter:
- made a visit on - which is one of - Web, App
You can also exclude 'App' contacts using this filter:
- made a visit on - which is not - App
Comments
0 comments
Article is closed for comments.