Wiki source code of 3.2. Triggers
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 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.Usage.Smart_Communications.Customers.All_clients.WebHome||anchor="Profile"]] that meet the condition defined in the trigger. | ||
| 2 | |||
| 3 | (% class="box" %) | ||
| 4 | ((( | ||
| 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. | ||
| 6 | ))) | ||
| 7 | |||
| 8 | === Editing a trigger === | ||
| 9 | |||
| 10 | When creating a new campaign, a trigger is already present in the editing field. The default trigger depends on the enabled functionality: | ||
| 11 | |||
| 12 | * If both [[receipt>>doc:Main.Usage.Smart_Communications.Customers.All_clients.WebHome||anchor="H42743543A438"]] and [[order>>doc:Main.Usage.Smart_Communications.Customers.All_clients.WebHome||anchor="H41743043A43043744B"]] functionality is enabled, the default trigger is **Cheque issued**; | ||
| 13 | * If only [[order>>doc:Main.Usage.Smart_Communications.Customers.All_clients.WebHome||anchor="H41743043A43043744B"]] functionality is enabled, the default trigger is **Order created**; | ||
| 14 | * If both [[receipt>>doc:Main.Usage.Smart_Communications.Customers.All_clients.WebHome||anchor="H42743543A438"]] and [[order>>doc:Main.Usage.Smart_Communications.Customers.All_clients.WebHome||anchor="H41743043A43043744B"]] options are disabled, the default trigger is **Date has come**. | ||
| 15 | |||
| 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**. | ||
| 17 | |||
| 18 | |(% style="border-color:white; text-align:center; width:50%" %)[[image:image1.png]]|(% style="border-color:white; text-align:center; width:50%" %){{lightbox image="image2.png" width="400"/}} | ||
| 19 | |||
| 20 | **The following triggers are available in Loymax Smart Communications:** | ||
| 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" %)((( | ||
| 27 | ====== Lost cart on the site ====== | ||
| 28 | )))|(% style="width:1010px" %)((( | ||
| 29 | Detects cases when the customer adds items to the cart but does not place an order. | ||
| 30 | A cart is considered lost if: | ||
| 31 | |||
| 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). | ||
| 34 | |||
| 35 | (% class="box infomessage" %) | ||
| 36 | ((( | ||
| 37 | For this trigger to work correctly, the [[JS tracker>>doc:Main.Integration.Smart_Com_Integration.JS_tracker.WebHome]] must be configured on the Company’s website. | ||
| 38 | ))) | ||
| 39 | |||
| 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. | ||
| 41 | ))) | ||
| 42 | |(% style="width:428px" %)((( | ||
| 43 | ====== Lost view on the site ====== | ||
| 44 | )))|(% style="width:1010px" %)((( | ||
| 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. | ||
| 46 | |||
| 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. | ||
| 48 | |||
| 49 | (% class="box infomessage" %) | ||
| 50 | ((( | ||
| 51 | For this trigger to work correctly, the [[JS tracker>>doc:Main.Integration.Smart_Com_Integration.JS_tracker.WebHome]] must be configured on the Partner’s website. | ||
| 52 | ))) | ||
| 53 | |||
| 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.Usage.Smart_Communications.Campaign_list.Actions.WebHome||anchor="HWaitA0"]] action after the trigger, followed by a [[Filter customers>>doc:Main.Usage.Smart_Communications.Campaign_list.Actions.WebHome||anchor="HFiltercustomersA0"]] action with the following settings: | ||
| 55 | |||
| 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. | ||
| 60 | |||
| 61 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Filter_customers.png" width="700"/}} | ||
| 62 | ))) | ||
| 63 | |(% style="width:428px" %)((( | ||
| 64 | ====== Lost view of category ====== | ||
| 65 | )))|(% style="width:1010px" %)((( | ||
| 66 | Detects cases where a customer views a category on the website but does not add items to the cart. | ||
| 67 | |||
| 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. | ||
| 69 | |||
| 70 | (% class="box infomessage" %) | ||
| 71 | ((( | ||
| 72 | For this trigger to work correctly, the [[JS tracker>>doc:Main.Integration.Smart_Com_Integration.JS_tracker.WebHome]] must be configured on the Partner’s website. | ||
| 73 | ))) | ||
| 74 | |||
| 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. | ||
| 76 | |||
| 77 | Therefore, we recommend adding a [[Wait>>doc:Main.Usage.Smart_Communications.Campaign_list.Actions.WebHome||anchor="HWaitA0"]] action after the trigger, followed by a [[Filter customers>>doc:Main.Usage.Smart_Communications.Campaign_list.Actions.WebHome||anchor="HFiltercustomersA0"]] action with the following settings: | ||
| 78 | |||
| 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. | ||
| 83 | |||
| 84 | |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Trigger_example_1.png]] | ||
| 85 | |||
| 86 | (% class="box infomessage" %) | ||
| 87 | ((( | ||
| 88 | **Note**: | ||
| 89 | |||
| 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. | ||
| 92 | ))) | ||
| 93 | ))) | ||
| 94 | |(% style="width:428px" %)((( | ||
| 95 | ====== Lost view of product on the site ====== | ||
| 96 | )))|(% style="width:1010px" %)((( | ||
| 97 | Detects cases where a customer views a product on the website but does not add it to the cart. | ||
| 98 | |||
| 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. | ||
| 100 | |||
| 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. | ||
| 102 | |||
| 103 | After the trigger, we recommend adding a [[Wait>>doc:Main.Usage.Smart_Communications.Campaign_list.Actions.WebHome||anchor="HWaitA0"]] action after the trigger, followed by a [[Filter customers>>doc:Main.Usage.Smart_Communications.Campaign_list.Actions.WebHome||anchor="HFiltercustomersA0"]] action with the following settings: | ||
| 104 | |||
| 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. | ||
| 109 | |||
| 110 | |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Trigger_example_1.png.png]] | ||
| 111 | |||
| 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. | ||
| 113 | |||
| 114 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Lost_view_en.png" width="400"/}} | ||
| 115 | |||
| 116 | The screenshot shows a configuration example where the trigger fires only when a customer views products priced above 1,000 RUR. | ||
| 117 | |||
| 118 | (% class="box infomessage" %) | ||
| 119 | ((( | ||
| 120 | For this feature to work correctly, the [[JS tracker>>doc:Main.Integration.Smart_Com_Integration.JS_tracker.WebHome]] must transmit the product price in the ##price## field of the ##view_product## event. | ||
| 121 | ))) | ||
| 122 | ))) | ||
| 123 | |(% style="width:428px" %)((( | ||
| 124 | ====== Anniversary ====== | ||
| 125 | |||
| 126 | |||
| 127 | )))|(% style="width:1010px" %)((( | ||
| 128 | ((( | ||
| 129 | Detects X days before/after the anniversary of: | ||
| 130 | |||
| 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"/}} | ||
| 137 | ))) | ||
| 138 | |||
| 139 | ((( | ||
| 140 | The trigger allows you to: | ||
| 141 | |||
| 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; | ||
| 151 | 1*. Every 10 days. | ||
| 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”). | ||
| 156 | |||
| 157 | Trigger usage examples: | ||
| 158 | |||
| 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. | ||
| 162 | ))) | ||
| 163 | ))) | ||
| 164 | |(% style="width:428px" %)((( | ||
| 165 | ====== Days since order ====== | ||
| 166 | )))|(% style="width:1010px" %)((( | ||
| 167 | The trigger fires when the specified number of days has passed since the customer placed an online [[order>>doc:Main.Usage.Smart_Communications.Orders.WebHome]]. | ||
| 168 | |||
| 169 | For example, customers who haven’t placed a new order within 30 days after their last order: | ||
| 170 | |||
| 171 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Days_since_order.png" width="400"/}} | ||
| 172 | ))) | ||
| 173 | |(% style="width:428px" %)((( | ||
| 174 | ====== Days since receipt ====== | ||
| 175 | )))|(% style="width:1010px" %)((( | ||
| 176 | The trigger fires when the specified number of days has passed since the receipt appeared in the system. | ||
| 177 | |||
| 178 | For example, customers who have not made any purchases within 60 days after their last receipt: | ||
| 179 | |||
| 180 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Days_since_receipt.png" width="400"/}} | ||
| 181 | ))) | ||
| 182 | |(% style="width:428px" %)((( | ||
| 183 | ====== Days since registration ====== | ||
| 184 | )))|(% style="width:1010px" %)((( | ||
| 185 | The trigger fires when the specified number of days has passed since the customer’s registration. | ||
| 186 | |||
| 187 | The trigger fires only if the **Registration date** field is not empty in the [[customer profile>>doc:Main.Usage.Smart_Communications.Customers.All_clients.WebHome||anchor="H41F44043E44443843B44C43A43B43843543D442430"]]. | ||
| 188 | ))) | ||
| 189 | |(% style="width:428px" %)((( | ||
| 190 | ====== Added a product to the container ====== | ||
| 191 | )))|(% style="width:1010px" %)((( | ||
| 192 | Detects when a customer adds an item to the specified container. | ||
| 193 | |||
| 194 | Select the desired container from the dropdown list in the [[**Container**>>doc:Main.Integration.Smart_Com_Integration.JS_tracker.WebHome||anchor="HWorkwithcontainers"]] field. | ||
| 195 | |||
| 196 | (% class="box infomessage" %) | ||
| 197 | ((( | ||
| 198 | **Note**: | ||
| 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.Integration.Smart_Com_Integration.JS_tracker.WebHome]]. | ||
| 200 | ))) | ||
| 201 | ))) | ||
| 202 | |(% style="width:428px" %)((( | ||
| 203 | ====== Item ordered ====== | ||
| 204 | )))|(% style="width:1010px" %)((( | ||
| 205 | Detects when a product is [[ordered>>doc:Main.Usage.Smart_Communications.Orders.WebHome]] on the website. | ||
| 206 | |||
| 207 | To define the order status for which the trigger should fire, fill in the **Order statuses** field. | ||
| 208 | |||
| 209 | To select a product, begin typing its name in the **Product** field. Matching products will appear in the list. | ||
| 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" %)((( | ||
| 216 | Detects when a product from a specific category is [[ordered>>doc:Main.Usage.Smart_Communications.Orders.WebHome]]. | ||
| 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 | |||
| 220 | Select the desired [[classifier>>doc:Main.Usage.Smart_Communications.Settings_SC.Classifiers.WebHome]] from the **Classifier** dropdown. | ||
| 221 | |||
| 222 | To select a category, begin typing its name in the **Category** field. Matching categories will appear in the list. | ||
| 223 | |||
| 224 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Product_category_order.png" width="400"/}} | ||
| 225 | ))) | ||
| 226 | |(% style="width:428px" %)((( | ||
| 227 | ====== Product in cart is low on stock ====== | ||
| 228 | )))|(% style="width:1010px" %)The trigger fires when items placed in the customer’s cart but not purchased are running out of stock. | ||
| 229 | |(% style="width:428px" %)((( | ||
| 230 | ====== The price of the viewed product has changed ====== | ||
| 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" %)((( | ||
| 239 | ====== Product price has changed ====== | ||
| 240 | )))|(% style="width:1010px" %)((( | ||
| 241 | Detects price changes for a product. | ||
| 242 | |||
| 243 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Product_price_en.png" width="400"/}} | ||
| 244 | |||
| 245 | Select the desired container from the **Container** dropdown. | ||
| 246 | |||
| 247 | Specify the **price change direction** (decreased or increased) and set the **minimum change** value (absolute value or percentage). | ||
| 248 | ))) | ||
| 249 | |(% style="width:428px" %)((( | ||
| 250 | ====== Order status changed ====== | ||
| 251 | )))|(% style="width:1010px" %)((( | ||
| 252 | Detects changes in [[order>>doc:Main.Usage.Smart_Communications.Orders.WebHome]] status. | ||
| 253 | |||
| 254 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Order_status_changed.png" width="400"/}} | ||
| 255 | |||
| 256 | Specify the **order search depth** (in days), and select the **initial** and **current** order statuses. | ||
| 257 | ))) | ||
| 258 | |(% style="width:428px" %)((( | ||
| 259 | ====== Customer registration ====== | ||
| 260 | )))|(% style="width:1010px" %)Detects when a customer registers in the System. | ||
| 261 | |(% style="width:428px" %)((( | ||
| 262 | ====== Customer registration + filter ====== | ||
| 263 | )))|(% style="width:1010px" %)Detects when a customer registers in the System and allows an additional filter: **Customer ID contains**. | ||
| 264 | |(% style="width:428px" %)((( | ||
| 265 | ====== Viewed the page on the site ====== | ||
| 266 | )))|(% style="width:1010px" %)((( | ||
| 267 | Detects when a customer visits a specific section of the website. | ||
| 268 | |||
| 269 | To select a section, begin typing its name in the **Section** field. Matching sections will appear in the list. | ||
| 270 | ))) | ||
| 271 | |(% style="width:428px" %)((( | ||
| 272 | ====== The customer visited the site ====== | ||
| 273 | )))|(% style="width:1010px" %)Detects when a customer visits the website. | ||
| 274 | |(% style="width:428px" %)((( | ||
| 275 | ====== Viewed the product on the site ====== | ||
| 276 | )))|(% style="width:1010px" %)((( | ||
| 277 | Detects when a product is viewed on the website. | ||
| 278 | |||
| 279 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Viewed_product_en.png" width="400"/}} | ||
| 280 | |||
| 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. | ||
| 282 | ))) | ||
| 283 | |(% style="width:428px" %)((( | ||
| 284 | ====== Viewed the product category on the site ====== | ||
| 285 | )))|(% style="width:1010px" %)((( | ||
| 286 | Detects when a product from a specific category is viewed. | ||
| 287 | |||
| 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. | ||
| 289 | ))) | ||
| 290 | |(% style="width:428px" %)((( | ||
| 291 | ====== Item purchased ====== | ||
| 292 | )))|(% style="width:1010px" %)((( | ||
| 293 | Detects when a product is purchased. | ||
| 294 | |||
| 295 | To select a product, begin typing its name in the **Product** field. Matching products will appear in the list. | ||
| 296 | ))) | ||
| 297 | |(% style="width:428px" %)((( | ||
| 298 | ====== Item from specific category ====== | ||
| 299 | )))|(% style="width:1010px" %)((( | ||
| 300 | Detects when a product from a specific category is purchased. | ||
| 301 | |||
| 302 | To select a category, begin typing its name in the **Category** field. Matching categories will appear in the list. | ||
| 303 | ))) | ||
| 304 | |(% style="width:428px" %)((( | ||
| 305 | ====== Date has come ====== | ||
| 306 | )))|(% style="width:1010px" %)((( | ||
| 307 | Launches the campaign on the selected date. | ||
| 308 | |||
| 309 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Due_date_en.png" width="400"/}} | ||
| 310 | |||
| 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.Usage.Smart_Communications.Settings_SC.Settings.WebHome||anchor="01"]]** > Time zone**). | ||
| 312 | |||
| 313 | (% class="box infomessage" %) | ||
| 314 | ((( | ||
| 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.Usage.Smart_Communications.Settings_SC.Settings.WebHome||anchor="03"]]** > SMS delivery time window**. | ||
| 316 | ))) | ||
| 317 | |||
| 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). | ||
| 319 | |||
| 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. | ||
| 321 | ))) | ||
| 322 | |(% style="width:428px" %)((( | ||
| 323 | ====== Date come for order ====== | ||
| 324 | )))|(% style="width:1010px" %)((( | ||
| 325 | Launches the campaign a certain number of days before/after/on the date specified in an [[order>>doc:Main.Usage.Smart_Communications.Orders.WebHome]] field. | ||
| 326 | |||
| 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. | ||
| 328 | |||
| 329 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Date_for_order" width="400"/}} | ||
| 330 | |||
| 331 | To select the date field, begin typing its name in the **Date field** input. Matching fields will appear in the list. | ||
| 332 | |||
| 333 | Available options for trigger: | ||
| 334 | |||
| 335 | * On the specified date; | ||
| 336 | * N days before the date; | ||
| 337 | * N days after the date. | ||
| 338 | |||
| 339 | The trigger fires at 00:00 (according to the time zone configured in **Settings > General settings > **[[Contact details>>doc:Main.Usage.Smart_Communications.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.Usage.Smart_Communications.Campaign_list.Actions.WebHome||anchor="HWaitA0"]] action, or specify a launch time in **Start at ... hours ... minutes**. | ||
| 340 | |||
| 341 | If the trigger should fire only for orders with a specific status, select the desired status from the **Order statuses** dropdown. | ||
| 342 | ))) | ||
| 343 | |(% style="width:428px" %)((( | ||
| 344 | ====== Date come for client ====== | ||
| 345 | )))|(% style="width:1010px" %)((( | ||
| 346 | Launches the campaign on the date specified in a field of the customer’s profile. | ||
| 347 | |||
| 348 | |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Customer_date.png]] | ||
| 349 | |||
| 350 | You can link campaign launches to customer-specific dates, such as: | ||
| 351 | |||
| 352 | * Birthday; | ||
| 353 | * Registration date; | ||
| 354 | * Date of first receipt; | ||
| 355 | * Date of last receipt; | ||
| 356 | * Child’s birthday; | ||
| 357 | * Upcoming bonus deactivation date; | ||
| 358 | * RFM segment change date. | ||
| 359 | |||
| 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.Usage.Smart_Communications.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.Usage.Smart_Communications.Campaign_list.Actions.WebHome||anchor="HWaitA0"]] action, or specify a launch time in **Start at ... hours ... minutes**. | ||
| 361 | |||
| 362 | (% class="box infomessage" %) | ||
| 363 | ((( | ||
| 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.Usage.Smart_Communications.Settings_SC.Settings.WebHome||anchor="03"]]** > SMS delivery time window**. | ||
| 365 | ))) | ||
| 366 | |||
| 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). | ||
| 368 | |||
| 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. | ||
| 370 | ))) | ||
| 371 | |(% style="width:428px" %)((( | ||
| 372 | ====== Date come for cheque ====== | ||
| 373 | )))|(% style="width:1010px" %)((( | ||
| 374 | Launches the campaign a certain number of days before/after/on the date specified in one of the receipt [[fields>>doc:Main.Usage.Smart_Communications.Settings_SC.Data_field.WebHome]]. | ||
| 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 | |||
| 386 | The trigger fires at 00:00 (according to the time zone configured in **Settings > General settings > **[[Contact details>>doc:Main.Usage.Smart_Communications.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.Usage.Smart_Communications.Campaign_list.Actions.WebHome||anchor="HWaitA0"]] action, or specify a launch time in **Start at ... hours ... minutes**. | ||
| 387 | ))) | ||
| 388 | |(% style="width:428px" %)((( | ||
| 389 | ====== Bonus expected expiration ====== | ||
| 390 | )))|(% style="width:1010px" %)((( | ||
| 391 | Launches the campaign when bonus points expiration is expected for the customer. | ||
| 392 | |||
| 393 | (% class="box infomessage" %) | ||
| 394 | ((( | ||
| 395 | This trigger is available only when Loyalty Program integration is enabled. Integration setup is performed via a request to Technical Support. | ||
| 396 | ))) | ||
| 397 | |||
| 398 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Bonus_expiration_en.png" width="400"/}} | ||
| 399 | |||
| 400 | In the **Days to the nearest deactivation** and **Number of deactivation bonuses** fields, you can set the condition as: | ||
| 401 | |||
| 402 | * greater than; | ||
| 403 | * less than; | ||
| 404 | * greater than or equal to; | ||
| 405 | * less than or equal to; | ||
| 406 | * equal to; | ||
| 407 | * number of days; | ||
| 408 | * number of bonus points. | ||
| 409 | |||
| 410 | For example: the trigger fires for customers whose bonuses (over 500 points) will expire in 7 days or less. | ||
| 411 | ))) | ||
| 412 | |(% style="width:428px" %)((( | ||
| 413 | ====== Repeat date ====== | ||
| 414 | )))|(% style="width:1010px" %)((( | ||
| 415 | Enables **recurring campaigns** on specified dates. | ||
| 416 | |||
| 417 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Repeat_date.png" width="400"/}} | ||
| 418 | |||
| 419 | **Recurrence rules** define how often the campaign runs. Select the desired option in the **Frequency** field: | ||
| 420 | |||
| 421 | * Daily; | ||
| 422 | * Weekly; | ||
| 423 | * Monthly; | ||
| 424 | * Yearly. | ||
| 425 | |||
| 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.Usage.Smart_Communications.Settings_SC.Settings.WebHome||anchor="01"]]** > Time zone**). | ||
| 427 | |||
| 428 | (% class="box infomessage" %) | ||
| 429 | ((( | ||
| 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.Usage.Smart_Communications.Settings_SC.Settings.WebHome||anchor="03"]]** > SMS delivery time window**. | ||
| 431 | ))) | ||
| 432 | |||
| 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: | ||
| 436 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Daily_campaign.png" width="400"/}} | ||
| 437 | {{/showhide}} | ||
| 438 | |||
| 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. | ||
| 443 | |||
| 444 | Example: every other week, on Thursdays and Sundays: | ||
| 445 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Weekly_campaign.png" width="400"/}} | ||
| 446 | {{/showhide}} | ||
| 447 | |||
| 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: | ||
| 452 | |||
| 453 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Monthly_1.png" width="400"/}} | ||
| 454 | |||
| 455 | * Runs on special days. Example: on the last business day of each month: | ||
| 456 | |||
| 457 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Monthly_2.png" width="400"/}} | ||
| 458 | |||
| 459 | {{/showhide}} | ||
| 460 | |||
| 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: | ||
| 464 | |||
| 465 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Yearly_campaign.png" width="400"/}} | ||
| 466 | {{/showhide}} | ||
| 467 | ))) | ||
| 468 | |(% style="width:428px" %)((( | ||
| 469 | ====== Segment is changed ====== | ||
| 470 | )))|(% style="width:1010px" %)((( | ||
| 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. | ||
| 472 | |||
| 473 | First, [[create a segment>>doc:Main.Usage.Smart_Communications.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. | ||
| 474 | |||
| 475 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="RFM_segment_en.png" width="400"/}} | ||
| 476 | |||
| 477 | If you enter * instead of a number for a parameter, that parameter is ignored and can take any value. | ||
| 478 | |||
| 479 | Example: track customers in R-segment category 3, regardless of F and M values: | ||
| 480 | |||
| 481 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Segment_example_en.png" width="400"/}} | ||
| 482 | ))) | ||
| 483 | |(% style="width:428px" %)((( | ||
| 484 | ====== User segment change ====== | ||
| 485 | )))|(% style="width:1010px" %)((( | ||
| 486 | Allows selecting a segment containing customers for whom the trigger should fire. | ||
| 487 | |||
| 488 | First, [[create a segment>>doc:Main.Usage.Smart_Communications.Customers.User_segments.Segment_builder.WebHome]] or select one from the dropdown list. | ||
| 489 | ))) | ||
| 490 | |(% style="width:428px" %)((( | ||
| 491 | ====== Cheque issued ====== | ||
| 492 | )))|(% style="width:1010px" %)((( | ||
| 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. | ||
| 494 | |||
| 495 | |(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Receipt_issued.png||height="255" width="486"]] | ||
| 496 | |||
| 497 | Optionally, you can set the **cheque search depth** (in days) by filling in the corresponding field. | ||
| 498 | ))) | ||
| 499 | |(% style="width:428px" %)((( | ||
| 500 | ====== Event occurred ====== | ||
| 501 | )))|(% style="width:1010px" %)((( | ||
| 502 | Detects custom events. | ||
| 503 | |||
| 504 | To select an event, begin typing its name in the **Event name** field. Matching events will appear in the list. | ||
| 505 | |||
| 506 | Event examples: | ||
| 507 | |||
| 508 | * Call Center inquiry; | ||
| 509 | * Notification of product restock. | ||
| 510 | |||
| 511 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Event_occurred.png" width="600"/}} | ||
| 512 | |||
| 513 | For more details, refer to the dedicated [[article>>doc:Main.Usage.Smart_Communications.Events_SmC.WebHome]]. | ||
| 514 | |||
| 515 | (% class="box infomessage" %) | ||
| 516 | ((( | ||
| 517 | The list of tracked events is configured during System implementation. | ||
| 518 | ))) | ||
| 519 | ))) | ||
| 520 | |(% style="width:428px" %)((( | ||
| 521 | ====== Web event occurred ====== | ||
| 522 | )))|(% style="width:1010px" %)((( | ||
| 523 | Detects events on the website or in the Mobile Application. | ||
| 524 | |||
| 525 | To select an event, begin typing its name in the **Event name** field. Matching events will appear in the list. | ||
| 526 | |||
| 527 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Web_event.png" width="400"/}} | ||
| 528 | |||
| 529 | Web event examples: | ||
| 530 | |||
| 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. | ||
| 537 | ))) | ||
| 538 | |(% style="width:428px" %)((( | ||
| 539 | ====== Poll completed ====== | ||
| 540 | )))|(% style="width:1010px" %)The trigger fires when a customer complets a [[poll>>doc:Main.Usage.Smart_Communications.Polls.WebHome]]. | ||
| 541 | |(% style="width:428px" %)((( | ||
| 542 | ====== Days since last visit to the site ====== | ||
| 543 | )))|(% style="width:1010px" %)The trigger fires when the specified number of days has passed since the customer’s last website visit. | ||
| 544 | |(% style="width:428px" %)((( | ||
| 545 | ====== Order created ====== | ||
| 546 | )))|(% style="width:1010px" %)((( | ||
| 547 | This is the default trigger when [[order>>doc:Main.Usage.Smart_Communications.Orders.WebHome]] functionality is enabled. It fires upon order placement in the online store. | ||
| 548 | |||
| 549 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Order_made.png" width="400"/}} | ||
| 550 | ))) | ||
| 551 | |(% style="width:428px" %)((( | ||
| 552 | ====== System event ====== | ||
| 553 | )))|(% style="width:1010px" %)((( | ||
| 554 | Detects system events. To select an event, begin typing its name in the **Event name** field. Matching events will appear in the list. | ||
| 555 | |||
| 556 | Event example: product X is back in stock. | ||
| 557 | |||
| 558 | For more details, refer to the dedicated [[article>>doc:Main.Usage.Smart_Communications.Events_SmC.WebHome]]. | ||
| 559 | |||
| 560 | (% class="box infomessage" %) | ||
| 561 | ((( | ||
| 562 | The list of tracked events is configured during System implementation. | ||
| 563 | ))) | ||
| 564 | ))) | ||
| 565 | |(% style="width:428px" %)((( | ||
| 566 | ====== Action worked ====== | ||
| 567 | )))|(% style="width:1010px" %)((( | ||
| 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). | ||
| 569 | |||
| 570 | |(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Action_trigger_en.png" width="400"/}} | ||
| 571 | )))``` |