Triggers

With Triggers, Relewise can be configured to call other systems when certain criteria are met.

Triggers are evaluated by default every fifteen minutes. When they are evaluated it is checked if any users fulfill the criteria for one or more triggers. If this is the case, this information is passed on, usually as an API call to a 3rd part customer system.

Oftentimes this 3rd party system is the customer's e-mail marketing platform, which, if permission has been collected, sends an e-mail to the user. Other common scenarios for trigger actions are an API call to Facebook Messenger, sending an SMS, notifying an internal salesperson, or updating a CRM system.

It is possible to set up rules as to how many triggers can be activated for a given user within a specific time period (both for the same type of trigger and triggers in general), as well as specifying the priority order between triggers. Triggers can also be limited to only affect authenticated users or users belonging to specific classifications.

Relewise supports the following triggers, all of which can be configured as needed.

AbandonedCart

The AbandonedCart trigger can be configured to be activated when a user adds something to the cart but does not complete the order.

When tracking a cart, it is not necessary to specify the Name value if you are using the .NET or PHP SDKs. If you need to track the ID of the cart, it should not be added as the Name, and instead be added as a Data Field. If you are using TS/JS or Java, Name of the cart should be set to default.

Example of configuration

The user left the cart 2 hours ago and has not met the criteria for any trigger within 7 days.

AbandonedSearch

The AbandonedSearch trigger can be configured to be activated when a user performs a specific type of search, and can additionally be configured to only trigger if no entity views of the same type have happened within a given period.

Example of configuration

The user is known by their email and has had no activitiy in the last 15 minutes but has made a product search between 20 and 30 minutes ago without having viewed any products since.

ProductInterest

The ProductInterest trigger can be configured to be activated when a user shows interest in a product. What "interest" specifically looks like can be configured.

Example of configuration'

The user has viewed the product 3 times within 30 days in at least 2 unique visits to the store and has not activated a ProductInterest trigger within 7 days.

CategoryInterest

The CategoryInterest trigger can be configured to be activated when a user shows interest in products in a given category. What "interest" specifically looks like can be configured.

Example of configuration

The user has viewed the category page 3 times and at least 1 product in the category within 14 days and has not activated a ProductInterest nor a CategoryInterest trigger within 7 days.

UserActivity

The UserActivity trigger can be configured to be activated when a user has abandoned the browser.

Example of configuration

The user is known by their email and has visited the site at least 15 minutes over the past 3 hours, but has not had any activity in the last 15 minutes.

ProductChange

The ProductChange trigger can be configured to be activated when a user has shown interest in a product, and a certain data key on the product changes value.

The ProductChange trigger is useful for setting up a Price Drop flow, in which customers are alerted when products they have shown interest in drop in price.

It can also be used to create a flow for Back in Stock, where the user is alerted when a product they have shown interest in go back in stock from having been sold out.

Example of configuration

The user has shown interest in a product within the past 48 hours, but the product stock = 0. A product integration sets stock = 10, which causes the trigger to fire.

Example of configuration

The user has shown interest in a product within the past 48 hours. The product's price is updated, and drops from 30 USD to 22 USD. This causes the trigger to fire.

VariantChange

The VariantChange trigger is similar to the ProductChange trigger, and can be configured to be activated when a user has shown interest in a variant product, and a certain data key on the variant changes value.

The VariantChange trigger is useful for setting up a Price Drop flow, in which customers are alerted when products they have shown interest in drop in price.

It can also be used to create a flow for Back in Stock, where the user is alerted when a product they have shown interest in go back in stock from having been sold out.