Retail Engine, 2026

Wiki source code of 3.3. Actions

Show last authors
1 **Action** is an activity that Smart Communications must perform on a [[customer profile>>doc:Main.Smart_Communications.SMC_Use.Customers.All_clients.WebHome||anchor="Profile"]] that has entered a [[campaign>>doc:Main.Smart_Communications.SMC_Use.Campaigns.WebHome]] (e.g., send an email, wait, apply a filter, add to a target audience, etc.).
2
3 As input, the **action** receives an array of customer profiles. As output, it returns an array of customer profiles for whom the **action** was performed.
4
5 (% class="box" %)
6 (((
7 {{toc depth="3" start="3"/}}
8 )))
9
10 === Creating an action ===
11
12 To create a new **action** in the chain:
13
14 * drag the **action** from the left menu onto the editing canvas;
15 * or click the desired **action**, then click the canvas:
16
17 |(% style="border-color:#ffffff; text-align:center" %)[[image:3_Actions_the_main.png]]
18
19 |(% style="border-color:white; width:1040px" %)(((
20 Connect the action to the previous campaign element by left-clicking. The connecting line should run from the green dot to the blue dot, as shown in the screenshot.
21
22 To delete a connection, right-click the line.
23 )))|(% style="border-color:white; text-align:center; width:398px" %)[[image:Connection_line.png||height="130" width="285"]]
24 |(% style="border-color:white; width:1040px" %)(((
25 === Editing, copying, and deleting actions ===
26
27 Campaign actions can be **edited**, **copied**, or **deleted**. To do this, right-click the action and select the desired option from the context menu.
28
29 You can also copy actions using Ctrl+C/Ctrl+V. Select the desired action with the **right** mouse button and press Ctrl+C. The copied action can be pasted into the same campaign editor or into another editor opened in a new tab within the same browser.
30
31 To edit an action, double-click it with the left mouse button.
32 )))|(% style="border-color:white; text-align:center; width:398px" %)(((
33
34 [[image:actions_menu.png||height="112" width="297"]]
35 )))
36 |(% style="border-color:white; width:1040px" %)(((
37 ===== Merging multiple campaign branches =====
38
39 If a campaign includes multiple scenarios in a trigger chain that end with the same action, you can merge several branches into one action.
40 )))|(% style="border-color:white; text-align:center; width:398px" %)[[image:Multiple_branch_chain.png||height="273" width="295"]]
41 |(% style="border-color:white; width:1040px" %)(((
42 ===== Positive and negative scenarios =====
43
44 For the **Filter customers** and **Refresh filter** actions, you can split the incoming flow into two scenarios:
45
46 (((
47 * **Positive** — marked with a green plus. This branch includes all customers who meet the filter conditions;
48 * **Negative** — marked with a red minus. This branch includes all customers who do not meet the filter conditions.
49 )))
50 )))|(% style="border-color:white; text-align:center; width:398px" %)[[image:Scenarios.png||height="238" width="287"]]
51
52 === Full list of actions and their descriptions ===
53
54 {{toc start="6"/}}
55
56 (% class="table-bordered" style="width:1443px" %)
57 (% class="info" %)|(% style="width:417px" %)**Action**|(% style="width:1021px" %)**Description**
58 |(% style="width:417px" %)(((
59 ====== A/B test [[image:A_B_icon.png]] ======
60 )))|(% style="width:1021px" %)(((
61 Allows you to conduct [[A/B testing>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.A_B_testing.WebHome]], i.e., create different continuation variants of a campaign chain. This helps identify the best-performing campaign variant to use going forward.
62
63 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="A_B_test_en.png" width="700"/}}
64
65 In the field **Randomly distribute the specified number of customers**, enter the number of customers on whom the test will be conducted. These customers will be evenly distributed across all branches. The most effective variant will then be selected. For example, if 500 is entered, the first 500 customers will be evenly distributed among all branches, and all subsequent customers will be directed to the winning branch.
66
67 In the field **Criteria for selecting the winning variant**, specify the metric used to determine the best variant. The winner will be the variant with the highest number of opens/clicks/orders.
68
69 |(% style="border-color:#ffffff; text-align:center" %)[[image:Criteria_en.png]]
70
71 The field **Results evaluation period, days** allows you to delay evaluation of customer actions. For example, if 7 days is specified, opens/clicks/orders during the first 7 days will not be counted toward determining the winner.
72
73 The checkbox **Enable test restart** allows you to reset results from previous tests. If enabled, you must fill in one of the following fields:
74
75 * Restart period, days;
76 * Restart period, hours.
77
78 To create branching variants, add child actions. You can define two or more different variants.
79
80 **A/B test example:**
81
82 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:A_B_example.png||height="267" width="345"]]
83 )))
84 |(% style="width:417px" %)(((
85 ====== Refresh filter [[image:attach:Filter.webp]] ======
86 )))|(% style="width:1021px" %)(((
87 Used when a filter (**Filter customers**) was already applied earlier in the action chain and now needs to be updated—avoiding duplication of the filter definition.
88
89 **Usage example**:
90
91 * Filter customers—for instance, include everyone who made 1 order.
92 * Send them an email.
93 * Wait 30 days.
94 * Refresh the filter (new buyers may have appeared during this time).
95 * Send them another email.
96
97 |(% style="border-color:#ffffff; text-align:center" %)[[image:Filter_update_en.png]]
98
99 Other actions may occur between **Filter customers** and **Refresh filter**.
100
101 (% class="box infomessage" %)
102 (((
103 * If multiple filters appear before **Refresh filter**, the nearest one will be refreshed.
104 * For the **Refresh filter** action, you can define separate paths for customers who match the filter and those who do not.
105 )))
106
107 Like **Filter customers**, **Refresh filter** splits the incoming flow into two scenarios:
108
109 * **Positive** — marked with a green plus. Includes all customers meeting the filter conditions;
110 * **Negative** — marked with a red minus. Includes all customers not meeting the filter conditions.
111
112 For example, the filter selects all customers who will receive an SMS. All others (via the red-minus branch) receive an email.
113
114 Branches can later be merged again into a single common action if needed.
115
116 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Filter_update_example_en.png" width="700"/}}
117 )))
118 |(% style="width:417px" %)(((
119 ====== Select customers from segment [[image:attach:Customer_selection.png]] ======
120 )))|(% style="width:1021px" %)(((
121 Allows you to select customers belonging to a specific predefined segment.
122
123 (% class="box infomessage" %)
124 (((
125 You can review the list of predefined segments and their settings in **Customers > **[[User segments>>doc:Main.Smart_Communications.SMC_Use.Customers.User_segments.WebHome]].
126 )))
127 )))
128 |(% style="width:417px" %)(((
129 ====== {{id name="tags"/}}Audience actions [[image:attach:Add_to_audience.png]] ======
130 )))|(% style="width:1021px" %)(((
131 Allows you to **add to audience** or **exclude from audience** customers during campaigns.
132
133 |(% style="border-color:white; text-align:center; width:505px" %)[[image:Add_to_audience_example.png]]|(% style="border-color:white; text-align:center; width:499px" %)[[image:Create_new_audience.png]]
134
135 Select the desired **audience name** from the dropdown list. To create a new target audience, enter a **Name** in the **Audience actions** settings window and click **Create audience** (see image on the right). A new target audience will be created and selected.
136
137 If needed, check the box **Send audience list to Loyalty Program**. If Loyalty Program integration is configured and supports audience list transfer, the list will be automatically sent to the Loyalty Program upon inclusion.
138
139 **Example**:
140
141 1. Create an audience named "Wants to buy iPhone 13".
142 2. This list is automatically sent to the Loyalty Program.
143 3. In the Loyalty Program, you can set up a rule for these customers—for example, offer a gift if they purchase an iPhone 13.
144
145 The **Exclude from audience** option removes a segment from the audience. Select the audience to exclude from the dropdown list. Exclusion can also be sent to the Loyalty Program.
146
147 To skip actions for control group customers, check **Ignore control group customers**.
148
149 (% class="box infomessage" %)
150 (((
151 For detailed information on working with target audiences, see the [[dedicated article>>doc:Main.Smart_Communications.SMC_Use.Customers.Target_audiences.WebHome]].
152 )))
153 )))
154 |(% style="width:417px" %)(((
155 ====== Control group [[image:attach:CG_icon.png||height="38" width="40"]] ======
156 )))|(% style="width:1021px" %)(((
157 Allows you to designate a [[control group>>doc:Main.Smart_Communications.SMC_Use.Control_groups.WebHome]] of customers during campaigns. The **control group** consists of potential campaign participants who are not exposed to communications or campaign mechanics. However, campaign metrics are calculated for them just as for the main group receiving communications.
158
159 (% class="table-bordered" %)
160 |(% style="border-color:white; text-align:center" %)**Image 1**|(% style="border-color:white; text-align:center" %)**Image 2**
161 |(% style="border-color:white; text-align:right" %){{lightbox image="action_cg_size.png" width="280"/}}|(% style="border-color:white; text-align:left" %){{lightbox image="action_cg_audience.png" width="280"/}}
162
163 Enter an **action description** and select a **control group selection method**:
164
165 * **By size** (see Image 1). This option displays the following fields:
166 * **Control group size**: specify the percentage of the campaign participants that will not receive communications.
167 * **Stratification parameters**: optionally, use stratification—proportionally dividing the campaign participants into subgroups (strata) by a specific attribute (e.g., age, gender, registration date). Then, within each subgroup, assign customers to main and control groups. Add one or more stratification parameters by clicking **Add parameter**. A modal window with control group configuration settings will open. Read more about stratification [[here>>doc:Main.Smart_Communications.SMC_Use.Control_groups.WebHome||anchor="Stratification"]].
168
169 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="action_cg_strat.png" width="500"/}}
170
171 * **Use audience** (see Image 2). This option displays the **Audience as control group** field. Select a [[target audience>>doc:Main.Smart_Communications.SMC_Use.Customers.Target_audiences.WebHome]] from the dropdown list to serve as the control group.
172 )))
173 |(% style="width:417px" %)(((
174 ====== Award points [[image:attach:Points.png]] ======
175 )))|(% style="width:1021px" %)(((
176 Allows awarding internal points to customers for actions in the system.
177
178 **Examples**:
179
180 * Visited website — 3 points;
181 * Made a purchase from an email — 5 points;
182 * Bought at a store — 20 points.
183
184 Points can also be deducted. For example, if a customer hasn’t made any purchases in three months—deduct 50 points.
185
186 (% class="box" %)
187 (((
188 You can use point scoring to identify the most active customers and build segments.
189
190 **Examples**:
191
192 * Visited the site 3 times in a month — award points;
193 * Made more than 2 purchases last quarter — award points;
194 * Opened an email — award points.
195 )))
196
197 In the **Number of points** field, enter a positive number (to award) or a negative number (to deduct). For example, you can award -10 points:
198
199 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Assess_scores_en.png" width="400"/}}
200
201 (% class="box warningmessage" %)
202 (((
203 **Note**: The **Award points** action is used only for internal customer evaluation. These point awards and deductions are not visible to customers.
204 )))
205 )))
206 |(% style="width:417px" %)(((
207 ====== Accrue bonus points [[image:attach:Bonus_points.png]] ======
208 )))|(% style="width:1021px" %)(((
209 Allows accruing [[bonus points in the Loyalty Program>>doc:Main.Smart_Communications.SMC_Use.SmartCom_Bonuses_Accrual.WebHome]].
210
211 (% class="box infomessage" %)
212 (((
213 This action is available only if integration with[[ Loyalty>>doc:Main.General_information.Loymax_Loyalty.WebHome]] Platform is configured. Integration setup requires a request to Technical Support.
214 )))
215
216 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Issue_bonus_en.png" width="400"/}}
217
218 (% class="box infomessage" %)
219 (((
220 The available parameters for **Accrue bonus points** depend on the capabilities of the Loyalty Program (LP) platform in use.
221 )))
222
223 Specify the **number** of bonus points to accrue, **expiration period** (if the LP supports bonus expiration), and **legal entity**. Optionally, add an **accrual description**.
224
225 (% class="box" %)
226 (((
227 To notify customers about bonus accrual, create a campaign chain: **Accrue bonus points > Wait > Send message**. This ensures bonuses are credited before the notification is sent, avoiding cases where the customer receives a message before their bonus account is updated.
228 )))
229 )))
230 |(% style="width:417px" %)(((
231 ====== Limit number of participants [[image:attach:Limit_participants.png]] ======
232 )))|(% style="width:1021px" %)(((
233 Limits the number of customers for whom actions in the chain will be performed. The limit applies to the entire campaign. Once the specified number is reached, the campaign stops.
234
235 |(% style="border-color:#ffffff; text-align:center" %)[[image:Customer_limit_example.png]]
236
237 In the **Period** dropdown, select the timeframe for the limit:
238
239 * All time,
240 * One campaign launch,
241 * Day,
242 * Week,
243 * Month,
244 * Year.
245 )))
246 |(% style="width:417px" %)(((
247 ====== Limit poll [[image:attach:Poll_limitation.png]] ======
248 )))|(% style="width:1021px" %)(((
249 Sets the maximum number of customers who can complete a poll previously created in the [[Polls>>doc:Main.Smart_Communications.SMC_Use.Surveys.Polls.WebHome]] section.
250
251 (% class="box infomessage" %)
252 (((
253 This action is available only if the poll functionality is enabled. Learn more in the [[Polls>>doc:Main.Smart_Communications.SMC_Use.Surveys.Polls.WebHome]] section.
254 )))
255
256 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Limit_poll.png" width="400"/}}
257
258 In the **Survey** field, select a survey from the dropdown list. Then choose one of the following limit types:
259
260 * **Total limit**: the specified number defines the total number of survey participants.
261 * **Per point of sale**: the specified number applies separately to each registered point of sale.
262
263 To specify how many customers to **survey at once**, check the corresponding box and enter the number.
264 )))
265 |(% style="width:417px" %)(((
266 ====== Send SMS [[image:attach:SMS.png]] ======
267 )))|(% style="width:1021px" %)(((
268 Sends an SMS message to the customer.
269
270 (% class="box infomessage" %)
271 (((
272 If the SMS provider supports Viber, you can send Viber messages or a Viber > SMS cascade.
273 Read more about cascades and Viber usage [[here>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.SMS_mass_messaging.WebHome||anchor="01"]].
274 )))
275
276 *//Viber access is restricted in the Russian Federation. Usage in other countries is subject to local laws.//
277
278 **SMS message window without Viber**:
279
280 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Send_SMS_en.png" width="400"/}}
281
282 **Window with Viber enabled**:
283
284 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Viber_message_en.png" width="400"/}}
285
286 You can use [[macros>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Template_engine.WebHome]] in the message text.
287
288 You can also specify a [[messaging campaign category>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Mailing_categories.WebHome]] to send the message only to interested customers.
289
290 **Delivery management**
291
292 By default, SMS messages are delivered only during the system-defined allowed time window (e.g., 9:00 AM to 9:00 PM). If the recipient’s local time is outside this window, the message waits in the queue until the next valid delivery window.
293
294 The **Deliver immediately** checkbox bypasses this rule, sending the message instantly regardless of the recipient’s local time. This is useful when customers are in multiple time zones.
295
296 (% class="box infomessage" %)
297 (((
298 The **Send SMS** action is performed only for customers who:
299
300 * have an active SMS subscription;
301 * have a valid phone number;
302 * are subscribed to the selected messaging category (if specified).
303 )))
304
305 (% class="box warningmessage" %)
306 (((
307 **Important**: Any child actions under **Send SMS** are executed **only** for customers to whom the message was sent (regardless of delivery status).
308 )))
309 )))
310 |(% style="width:417px" %)(((
311 ====== Send push [[image:attach:Push_icon.png]] ======
312 )))|(% style="width:1021px" %)(((
313 Sends a push notification to the customer.
314
315 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Send_PUSH_en.png" width="500"/}}
316
317 Fill in the required fields:
318
319 * **Message title**.
320 * **Message text**. You can use [[template engine macros>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Template_engine.WebHome]].
321 * Sections **My discounts** and **Offer type**. Smart Communications also supports In-app notifications. When using this option, you can select **My discounts** or **Offer type** in the push editor, and choose **Push + Notification** in the **Send** section.
322
323 (% class="box infomessage" %)
324 (((
325 **Note**: Sending In-app notifications requires integration with the existing mobile app’s backend, configured upon Partner request.
326 )))
327
328 * Specify an **external link** or **deep-link** to redirect the customer to another resource or app page.
329 * In the **Send** section, choose:
330 * Push;
331 * Notification;
332 * Push + Notification.
333 * Check **Deliver immediately** to send the push instantly, ignoring the recipient’s local time.
334 * You can specify a [[messaging category>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Mailing_categories.WebHome]] to target interested customers.
335 * Set the **message lifetime** in hours, days, or minutes.
336
337 (% class="box infomessage" %)
338 (((
339 The **Send push** action is performed only for customers who:
340
341 * have an active push subscription;
342 * have a valid push identifier;
343 * are subscribed to the selected messaging category (if specified).
344 )))
345
346 (% class="box warningmessage" %)
347 (((
348 **Important**: Any child actions under **Send push** are executed **only** for customers who received the message (regardless of delivery status).
349 )))
350 )))
351 |(% style="width:417px" %)(((
352 ====== Send email [[image:attach:Mail.png]] ======
353 )))|(% style="width:1021px" %)(((
354 Sends an email to the customer.
355
356 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Send_email_en.png" width="500"/}}
357
358 * Specify the **sender name** and **email address**.
359 * Optionally, set a **reply-to address** by clicking the link and entering an email.
360 * Fill in the **subject** and **message body**. You can use [[email templates>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Email_mass_messaging.Templates.WebHome]] and [[formatting options>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Email_mass_messaging.WebHome||anchor="#HEmailbodyformatting"]].
361 * Attach files by clicking **Upload**.
362 * Add a [[UTM tag>>https://en.wikipedia.org/wiki/UTM_parameters]] to track online campaigns. If set, it will be appended to all links in the email.
363 * Specify a [[messaging category>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Mailing_categories.WebHome]] to target interested customers.
364 * Set the **message lifetime** in hours, days, or minutes.
365 * Check **Deliver immediately** to send the email instantly, ignoring the recipient’s local time.
366 * Check **Use fast delivery** to send via a dedicated mail server for urgent messages (e.g., promo codes). Limited to 200 fast deliveries per day.
367 * After configuration, send a test message by clicking **Send test message**, entering a name and email, and clicking **Send**.
368
369 (% class="box infomessage" %)
370 (((
371 The **Send email** action is performed only for customers who:
372
373 * have an active email subscription;
374 * have a valid email address;
375 * are subscribed to the selected messaging category (if specified).
376 )))
377
378 (% class="box warningmessage" %)
379 (((
380 **Important**: Any child actions under **Send email** are executed **only** for customers who received the message (regardless of delivery status).
381 )))
382 )))
383 |(% style="width:417px" %)(((
384 ====== Send notification [[image:attach:Notification_icon.png||height="47" width="33"]] ======
385 )))|(% style="width:1021px" %)(((
386 Sends an In-App notification to the customer. **In-App notifications** are personalized messages displayed inside the mobile app or website during use.
387
388 (% class="box infomessage" %)
389 (((
390 **In-App notifications** are an optional feature that must be enabled separately. Contact Retail Engine specialists to activate it.
391 )))
392
393 Fill in the required fields:
394
395 * **Message title**.
396 * **Message text**. You can use [[template engine variables and macros>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Template_engine.WebHome]].
397 * Specify an **external link** or **deep-link** to redirect the customer.
398 * Optionally, upload an **image**.
399 * If **Communication policies** are enabled, select a policy from the list.
400 * Set a **priority** for the message.
401 * Check **Deliver immediately** to send instantly, ignoring the recipient’s local time.
402 * Specify a [[messaging category>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Mailing_categories.WebHome]] to target interested customers.
403 * Set the **message lifetime** in hours, days, or minutes.
404
405 (% class="box infomessage" %)
406 (((
407 The **Send notification** action is performed only for customers who:
408
409 * have a non-empty **Push ID**;
410 * have an active push subscription.
411 )))
412
413 (% class="box warningmessage" %)
414 (((
415 **Important**: Any child actions under **Send notification** are executed **only** for customers who received the message (regardless of delivery status).
416 )))
417 )))
418 |(% style="width:417px" %)(((
419 ====== (% id="cke_bm_24063S" style="display:none" %) {{id name="Filter"/}}{{id name="CustomerFilter"/}}(%%)Filter customers [[image:attach:Customer_filter.png]] ======
420 )))|(% style="width:1021px" %)(((
421 Defines which customers the next action will apply to. For example, you can apply the next action only to customers with both SMS and email subscriptions active.
422
423 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Filter_customers_en.png" width="600"/}}
424
425 The **Filter customers** action allows defining separate paths for customers who match the filter and those who do not—splitting the flow into two scenarios:
426
427 * **Positive** — marked with a green plus. Includes all customers meeting the filter conditions;
428 * **Negative** — marked with a red minus. Includes all customers not meeting the filter conditions.
429
430 For example, the filter selects customers to receive an SMS. All others (via the red-minus branch) receive an email.
431
432 Branches can later be merged into a single common action.
433
434 For more details on filtering, see [[Creating a new segment>>doc:Main.Smart_Communications.SMC_Use.Customers.User_segments.WebHome]].
435
436 |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Filter_campaign.png]]
437 )))
438 |(% style="width:417px" %)(((
439 ====== {{id name="Wait"/}}Wait [[image:attach:Wait.png]] ======
440 )))|(% style="width:1021px" %)Introduces a delay before the next action. Specify the delay duration in hours, days, or minutes.
441 |(% style="width:417px" %)(((
442 ====== Wait until date [[image:attach:Wait_till_date.png]] ======
443 )))|(% style="width:1021px" %)(((
444 Delays the next action until a specified date.
445
446 The next action executes at 00:00 on the specified date (according to the time zone set in **Settings > General settings > **[[Contact details>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome||anchor="01"]]** > Time zone**).
447
448 (% class="box infomessage" %)
449 (((
450 If the next action is sending an SMS/push, messages will be delivered later during the time window defined in **Settings > General settings > **[[SMS>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome||anchor="03"]]** > SMS delivery time window**.
451 )))
452 )))
453 |(% style="width:417px" %)(((
454 ====== Show PopUp [[image:attach:PopUp.png]] ======
455 )))|(% style="width:1021px" %)(((
456 Configures a popup message for customers who perform a specific [[trigger action>>doc:||anchor="trigger"]].
457
458 (% class="box infomessage" %)
459 (((
460 **Note**: The **Show PopUp** action requires integration with the [[Mobile App via SDK>>doc:Main.Smart_Communications.SMC_integration.MobileSDK.WebHome]].
461 )))
462
463 Within this action, you can define:
464
465 * **Name** or **title** of the popup;
466 * **Subtitle**;
467 * **Message text** and **button text**;
468 * Optionally, add an **image**;
469 * **{{id name="trigger"/}}Trigger action** — the event that activates the popup (e.g., app/site login);
470 * **Trigger value** — optional; specifies the trigger context (e.g., which catalog section was opened);
471 * **Popup action** — defines what happens when the popup is interacted with (e.g., navigate to cart);
472 * **Popup action value** — optional; specifies the action context (e.g., product or section);
473 * **Primary color code** — matches brand guidelines;
474 * **Secondary color code** — matches brand guidelines;
475 * **Promo code** — if the popup includes a [[promo code>>doc:Main.Smart_Communications.SMC_Use.Promo_codes.WebHome]];
476 * **Lifetime** — popup duration in hours, days, or minutes.
477
478 Campaigns with **Show PopUp** are created in advance using the [[Recurring date>>doc:Main.Smart_Communications.SMC_Use.Campaigns.Triggers.WebHome||anchor="HRepeatdate"]] trigger, which sets the popup creation time.
479
480 The **lifetime** defined here controls how long the popup remains active, while the **trigger action** determines when it appears to the customer.
481
482 For example, if the start date is July 26 at 00:02 with daily recurrence, and the popup lifetime is 1 hour, the **PopUp** will be generated on that date and shown for one hour to customers who perform the trigger action before 01:02 on July 26.
483
484 An additional filter applies based on mobile app communication permissions.
485
486 (% style="background-color:transparent" %)Only one popup can correspond to a single trigger action per customer. If multiple popups are scheduled for the same trigger, only one will display. However, you can create one campaign (with the same trigger) containing multiple chains with different filters.
487 )))
488 |(% style="width:417px" %)(((
489 ====== Check email status [[image:attach:Status_check.png]] ======
490 )))|(% style="width:1021px" %)(((
491 Used after **Send email** to create different follow-up paths based on customer response.
492
493 |(% style="border-color:#ffffff; text-align:center" %)[[image:Check_mail_status_en.png]]
494
495 Possible email statuses:
496
497 * **Not delivered**;
498 * **Delivered, not opened**;
499 * **Opened, no click**;
500 * **Opened, clicked**.
501
502 **Action setup**:
503
504 1. Create a **Check email status** action.
505 2. Add the required number of child actions.
506 3. Edit **Check email status** and assign a criterion (customer response) to each branch.
507
508 (% class="box infomessage" %)
509 (((
510 A **Wait** action must exist between **Send email** and **Check email status** to allow time for customer interaction.
511 )))
512
513 **Example**:
514
515 Send email, wait 5 days, then check status:
516
517 * If opened and clicked → accrue bonus points;
518 * If delivered but not opened → send SMS;
519 * If not delivered → resend email.
520
521 To configure this, add three child actions to **Check email status**:
522
523 * [[Accrue bonus points>>doc:||anchor="H41D43044743844143B43844244C43143E43D44344144BA0"]];
524 * [[Send SMS>>doc:||anchor="H41E44243F44043043243844244CSMSA0"]];
525 * [[Send email>>doc:||anchor="H41E44243F44043043243844244C43F43844144C43C43EA0"]].
526
527 Then edit **Check email status** and assign criteria:
528
529 |(% style="border-color:#ffffff; text-align:center" %)[[image:Status_options_en.png||height="362" width="453"]]
530
531 Resulting campaign chain:
532
533 |(% style="border-color:#ffffff; text-align:center" %)[[image:Chain_status_check_en.png]]
534
535 (% class="box infomessage" %)
536 (((
537 **Note**: Before sending SMS, verify customer eligibility—i.e., apply filters for valid phone number and active SMS subscription.
538 )))
539 )))
540 |(% style="width:417px" %)(((
541 ====== Notify manager [[image:attach:Manager.png]] ======
542 )))|(% style="width:1021px" %)(((
543 Sends an email to a Smart Communications user within your organization.
544
545 |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Report_to_manager_en.png" width="400"/}}
546
547 Specify the **subject** and **message body**. You can use [[template engine constructs>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Template_engine.WebHome]].
548
549 You can send to a specific employee (selected from a dropdown) or assign automatically.
550
551 (% class="box infomessage" %)
552 (((
553 You can manually select any employee registered in the system (**Settings > Users > **employee list**).**
554 )))
555 )))
556 |(% style="width:417px" %)(((
557 ====== {{id name="splitter"/}}Splitter [[image:splitter_icon.png]] ======
558 )))|(% style="width:1021px" %)(((
559 Splits customers into several branches (from 2 to 5), each with its own action chain. Weights are assigned to the branches to determine how customers are distributed.
560
561 The proportion of customers directed to a specific output equals the weight of that output divided by the sum of all weights. In the example shown in the image below, 1/4 = 25% of customers will go to the first and third outputs, while 2/4 = 50% will go to the second output.
562
563 If an output is assigned a weight of zero, no customers will be directed to it.
564
565 |(% style="border-color:#ffffff; text-align:right" %){{lightbox image="splitter_action.png" width="450"/}}|(% style="border-color:#ffffff; text-align:left" %){{lightbox image="splitter_campaign.png" width="300"/}}
566 )))
Created 2025/05/21 04:10
Last edited 2026/09/08 03:41

News
Updates
Tag cloud
Glossary
Site