Loymax, 2026

Wiki source code of 3.2. Triggers

version	line-number	content
35.1	1	A trigger is an event that activates a [[campaign>>doc:Main.Usage.Smart_Communications.Campaigns.WebHome]]. Each trigger type has its own set of parameters. The trigger outputs an array of [[customer profiles>>doc:Main.Smart_Communications.SMC_Use.Customers.All_clients.WebHome\|\|anchor="Profile"]] that meet the condition defined in the trigger.
1.1	2
	3	(% class="box" %)
	4	(((
23.1	5	Trigger example: Days since registration. This trigger includes all customers who registered N days ago. Thus, the audience updates daily when the trigger fires.
1.1	6	)))
	7
23.1	8	=== Editing a trigger ===
1.1	9
23.1	10	When creating a new campaign, a trigger is already present in the editing field. The default trigger depends on the enabled functionality:
1.1	11
35.1	12	* If both [[receipt>>doc:Main.Smart_Communications.SMC_Use.Customers.All_clients.WebHome\|\|anchor="H42743543A438"]] and [[order>>doc:Main.Smart_Communications.SMC_Use.Customers.All_clients.WebHome\|\|anchor="H41743043A43043744B"]] functionality is enabled, the default trigger is Cheque issued;
	13	* If only [[order>>doc:Main.Smart_Communications.SMC_Use.Customers.All_clients.WebHome\|\|anchor="H41743043A43043744B"]] functionality is enabled, the default trigger is Order created;
	14	* If both [[receipt>>doc:Main.Smart_Communications.SMC_Use.Customers.All_clients.WebHome\|\|anchor="H42743543A438"]] and [[order>>doc:Main.Smart_Communications.SMC_Use.Customers.All_clients.WebHome\|\|anchor="H41743043A43043744B"]] options are disabled, the default trigger is Date has come.
19.1	15
23.1	16	To change the campaign’s trigger, double-click it or right-click and select the Edit icon. In the dropdown list, select the desired trigger and click OK.
19.1	17
32.1	18	\|(% style="border-color:white; text-align:right; width:30%" %)[[image:image1.png]]\|(% style="border-color:white; text-align:left; width:70%" %){{lightbox image="image2.png" width="400"/}}
1.1	19
23.1	20	The following triggers are available in Loymax Smart Communications:
1.1	21
	22	{{toc start="6"/}}
	23
	24	(% class="table-bordered" style="width:1447px" %)
	25	(% class="info" %)\|(% style="width:428px" %)Trigger\|(% style="width:1010px" %)Description
	26	\|(% style="width:428px" %)(((
46.1	27	====== {{id name="abandonedcart"/}}Lost cart on the site ======
1.1	28	)))\|(% style="width:1010px" %)(((
23.1	29	Detects cases when the customer adds items to the cart but does not place an order.
	30	A cart is considered lost if:
1.1	31
23.1	32	* the customer added items to the cart, but did not place an order;
	33	* N seconds/minutes/hours have passed since the last cart interaction after viewing (this setting is determined during integration).
1.1	34
	35	(% class="box infomessage" %)
	36	(((
45.1	37	For this trigger to work correctly, the [[JS tracker>>doc:Main.Smart_Communications.SMC_integration.JS_tracker.WebHome]] must be configured on the Company’s website.
1.1	38	)))
19.1	39
23.1	40	This trigger considers the web event Order completed (##order_complete##), which is unrelated to the presence of a receipt. If receipt-based logic is required, add an additional filter by receipt count.
1.1	41	)))
	42	\|(% style="width:428px" %)(((
46.1	43	====== {{id name="abandonedview"/}}Lost view on the site ======
1.1	44	)))\|(% style="width:1010px" %)(((
23.1	45	A general trigger for lost category or product views that detects cases where a customer viewed a product or a category on the website but did not add items to the cart.
1.1	46
23.1	47	If a customer viewed a product or category, but no Order completed (##order_complete##) web event occurred before the trigger chain processing starts (every 5 minutes), the customer is included in the campaign.
19.1	48
1.1	49	(% class="box infomessage" %)
	50	(((
45.1	51	For this trigger to work correctly, the [[JS tracker>>doc:Main.Smart_Communications.SMC_integration.JS_tracker.WebHome]] must be configured on the Partner’s website.
1.1	52	)))
19.1	53
37.1	54	The trigger fires only for customers with a Product view (##view_product##) or Category view (##view_category##) event in the same session, where no Order completed (##order_complete##) event occurred. Therefore, it is recommended to place a [[Wait>>doc:Main.Smart_Communications.SMC_Use.Campaigns.Actions.WebHome\|\|anchor="HWaitA0"]] action after the trigger, followed by a [[Filter customers>>doc:Main.Smart_Communications.SMC_Use.Campaigns.Actions.WebHome\|\|anchor="HFiltercustomersA0"]] action with the following settings:
19.1	55
23.1	56	* Online order placed — equals — No;
	57	* Event source: Any — Within the last — 1 day;
	58	* Has lost cart — equals — No;
	59	* Number of receipts — equals — 0 — within the last — 1 day.
19.1	60
23.1	61	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Filter_customers.png" width="700"/}}
1.1	62	)))
	63	\|(% style="width:428px" %)(((
46.1	64	====== {{id name="abandonedcatview"/}}Lost view of category ======
1.1	65	)))\|(% style="width:1010px" %)(((
23.1	66	Detects cases where a customer views a category on the website but does not add items to the cart.
1.1	67
23.1	68	If a customer views a category, but no Order completed (##order_complete##) event occurs before the trigger chain processing starts (every 5 minutes), the customer is included in the campaign.
19.1	69
1.1	70	(% class="box infomessage" %)
	71	(((
45.1	72	For this trigger to work correctly, the [[JS tracker>>doc:Main.Smart_Communications.SMC_integration.JS_tracker.WebHome]] must be configured on the Partner’s website.
1.1	73	)))
19.1	74
23.1	75	The trigger fires for customers who, within the last 2 days, had one of the following events: Login (##user_login##), Page visit (##user_visit##), or Subscription (##subscribe##)—indicating the start of a web session—and also had a Category view (##view_category##) event within the last 24 hours, but no Order completed (##order_complete##) event. This means the category was viewed, but the goal (order placement on the website or in the Mobile Application) was not achieved.
19.1	76
37.1	77	Therefore, we recommend adding a [[Wait>>doc:Main.Smart_Communications.SMC_Use.Campaigns.Actions.WebHome\|\|anchor="HWaitA0"]] action after the trigger, followed by a [[Filter customers>>doc:Main.Smart_Communications.SMC_Use.Campaigns.Actions.WebHome\|\|anchor="HFiltercustomersA0"]] action with the following settings:
19.1	78
23.1	79	* Online order placed — equals — No;
	80	* Event source: Any — Within the last — 1 day;
	81	* Has lost cart — equals — No;
	82	* Number of receipts — equals — 0 — within the last — 1 day.
19.1	83
23.1	84	\|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Trigger_example_1.png]]
19.1	85
	86	(% class="box infomessage" %)
	87	(((
23.1	88	Note:
19.1	89
23.1	90	* If a customer’s web session lasts longer than two days, they will not be captured by this trigger.
	91	* If a customer places an order and later views other categories without further orders, they will not be captured by this trigger.
1.1	92	)))
19.1	93	)))
1.1	94	\|(% style="width:428px" %)(((
	95	====== Lost view of product on the site ======
	96	)))\|(% style="width:1010px" %)(((
23.1	97	Detects cases where a customer views a product on the website but does not add it to the cart.
1.1	98
23.1	99	If a customer views a product, but no Order completed (##order_complete##) event occurs before the trigger chain processing starts (every 5 minutes), the customer is included in the campaign.
1.1	100
23.1	101	The trigger fires for customers who had one of the following events: Login (##user_login##), Page visit (##user_visit##), or Subscription (##subscribe##)—marking the start of a web session—and also had a Product view (##view_product##) event within the last 24 hours, but no Order completed (##order_complete##) event. Web session duration is not considered for this trigger.
19.1	102
37.1	103	After the trigger, we recommend adding a [[Wait>>doc:Main.Smart_Communications.SMC_Use.Campaigns.Actions.WebHome\|\|anchor="HWaitA0"]] action after the trigger, followed by a [[Filter customers>>doc:Main.Smart_Communications.SMC_Use.Campaigns.Actions.WebHome\|\|anchor="HFiltercustomersA0"]] action with the following settings:
19.1	104
23.1	105	* Online order placed — equals — No;
	106	* Event source: Any — Within the last — 1 day;
	107	* Has lost cart — equals — No;
	108	* Number of receipts — equals — 0 — within the last — 1 day.
19.1	109
32.1	110	\|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Trigger_example_1.png]]
19.1	111
23.1	112	You can configure the trigger to fire only for products in a specific price range. If the Consider price checkbox is selected, the trigger will activate only for products priced above the specified amount.
19.1	113
23.1	114	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Lost_view_en.png" width="400"/}}
1.1	115
32.1	116	The screenshot shows a configuration example where the trigger fires only when a customer views products priced above 10 RUR.
1.1	117
	118	(% class="box infomessage" %)
	119	(((
45.1	120	For this feature to work correctly, the [[JS tracker>>doc:Main.Smart_Communications.SMC_integration.JS_tracker.WebHome]] must transmit the product price in the ##price## field of the ##view_product## event.
1.1	121	)))
	122	)))
	123	\|(% style="width:428px" %)(((
23.1	124	====== Anniversary ======
1.1	125
23.1	126
1.1	127	)))\|(% style="width:1010px" %)(((
	128	(((
23.1	129	Detects X days before/after the anniversary of:
1.1	130
23.1	131	* First order/receipt;
	132	* Last order/receipt;
	133	* Birthday;
	134	* Registration date.
	135
	136	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Anniversary_en.png" width="400"/}}
1.1	137	)))
	138
	139	(((
23.1	140	The trigger allows you to:
1.1	141
23.1	142	1. Select the event type:
	143	1*. Customer registration in the Loyalty Program (on the website, at the POS terminal, or in the Mobile Application);
	144	1*. Customer’s first receipt;
	145	1*. Customer’s last receipt;
	146	1*. Customer’s birthday.
	147	1. Set the campaign launch interval, measured in years, months, or days.
	148	For example:
	149	1*. Annually;
	150	1*. Every 2 months;
1.1	151	1*. Every 10 days.
23.1	152	1. Set a delay.
	153	For example:
	154	1*. Send congratulations 15 days before the birthday (delay: “–15 days”);
	155	1*. Award bonuses one week after the first purchase (delay: “+7 days”).
1.1	156
23.1	157	Trigger usage examples:
1.1	158
23.1	159	* Annually, 15 days before the birthday, send a greeting and bonus points.
	160	* Congratulate customers on the anniversary of their first purchase.
	161	* Offer participation in a promotion on the anniversary of website registration.
1.1	162	)))
	163	)))
	164	\|(% style="width:428px" %)(((
	165	====== Days since order ======
	166	)))\|(% style="width:1010px" %)(((
47.1	167	The trigger fires when the specified number of days has passed since the customer placed an online [[order>>doc:Main.Smart_Communications.SMC_Use.E-Commerce.Orders.WebHome]].
1.1	168
23.1	169	For example, customers who haven’t placed a new order within 30 days after their last order:
1.1	170
23.1	171	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Days_since_order.png" width="400"/}}
1.1	172	)))
	173	\|(% style="width:428px" %)(((
23.1	174	====== Days since receipt ======
19.1	175	)))\|(% style="width:1010px" %)(((
23.1	176	The trigger fires when the specified number of days has passed since the receipt appeared in the system.
19.1	177
23.1	178	For example, customers who have not made any purchases within 60 days after their last receipt:
19.1	179
23.1	180	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Days_since_receipt.png" width="400"/}}
19.1	181	)))
	182	\|(% style="width:428px" %)(((
1.1	183	====== Days since registration ======
	184	)))\|(% style="width:1010px" %)(((
23.1	185	The trigger fires when the specified number of days has passed since the customer’s registration.
1.1	186
35.1	187	The trigger fires only if the Registration date field is not empty in the [[customer profile>>doc:Main.Smart_Communications.SMC_Use.Customers.All_clients.WebHome\|\|anchor="H41F44043E44443843B44C43A43B43843543D442430"]].
1.1	188	)))
	189	\|(% style="width:428px" %)(((
46.1	190	====== {{id name="container_add"/}}Added a product to the container ======
1.1	191	)))\|(% style="width:1010px" %)(((
23.1	192	Detects when a customer adds an item to the specified container.
1.1	193
45.1	194	Select the desired container from the dropdown list in the [[Container>>doc:Main.Smart_Communications.SMC_integration.JS_tracker.WebHome\|\|anchor="HWorkwithcontainers"]] field.
1.1	195
	196	(% class="box infomessage" %)
	197	(((
23.1	198	Note:
45.1	199	Containers are individual customer item lists. For example, the “Cart” container holds items added to the cart but not yet purchased. Items can be added to a container via an external file or transmitted via the [[JS tracker>>doc:Main.Smart_Communications.SMC_integration.JS_tracker.WebHome]].
1.1	200	)))
	201	)))
	202	\|(% style="width:428px" %)(((
23.1	203	====== Item ordered ======
	204	)))\|(% style="width:1010px" %)(((
47.1	205	Detects when a product is [[ordered>>doc:Main.Smart_Communications.SMC_Use.E-Commerce.Orders.WebHome]] on the website.
23.1	206
	207	To define the order status for which the trigger should fire, fill in the Order statuses field.
	208
32.1	209	To select a product, begin typing its name in the Item field. Matching products will appear in the list.
23.1	210
	211	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Product_ordered.png" width="400"/}}
	212	)))
	213	\|(% style="width:428px" %)(((
	214	====== Item from specific category ordered ======
	215	)))\|(% style="width:1010px" %)(((
47.1	216	Detects when a product from a specific category is [[ordered>>doc:Main.Smart_Communications.SMC_Use.E-Commerce.Orders.WebHome]].
23.1	217
	218	To define the order status for which the trigger should fire, fill in the Order statuses field by selecting the desired option from the dropdown.
	219
42.1	220	Select the desired [[classifier>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Classifiers.WebHome]] from the Classifier dropdown.
23.1	221
	222	To select a category, begin typing its name in the Category field. Matching categories will appear in the list.
	223
32.1	224	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="order_category.png" width="400"/}}
23.1	225	)))
	226	\|(% style="width:428px" %)(((
1.1	227	====== Product in cart is low on stock ======
23.1	228	)))\|(% style="width:1010px" %)The trigger fires when items placed in the customer’s cart but not purchased are running out of stock.
1.1	229	\|(% style="width:428px" %)(((
48.1	230	====== {{id name="pricechange_view"/}}The price of the viewed product has changed ======
23.1	231	)))\|(% style="width:1010px" %)(((
	232	Detects price changes for products previously viewed by the customer on the website.
	233
	234	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Viewed_product_changed_1.png" width="400"/}}
	235
	236	Specify the price change direction (decreased or increased) and set the minimum change value (absolute value or percentage).
	237	)))
	238	\|(% style="width:428px" %)(((
1.1	239	====== Product price has changed ======
	240	)))\|(% style="width:1010px" %)(((
23.1	241	Detects price changes for a product.
1.1	242
23.1	243	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Product_price_en.png" width="400"/}}
1.1	244
23.1	245	Select the desired container from the Container dropdown.
1.1	246
23.1	247	Specify the price change direction (decreased or increased) and set the minimum change value (absolute value or percentage).
1.1	248	)))
	249	\|(% style="width:428px" %)(((
23.1	250	====== Order status changed ======
19.1	251	)))\|(% style="width:1010px" %)(((
47.1	252	Detects changes in [[order>>doc:Main.Smart_Communications.SMC_Use.E-Commerce.Orders.WebHome]] status.
19.1	253
32.1	254	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="order_status_change.png" width="400"/}}
19.1	255
32.1	256	Specify the order search depth (in days), and select the initial and current order statuses.
19.1	257	)))
	258	\|(% style="width:428px" %)(((
1.1	259	====== Customer registration ======
23.1	260	)))\|(% style="width:1010px" %)Detects when a customer registers in the System.
1.1	261	\|(% style="width:428px" %)(((
23.1	262	====== Customer registration + filter ======
	263	)))\|(% style="width:1010px" %)Detects when a customer registers in the System and allows an additional filter: Customer ID contains.
1.1	264	\|(% style="width:428px" %)(((
23.1	265	====== Viewed the page on the site ======
1.1	266	)))\|(% style="width:1010px" %)(((
23.1	267	Detects when a customer visits a specific section of the website.
1.1	268
23.1	269	To select a section, begin typing its name in the Section field. Matching sections will appear in the list.
1.1	270	)))
	271	\|(% style="width:428px" %)(((
46.1	272	====== {{id name="site_visit"/}}The customer visited the site ======
23.1	273	)))\|(% style="width:1010px" %)Detects when a customer visits the website.
1.1	274	\|(% style="width:428px" %)(((
46.1	275	====== {{id name="product_view"/}}Viewed the product on the site ======
1.1	276	)))\|(% style="width:1010px" %)(((
23.1	277	Detects when a product is viewed on the website.
1.1	278
23.1	279	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Viewed_product_en.png" width="400"/}}
1.1	280
23.1	281	To select a product, set the condition to equals and enter the exact product name from the catalog. Alternatively, select contains and begin typing the product name—matching products will appear in the list. This trigger is useful when running promotions for a specific product or its complementary items.
1.1	282	)))
	283	\|(% style="width:428px" %)(((
46.1	284	====== {{id name="cat_view"/}}Viewed the product category on the site ======
1.1	285	)))\|(% style="width:1010px" %)(((
23.1	286	Detects when a product from a specific category is viewed.
1.1	287
23.1	288	To select a category, begin typing its name in the Category field. Matching categories will appear in the list. This trigger can be used when running promotions for a specific product category.
1.1	289	)))
	290	\|(% style="width:428px" %)(((
	291	====== Item purchased ======
	292	)))\|(% style="width:1010px" %)(((
23.1	293	Detects when a product is purchased.
1.1	294
23.1	295	To select a product, begin typing its name in the Product field. Matching products will appear in the list.
1.1	296	)))
	297	\|(% style="width:428px" %)(((
23.1	298	====== Item from specific category ======
1.1	299	)))\|(% style="width:1010px" %)(((
23.1	300	Detects when a product from a specific category is purchased.
1.1	301
23.1	302	To select a category, begin typing its name in the Category field. Matching categories will appear in the list.
1.1	303	)))
	304	\|(% style="width:428px" %)(((
	305	====== Date has come ======
	306	)))\|(% style="width:1010px" %)(((
23.1	307	Launches the campaign on the selected date.
1.1	308
23.1	309	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Due_date_en.png" width="400"/}}
1.1	310
44.1	311	In the Start at ... hours ... minutes field, you can define the exact time when the trigger should fire. If not specified, the trigger fires at 00:00 on the selected date (based on the time zone configured in Settings > General settings > [[Contact details>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome\|\|anchor="01"]] > Time zone).
1.1	312
	313	(% class="box infomessage" %)
	314	(((
44.1	315	If the first action in the campaign is SMS/push notification delivery, messages may be sent later—during the time window specified in Settings > General settings > [[SMS>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome\|\|anchor="03"]] > SMS delivery time window.
1.1	316	)))
	317
23.1	318	Sometimes it’s necessary to reuse campaigns that start with this trigger. For example, an earlier promotion triggered on the 2nd of last month used a campaign set to launch on the 1st of this month. A few months later, you may need to rerun the same campaign (e.g., with updated start date and message text).
1.1	319
23.1	320	In this case, ensure that the Interval between reentries value is shorter than the time elapsed since the previous campaign launch—otherwise, customers won’t re-enter the campaign, because the System will consider them already processed and exclude them.
1.1	321	)))
	322	\|(% style="width:428px" %)(((
23.1	323	====== Date come for order ======
1.1	324	)))\|(% style="width:1010px" %)(((
47.1	325	Launches the campaign a certain number of days before/after/on the date specified in an [[order>>doc:Main.Smart_Communications.SMC_Use.E-Commerce.Orders.WebHome]] field.
1.1	326
23.1	327	For example: if the order includes a separate field for pickup deadline, you can configure a reminder that the order will soon be returned.
1.1	328
32.1	329	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="order_date" width="400"/}}
1.1	330
23.1	331	To select the date field, begin typing its name in the Date field input. Matching fields will appear in the list.
1.1	332
23.1	333	Available options for trigger:
	334
1.1	335	* On the specified date;
23.1	336	* N days before the date;
	337	* N days after the date.
1.1	338
44.1	339	The trigger fires at 00:00 (according to the time zone configured in Settings > General settings > [[Contact details>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome\|\|anchor="01"]] > Time zone). If the subsequent actions are better executed during business hours, add a delay using the [[Wait>>doc:Main.Smart_Communications.SMC_Use.Campaigns.Actions.WebHome\|\|anchor="HWaitA0"]] action, or specify a launch time in Start at ... hours ... minutes.
23.1	340
	341	If the trigger should fire only for orders with a specific status, select the desired status from the Order statuses dropdown.
1.1	342	)))
	343	\|(% style="width:428px" %)(((
	344	====== Date come for client ======
	345	)))\|(% style="width:1010px" %)(((
23.1	346	Launches the campaign on the date specified in a field of the customer’s profile.
1.1	347
	348	\|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Customer_date.png]]
	349
23.1	350	You can link campaign launches to customer-specific dates, such as:
1.1	351
23.1	352	* Birthday;
1.1	353	* Registration date;
23.1	354	* Date of first receipt;
	355	* Date of last receipt;
	356	* Child’s birthday;
	357	* Upcoming bonus deactivation date;
	358	* RFM segment change date.
1.1	359
44.1	360	The trigger fires at 00:00 on the specified date (based on the time zone configured in Settings > General settings > [[Contact details>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome\|\|anchor="01"]] > Time zone). If subsequent actions are better performed during business hours, add a delay using the [[Wait>>doc:Main.Smart_Communications.SMC_Use.Campaigns.Actions.WebHome\|\|anchor="HWaitA0"]] action, or specify a launch time in Start at ... hours ... minutes.
1.1	361
	362	(% class="box infomessage" %)
	363	(((
44.1	364	If the first action in the campaign is SMS/push notification delivery, messages may be sent later—during the time window specified in Settings > General settings > [[SMS>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome\|\|anchor="03"]] > SMS delivery time window.
1.1	365	)))
	366
23.1	367	Sometimes it’s necessary to reuse campaigns that start with the Customer date reached trigger. For example, last month you ran a campaign tied to customers’ last receipt dates. A few months later, you may wish to run the same campaign again (e.g., with updated message text).
1.1	368
23.1	369	In such cases, ensure that the Interval between reentries value is shorter than the time elapsed since the previous campaign launch—otherwise, customers won’t re-enter the campaign, because the System will consider them already processed and exclude them.
1.1	370	)))
	371	\|(% style="width:428px" %)(((
23.1	372	====== Date come for cheque ======
	373	)))\|(% style="width:1010px" %)(((
43.1	374	Launches the campaign a certain number of days before/after/on the date specified in one of the receipt [[fields>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Data_field.WebHome]].
23.1	375
	376	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Date_for_receipt.png" width="400"/}}
	377
	378	To select the date field, begin typing its name in the Date field input. Matching fields will appear in the list.
	379
	380	Available options for trigger:
	381
	382	* On the specified date;
	383	* N days before the date;
	384	* N days after the date.
	385
44.1	386	The trigger fires at 00:00 (according to the time zone configured in Settings > General settings > [[Contact details>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome\|\|anchor="01"]] > Time zone). If subsequent actions are better executed during business hours, add a delay using the [[Wait>>doc:Main.Smart_Communications.SMC_Use.Campaigns.Actions.WebHome\|\|anchor="HWaitA0"]] action, or specify a launch time in Start at ... hours ... minutes.
23.1	387	)))
	388	\|(% style="width:428px" %)(((
19.1	389	====== Bonus expected expiration ======
1.1	390	)))\|(% style="width:1010px" %)(((
23.1	391	Launches the campaign when bonus points expiration is expected for the customer.
1.1	392
	393	(% class="box infomessage" %)
	394	(((
23.1	395	This trigger is available only when Loyalty Program integration is enabled. Integration setup is performed via a request to Technical Support.
1.1	396	)))
	397
23.1	398	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Bonus_expiration_en.png" width="400"/}}
1.1	399
23.1	400	In the Days to the nearest deactivation and Number of deactivation bonuses fields, you can set the condition as:
1.1	401
23.1	402	* greater than;
	403	* less than;
	404	* greater than or equal to;
1.1	405	* less than or equal to;
	406	* equal to;
	407	* number of days;
	408	* number of bonus points.
	409
23.1	410	For example: the trigger fires for customers whose bonuses (over 500 points) will expire in 7 days or less.
1.1	411	)))
	412	\|(% style="width:428px" %)(((
	413	====== Repeat date ======
	414	)))\|(% style="width:1010px" %)(((
23.1	415	Enables recurring campaigns on specified dates.
1.1	416
23.1	417	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Repeat_date.png" width="400"/}}
1.1	418
23.1	419	Recurrence rules define how often the campaign runs. Select the desired option in the Frequency field:
1.1	420
23.1	421	* Daily;
	422	* Weekly;
	423	* Monthly;
	424	* Yearly.
1.1	425
44.1	426	In the Start at ... hours ... minutes field, you can set the trigger’s firing time. If left unspecified, the trigger fires at 00:00 on the selected date (based on the time zone configured in Settings > General settings > [[Contact details>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome\|\|anchor="01"]] > Time zone).
1.1	427
	428	(% class="box infomessage" %)
	429	(((
44.1	430	If the next action in the campaign is SMS/push notification delivery, messages may be sent later—during the time window specified in Settings > General settings > [[SMS>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome\|\|anchor="03"]] > SMS delivery time window.
1.1	431	)))
	432
23.1	433	{{showhide showmessage="Daily campaign settings" hidemessage="Hide daily campaign example"}}
	434	The System allows not only daily campaign scheduling but also runs every N days.
	435	Example: every fourth day:
1.1	436	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Daily_campaign.png" width="400"/}}
	437	{{/showhide}}
	438
23.1	439	{{showhide showmessage="Weekly campaign settings" hidemessage="Hide weekly campaign example"}}
	440	Beyond standard weekly scheduling, you can configure:
	441	* Recurrence every N weeks;
	442	* Runs on specific weekdays.
1.1	443
23.1	444	Example: every other week, on Thursdays and Sundays:
1.1	445	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Weekly_campaign.png" width="400"/}}
	446	{{/showhide}}
	447
23.1	448	{{showhide showmessage="Monthly campaign settings" hidemessage="Hide monthly campaign example"}}
	449	Beyond standard monthly scheduling, you can configure:
	450	* Recurrence every N months;
	451	* Runs on specific dates. Example: every third month on the 11th and 25th:
1.1	452
	453	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Monthly_1.png" width="400"/}}
	454
23.1	455	* Runs on special days. Example: on the last business day of each month:
1.1	456
	457	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Monthly_2.png" width="400"/}}
	458
	459	{{/showhide}}
	460
23.1	461	{{showhide showmessage="Annual campaign settings" hidemessage="Hide annual campaign example"}}
	462	Annual scheduling options mirror monthly ones—with the added ability to specify the month(s).
	463	Example: annually on February 10 and August 10:
1.1	464
	465	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Yearly_campaign.png" width="400"/}}
	466	{{/showhide}}
	467	)))
	468	\|(% style="width:428px" %)(((
23.1	469	====== Segment is changed ======
1.1	470	)))\|(% style="width:1010px" %)(((
23.1	471	The trigger allows to select a segment and R (recency), F (frequency) and M (monetary) parameters. The trigger fires for customers matching the specified criteria.
1.1	472
36.1	473	First, [[create a segment>>doc:Main.Smart_Communications.SMC_Use.Customers.User_segments.Segment_builder.WebHome]] or select a saved one, then specify the exact parameters to track—for example, R=5, F=5, M=4.
1.1	474
23.1	475	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="RFM_segment_en.png" width="400"/}}
1.1	476
23.1	477	If you enter * instead of a number for a parameter, that parameter is ignored and can take any value.
1.1	478
23.1	479	Example: track customers in R-segment category 3, regardless of F and M values:
1.1	480
23.1	481	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Segment_example_en.png" width="400"/}}
1.1	482	)))
	483	\|(% style="width:428px" %)(((
	484	====== User segment change ======
	485	)))\|(% style="width:1010px" %)(((
23.1	486	Allows selecting a segment containing customers for whom the trigger should fire.
1.1	487
36.1	488	First, [[create a segment>>doc:Main.Smart_Communications.SMC_Use.Customers.User_segments.Segment_builder.WebHome]] or select one from the dropdown list.
1.1	489	)))
	490	\|(% style="width:428px" %)(((
19.1	491	====== Cheque issued ======
	492	)))\|(% style="width:1010px" %)(((
23.1	493	This is the default trigger in the System when receipt functionality is enabled. It fires upon a purchase—online or offline—when a receipt appears in the System.
19.1	494
23.1	495	\|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Receipt_issued.png\|\|height="255" width="486"]]
19.1	496
23.1	497	Optionally, you can set the cheque search depth (in days) by filling in the corresponding field.
19.1	498	)))
	499	\|(% style="width:428px" %)(((
1.1	500	====== Event occurred ======
	501	)))\|(% style="width:1010px" %)(((
23.1	502	Detects custom events.
1.1	503
23.1	504	To select an event, begin typing its name in the Event name field. Matching events will appear in the list.
1.1	505
23.1	506	Event examples:
1.1	507
23.1	508	* Call Center inquiry;
	509	* Notification of product restock.
1.1	510
23.1	511	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Event_occurred.png" width="600"/}}
19.1	512
40.1	513	For more details, refer to the dedicated [[article>>doc:Main.Smart_Communications.SMC_Use.Events_SmC.WebHome]].
1.1	514
	515	(% class="box infomessage" %)
	516	(((
23.1	517	The list of tracked events is configured during System implementation.
1.1	518	)))
	519	)))
	520	\|(% style="width:428px" %)(((
19.1	521	====== Web event occurred ======
	522	)))\|(% style="width:1010px" %)(((
23.1	523	Detects events on the website or in the Mobile Application.
19.1	524
23.1	525	To select an event, begin typing its name in the Event name field. Matching events will appear in the list.
19.1	526
23.1	527	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Web_event.png" width="400"/}}
19.1	528
23.1	529	Web event examples:
19.1	530
23.1	531	* Customer left a website review;
	532	* Customer logged in;
	533	* Customer added item to favorites;
	534	* Page view;
	535	* Personal info update;
	536	* Site search.
19.1	537	)))
	538	\|(% style="width:428px" %)(((
1.1	539	====== Poll completed ======
49.1	540	)))\|(% style="width:1010px" %)The trigger fires when a customer complets a [[poll>>doc:Main.Smart_Communications.SMC_Use.Surveys.Polls.WebHome]].
1.1	541	\|(% style="width:428px" %)(((
46.1	542	====== {{id name="time_since_visit"/}}Days since last visit to the site ======
23.1	543	)))\|(% style="width:1010px" %)The trigger fires when the specified number of days has passed since the customer’s last website visit.
1.1	544	\|(% style="width:428px" %)(((
46.1	545	====== {{id name="order_complete"/}}Order created ======
1.1	546	)))\|(% style="width:1010px" %)(((
47.1	547	This is the default trigger when [[order>>doc:Main.Smart_Communications.SMC_Use.E-Commerce.Orders.WebHome]] functionality is enabled. It fires upon order placement in the online store.
1.1	548
32.1	549	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="order_created.png" width="400"/}}
1.1	550	)))
	551	\|(% style="width:428px" %)(((
	552	====== System event ======
	553	)))\|(% style="width:1010px" %)(((
23.1	554	Detects system events. To select an event, begin typing its name in the Event name field. Matching events will appear in the list.
1.1	555
23.1	556	Event example: product X is back in stock.
1.1	557
40.1	558	For more details, refer to the dedicated [[article>>doc:Main.Smart_Communications.SMC_Use.Events_SmC.WebHome]].
1.1	559
	560	(% class="box infomessage" %)
	561	(((
23.1	562	The list of tracked events is configured during System implementation.
1.1	563	)))
	564	)))
	565	\|(% style="width:428px" %)(((
	566	====== Action worked ======
	567	)))\|(% style="width:1010px" %)(((
23.1	568	The trigger fires when the specified offer is applied. Enter the offer identifier in the Action code field. You can also define the cheque search depth (in days).
1.1	569
23.1	570	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Action_trigger_en.png" width="400"/}}
33.1	571	)))

Created 2025/05/14 08:01
Last edited 2026/05/06 05:06

News
Updates
Tag cloud
Glossary
Site

Navigation

Wiki source code of 3.2. Triggers