Loymax, 2026

Wiki source code of 3.2. Triggers

Show last authors
1 (((
2 **Trigger **is** **an event that activates a [[campaign>>doc:Main.Using.Smart_Communications.Campaign_list.WebHome]]. Each type of triggers has its own set of parameters. Once triggered, the chain receives an array of [[customer profiles>>doc:Main.Using.Smart_Communications.Customers.All_clients.WebHome||anchor="Profile"]] that satisfy the conditions set in the trigger.
3 )))
4
5 (% class="box" %)
6 (((
7 **Trigger example**: a customer has placed an order. This trigger includes all customers who have made a purchase within a period set in the settings (by default, the receipt search depth is 3 days). Then the trigger is activated on a daily basis, i.e. every 24 hours.
8 )))
9
10 === Trigger editing ===
11
12 When a new campaign is created, there is a trigger in the field for editing. By default, it is the **New order is placed **trigger. To change the campaign trigger, double-click it with the left button of the mouse or click the right button and then select the Edit icon. Select a new trigger from the drop-down list and click **Оk**. 
13
14 |(% style="border-color:white; text-align:center; width:702px" %)[[image:attach:image1.png]]|(% style="border-color:white; text-align:center; width:736px" %)[[image:attach:image2.png||height="300" width="436"]]
15
16 **The following triggers are available in the Smart Communications module:**
17
18 {{toc start="6"/}}
19
20 (% class="table-bordered" style="width:1447px" %)
21 (% class="info" %)|(% style="width:428px" %)**Trigger**|(% style="width:1010px" %)**Description**
22 |(% style="width:428px" %)(((
23 ====== Lost cart on the site ======
24 )))|(% style="width:1010px" %)(((
25 Allows to track events when a customer added products to the cart but did not place an order. 
26 The cart is considered abandoned if:
27
28 * the customer added products to the cart, but did not place an order;
29 * N seconds, minutes, hours have passed since the last actions with the cart (the settings are determined  upon agreement with the Partner).
30
31 (% class="box infomessage" %)
32 (((
33 The [[JS-tracker>>doc:Main.Integration.Integration_of_SC.JS_tracker.WebHome]] should be set up on the Partner's website for correct operation of this trigger.
34 )))
35 )))
36 |(% style="width:428px" %)(((
37 ====== Lost view on the site ======
38 )))|(% style="width:1010px" %)(((
39 This is a common trigger for abandoned viewing of product or product category. It allows to track events when a customer viewed product/product category on the website, but did not add it to his/her cart. Viewing is considered abandoned N seconds, minutes, hours after the customer has viewed a product (the settings are determined  upon agreement with the Partner).
40
41 (% class="box infomessage" %)
42 (((
43 The [[JS-tracker>>doc:Main.Integration.Integration_of_SC.JS_tracker.WebHome]] should be set up on the Partner's website for correct operation of this trigger.
44 )))
45 )))
46 |(% style="width:428px" %)(((
47 ====== Lost view of category ======
48 )))|(% style="width:1010px" %)(((
49 The trigger allows to track events when a customer visited the product category on the website, but did not add products to his/her cart. Viewing is considered abandoned N seconds, minutes, hours after the customer has viewed a category (the settings are determined  upon agreement with the Partner).
50
51 (% class="box infomessage" %)
52 (((
53 The [[JS-tracker>>doc:Main.Integration.Integration_of_SC.JS_tracker.WebHome]] should be set up on the Partner's website for correct operation of this trigger.
54 )))
55 )))
56 |(% style="width:428px" %)(((
57 ====== Lost view of product on the site ======
58 )))|(% style="width:1010px" %)(((
59 The trigger allows to track events when a customer viewed the product on the website, but did not add it to his/her cart. Viewing is considered abandoned N seconds, minutes, hours after the customer has viewed a product (the settings are determined  upon agreement with the Partner).
60
61 It is possible to configure this trigger for viewing items of a specific price category. If the checkbox **Check price** is enabled, the trigger will be activated for products the price of which is higher than the specified price.
62
63 |(% style="border-color:#ffffff; text-align:center" %) [[image:attach:Lost_view_en.png]]
64
65 The screenshot shows an example of the setting, where the trigger will be activated only if customers view products with a price higher than 10 US dollars.
66
67 (% class="box infomessage" %)
68 (((
69 For correct operation of this feature in the [[JS-tracker>>doc:Main.Integration.Integration_of_SC.JS_tracker.WebHome]], it is required to transmit the product price value in the **price** field of the **view_product **event.
70 )))
71 )))
72 |(% style="width:428px" %)(((
73 ====== Anniversary (Х days before/after): ======
74
75 * first order/receipt
76 * last order/receipt
77 * birthday
78 * date of registration
79 )))|(% style="width:1010px" %)(((
80 (((
81 Allows to track anniversaries of events.
82
83 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Anniversary_en.png]]
84 )))
85
86 (((
87 The trigger allows:
88
89 1. Define the type of **event**:
90 1*. Customer registration in the Loyalty Program (on the website, at the cash register or in Mobile App);
91 1*. Customer's first order;
92 1*. Customer's last order;
93 1*. Customer's birthday.
94 1. Set the **interval **for launching the campaign. The interval can be in years, months, days.
95 For example: 
96 1*. Every year;
97 1*. Every two months;
98 1*. Every 10 days.
99 1. Set a **delay**.
100 For example: 
101 1*. Birthday greetings 15 days before the due date (delay "-15 days");
102 1*. Bonus points a week after the first purchase (delay "+7 days").
103
104 Examples of using this trigger :
105
106 * Every year send birthday greetings and bonus points 15 days before the customer's birthday.
107 * Send congratulations on the anniversary of the customer's first purchase.
108 * If the customer has not purchased within a year, send him/her a promocode to encourage their next purchase.
109 * Offer participation in a promotion to celebrate the anniversary of the customer's registration on the website.
110 )))
111 )))
112 |(% style="width:428px" %)(((
113 ====== Days since order ======
114 )))|(% style="width:1010px" %)(((
115 The trigger is activated when the specified number of days has passed since the first/last receipt.
116
117 For example, the customer has not purchased anything for the last 60 days:
118
119 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Days_since_order.png]]
120 )))
121 |(% style="width:428px" %)(((
122 ====== Days since registration ======
123 )))|(% style="width:1010px" %)(((
124 The trigger is activated if the specified number of days has passed from the date of registration:
125
126 * for online stores — number of days since registration on the website.
127 * for offline stores — number of days since registration in the Loyalty Program.
128 )))
129 |(% style="width:428px" %)(((
130 ====== Added a product to the container ======
131 )))|(% style="width:1010px" %)(((
132 The trigger allows to track adding of products by the customer to a specified container.
133
134 Select the required container from the drop-down list in the **Container** field.
135
136 (% class="box infomessage" %)
137 (((
138 **Note**:
139 **Containers **mean customer's individual product lists. For example, the "Cart" container includes the products that were added to the cart but not purchased by a customer. Products can be uploaded to a container with an external file or transmitted by the [[JS-tracker>>doc:Main.Integration.Integration_of_SC.JS_tracker.WebHome]].
140 )))
141 )))
142 |(% style="width:428px" %)(((
143 ====== Product in cart is low on stock ======
144 )))|(% style="width:1010px" %)The trigger is activated if the products, which the customer added to the cart and did not buy, are running low.
145 |(% style="width:428px" %)(((
146 ====== Product price has changed ======
147 )))|(% style="width:1010px" %)(((
148 Allows to track change of product price.
149
150 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Product_price_en.png]]
151
152 Select the required container from the drop-down list in the **Container** field.
153
154 It is also necessary to specify the **direction of change** (the price went down or went up) and set the value of **minimal change **(in dollars or as a percentage).
155 )))
156 |(% style="width:428px" %)(((
157 ====== Customer registration ======
158 )))|(% style="width:1010px" %)The trigger allows to track customer registration in the System.
159 |(% style="width:428px" %)(((
160 ====== Customer registration + filter ======
161 )))|(% style="width:1010px" %)The trigger allows to track customer registration in the System and additionally set the filter **Customer Id contains**.
162 |(% style="width:428px" %)(((
163 ====== Customer visited the site section ======
164 )))|(% style="width:1010px" %)(((
165 The trigger allows to track customer's visit to a certain section of the website.
166
167 To select a section, start typing its name in the **Section** field. The list will display all sections containing the typed text in their names.
168 )))
169 |(% style="width:428px" %)(((
170 ====== Customer visited the site ======
171 )))|(% style="width:1010px" %)The trigger allows to track customer's site visits.
172 |(% style="width:428px" %)(((
173 ====== Viewed product on the site ======
174 )))|(% style="width:1010px" %)(((
175 The trigger allows to track product viewing on the website.
176
177 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Viewed_product_en.png]]
178
179 To select a product, choose **equal **and enter the product name from the product catalog in the nearby field. Or select **contains **and start typing the product name. The list will display all products that have the typed text in their names. This trigger can be used if there is a promo for a specific product or any related product.
180 )))
181 |(% style="width:428px" %)(((
182 ====== Viewed product category on the site ======
183 )))|(% style="width:1010px" %)(((
184 The trigger allows to track viewing product from a specific category.
185
186 To select a product category, start typing its name in the **Category **field. The list will display all categories containing the typed text in their names. This trigger can be used if there is a promo for a specific product category.
187 )))
188 |(% style="width:428px" %)(((
189 ====== Item purchased ======
190 )))|(% style="width:1010px" %)(((
191 The trigger allows to track purchase of a product.
192
193 To select a product, start typing its name in the **Item** field. All products containing the typed text in their names will be displayed in the list.
194 )))
195 |(% style="width:428px" %)(((
196 ====== Item from specific category purchased ======
197 )))|(% style="width:1010px" %)(((
198 The trigger allows to track purchase of a product from a specific category.
199
200 To select a category, start typing its name in the **Category **field. The list will display all categories with the typed text in their names.
201 )))
202 |(% style="width:428px" %)(((
203 ====== Date has come ======
204 )))|(% style="width:1010px" %)(((
205 The trigger allows to launch a campaign on a scheduled date.
206
207 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Due_date_en.png]]
208
209 The field **Wait, hours...minutes ...** allows to set the time of trigger launching. If you don't do this, the trigger will be activated on the scheduled date at 00:00 (according to the time zone specified in the **Settings > General Settings > **[[Contact Details>>doc:Main.Using.Smart_Communications.Settings_SC.Settings.WebHome||anchor="01"]]** > Time Zone**).
210
211 (% class="box infomessage" %)
212 (((
213 If the first action in the campaign is to send SMS/push notification, the messages will be delivered later (at the time specified in **Settings > General Settings > **[[SMS>>doc:Main.Using.Smart_Communications.Settings_SC.Settings.WebHome||anchor="03"]]** > Time interval for SMS delivery**).
214 )))
215
216 Sometimes there is a need to re-use campaigns that start with the **Date has come **trigger. For example, on the 2nd day of last month there was a promo and you launched a campaign to notify about this promo on the 1st day of the same month. A couple of months later, there is a need to run a similar campaign for sending notifications. You can do it by replacing the start date in the trigger and the text about a promo in the message.
217
218 In this case, the value of the **Threshold before second hit **parameter** **should be **less** than the time period passed from the start of the previous campaign. Otherwise the customers will not get into this campaign upon re-use, as the System will consider that the customers have already been hit in the campaign before and they should be excluded.** **
219 )))
220 |(% style="width:428px" %)(((
221 ====== Date come for order ======
222 )))|(% style="width:1010px" %)(((
223 This trigger allows to launch a campaign a few days before/after/upon occurrence of the date specified in one of the order fields.
224
225 For example, an order storage term at a pick-up point may be specified in a separate field. In this case you can set up a notification that the order will soon be retuned back from a pick-up point.
226
227 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Order_date.png]]
228
229 To select a date, start typing its name in the **Date field**. The list will display all fields containing the typed text in the name.
230
231 There are several timing options to start the trigger:
232
233 * On the specified date;
234 * Specified number of days before the date;
235 * Specified number of days after the date.
236
237 The trigger will be activated at 00:00 (according to the time zone specified in the **Settings > General Settings > **[[Contact Details>>doc:Main.Using.Smart_Communications.Settings_SC.Settings.WebHome||anchor="01"]]** > Time Zone**). If it is better to perform further actions during working hours, set the delay using the [[Wait >>doc:Main.Using.Smart_Communications.Campaign_list.Actions.WebHome||anchor="H41F43E43443E43643443044244CA0"]]action or fill in the **Wait, ...hours ... minutes **field.
238 )))
239 |(% style="width:428px" %)(((
240 ====== Date come for client ======
241 )))|(% style="width:1010px" %)(((
242 This trigger allows to launch a campaign on a special date for the customer that was specified in one of the fields of Customer Profile.
243
244 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Customer_date.png]]
245
246 It is possible to tie the campaign launch to one of the following dates:
247
248 * Birth date;
249 * Registration date;
250 * First order date;
251 * Last order date;
252 * Activation date;
253 * Date of last replenishment.
254
255 The trigger will be activated at 00:00 (according to the time zone specified in the **Settings > General Settings > **[[Contact Details>>doc:Main.Using.Smart_Communications.Settings_SC.Settings.WebHome||anchor="01"]]** > Time Zone**). If it is better to perform further actions during working hours, set the delay using the [[Wait >>doc:Main.Using.Smart_Communications.Campaign_list.Actions.WebHome||anchor="H41F43E43443E43643443044244CA0"]]action or fill in the **Wait, ...hours ... minutes **field.
256
257 (% class="box infomessage" %)
258 (((
259 If the first action in the campaign is to send SMS/push notification, the messages will be delivered later (at the time specified in **Settings > General Settings > **[[SMS>>doc:Main.Using.Smart_Communications.Settings_SC.Settings.WebHome||anchor="03"]]** > Time interval for SMS delivery**).
260 )))
261
262 Sometimes there is a need to re-use campaigns that start with the **Date come for client **trigger. For example, there was a promo associated with the customer's last order. A couple of months later, there is a need to run a similar campaign for notifications by replacing the text of the promotion message.
263
264 In this case, the value of the **Threshold before second hit **parameter** **should be **less** than the time period passed from the start of the previous campaign. Otherwise the customers will not get into this campaign upon re-use, as the System will consider that the customers have already been hit in the campaign before and they should be excluded.** **
265 )))
266 |(% style="width:428px" %)(((
267 ====== Bonuses expected expiration ======
268 )))|(% style="width:1010px" %)(((
269 The trigger allows to launch a campaign if the customer's bonus points are about to expire.
270
271 (% class="box infomessage" %)
272 (((
273 This trigger is available if integration with the Loyalty Program is enabled. Integration can be set up by sending a request to our technical support service.
274 )))
275
276 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Bonus_expiration_en.png]]
277
278 The following conditions can be used in the **Days to the nearest deactivation **and** Number of deactivation bonuses**:
279
280 * more;
281 * less;
282 * more than or equal to;
283 * less than or equal to;
284 * equal to;
285 * number of days;
286 * number of bonus points.
287
288 For example: the trigger will be activated for those customers who have more than 500 bonus points expiring after 7 days or less.
289 )))
290 |(% style="width:428px" %)(((
291 ====== Order is paid ======
292 )))|(% style="width:1010px" %)(((
293 This trigger is activated when the order payment status changes from **Pending **to** Paid**. This trigger is designed for online stores, where the order can be placed online and paid later, for example, upon receipt.
294 )))
295 |(% style="width:428px" %)(((
296 ====== Order is canceled ======
297 )))|(% style="width:1010px" %)(((
298 the trigger is activated if the order status is changed to **Canceled**.
299
300 (% class="box infomessage" %)
301 (((
302 This trigger is used for online stores only.
303 )))
304 )))
305 |(% style="width:428px" %)(((
306 ====== Repeat date ======
307 )))|(% style="width:1010px" %)(((
308 This trigger allows to launch **repeated campaigns** on the scheduled dates.
309
310 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Repeat_date.png]]
311
312 The** Recurrent rules **allow to set the frequency of the campaign start. Select the required option in the **How often **field:
313
314 * daily;
315 * weekly;
316 * monthly;
317 * yearly.
318
319 The **Wait, hours ...minutes** field allows to set the time for trigger launching. If you will not do this, the trigger will be activated on the scheduled date at 00:00 (according to the time zone specified in the **Settings > General Settings > **[[Contact Details>>doc:Main.Using.Smart_Communications.Settings_SC.Settings.WebHome||anchor="01"]]** > Time Zone**).
320
321 (% class="box infomessage" %)
322 (((
323 If the next action in the campaign is to send SMS/push notification, the messages will be delivered later (at the time specified in **Settings > General Settings > **[[SMS>>doc:Main.Using.Smart_Communications.Settings_SC.Settings.WebHome||anchor="03"]]** > Time interval for SMS delivery**).
324 )))
325
326 {{showhide showmessage="Daily campaign settings" hidemessage="Hide daily campaign settings"}}
327 The System allows to set up not only the daily campaign triggering, but also triggering after a specified number of days.
328 For example, every fourth day:
329 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Daily_campaign.png" width="400"/}}
330 {{/showhide}}
331
332 {{showhide showmessage="Weekly campaign settings" hidemessage="Hide weekly campaign settings"}}
333 In addition to the standard weekly campaign triggering, it is possible to set up a campaign launch:
334 * Every few weeks;
335 * On certain days.
336
337 For example, launch the campaign every second week on Thursdays and Sundays:
338 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Weekly_campaign.png" width="400"/}}
339 {{/showhide}}
340
341 {{showhide showmessage="Monthly campaign settings" hidemessage="Hide monthly campaign settings"}}
342 In addition to the standard monthly campaign triggering, it is possible to set up a campaign launch:
343 * Every few months;
344 * On a specific date. For example, every third month on 11th and 25th:
345
346 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Monthly_1.png" width="400"/}}
347
348 * On certain days. For example, every last working day of the month:
349
350 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Monthly_2.png" width="400"/}}
351
352 {{/showhide}}
353
354 {{showhide showmessage="Yearly campaign settings" hidemessage="Hide yearly campaign settings"}}
355 Yearly campaign launch settings are similar to the monthly launch settings. There is an additional option to specify the month in which the campaign will be launched.
356 For example, the campaign can be triggered every year on February 10 and August 10:
357
358 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Yearly_campaign.png" width="400"/}}
359 {{/showhide}}
360 )))
361 |(% style="width:428px" %)(((
362 ====== Segment is changed (getting into RFM segment) ======
363 )))|(% style="width:1010px" %)(((
364 The trigger allows to select a segment and R (recency), F (frequency) and M (monetary) parameters. The trigger will be activated if the customer will get within these parameters.
365
366 You should [[create a segment>>doc:Main.Using.Smart_Communications.Customers.User_segments.Segment_builder.WebHome]] or select previously saved one and specify values that must be tracked. For example, R=5, F=5, M=4:
367
368 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:RFM_segment_en.png]]
369
370 By using "*" symbol instead of a digit in a parameter, this parameter will not be taken into account and can have any value.
371
372 For example, you want to track customers who are in category 3 of R-segment, whereas frequency (F) and cost (M) of purchases should not be taken into account:
373
374 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Segment_example_en.png]]
375 )))
376 |(% style="width:428px" %)(((
377 ====== User segment change ======
378 )))|(% style="width:1010px" %)(((
379 This trigger allows to select a segment. The trigger will be activated when customers will get into this segment.
380
381 There is a need either to [[create a segment>>doc:Main.Using.Smart_Communications.Customers.User_segments.Segment_builder.WebHome]] or select a previously saved one from the drop-down list.
382 )))
383 |(% style="width:428px" %)(((
384 ====== Event occurred ======
385 )))|(% style="width:1010px" %)(((
386 This trigger allows to track events on the website.
387
388 To select an event, start typing its name in the **Event Name** field. The list will display all events that have the typed text in their name.
389
390 Examples of events:
391
392 * Contacting the Call Center;
393 * (((
394 Notify when the product is available for purchase.
395 )))
396
397 More information about events can be found in a separate [[article>>doc:Main.Using.Smart_Communications.Events.WebHome]].
398
399 (% class="box infomessage" %)
400 (((
401 The list of events to be tracked is configured during the System integration.
402 )))
403 )))
404 |(% style="width:428px" %)(((
405 ====== Poll completed ======
406 )))|(% style="width:1010px" %)The trigger is activated when customers complete surveys/polls.
407 |(% style="width:428px" %)(((
408 ====== Days since last visit to the site ======
409 )))|(% style="width:1010px" %)The trigger is activated when the specified number of days have passed since the last time the customer's last visit to the website.
410 |(% style="width:428px" %)(((
411 ====== New order is placed ======
412 )))|(% style="width:1010px" %)(((
413 This is a default trigger set up in the System. It is triggered when customers make a purchase in an online/offline store and when a receipt appears in the System.
414
415 If required, there is an option to specify the **order search depth** in days by filling in the corresponding field.
416 )))
417 |(% style="width:428px" %)(((
418 ====== System event ======
419 )))|(% style="width:1010px" %)(((
420 The trigger allows to track system events. To select an event, start typing its name in the **Event name **field. All events that have the typed text in their name will be displayed in the list.
421
422 Event example: product Х is now in stock.
423
424 More information about events can be found in a separate [[article>>doc:Main.Using.Smart_Communications.Events.WebHome]].
425
426 (% class="box infomessage" %)
427 (((
428 The list of events to be tracked is configured during the System integration.
429 )))
430 )))
431 |(% style="width:428px" %)(((
432 ====== Action worked ======
433 )))|(% style="width:1010px" %)(((
434 The trigger is activated if a specified offer/action has worked. Fill in ID of the offer for which the trigger is set up in the **Action code** field.  It is also possible to set the **order/receipt search depth **in days.
435
436 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Action_trigger_en.png]]
437 )))
Created 2025/05/14 08:01
Last edited 2025/05/14 08:01

News
Updates
Tag cloud
Glossary
Site