Retail Engine, 2026

Changes for page Event communication

From version 11.1
edited by Anastasia Lozinskaia
on 2026/09/09 03:24
Change comment: There is no comment for this version
To version 6.1
edited by Andrej Rylov
on 2025/11/01 10:30
Change comment: Upload new image "event_communication_1.png", version 1.1

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.alozinskaia
1 +XWiki.arylov
Content
... ... @@ -1,7 +1,7 @@
1 1  (% class="lead" %)
2 -Communications triggered by events that happen in the Retail Engine system are classified as event communication.
2 +Communications triggered by events that happen in the Loymax system are classified as event communication.
3 3  
4 -The Retail Engine system can monitor events and respond to them. A complete list of available events is provided in the [[dedicated article>>doc:Main.Usage.MMP.Marketing.Offers.Event_catalog.WebHome]]. For these events, marketers can configure communication channels with LP Members.
4 +The Loymax system can monitor events and respond to them. A complete list of available events is provided in the [[dedicated article>>doc:Main.Usage.MMP.Marketing.Offers.Event_catalog.WebHome]]. For these events, marketers can configure communication channels with LP Members.
5 5  
6 6  The following types of event communication are available in the System:
7 7  
... ... @@ -17,7 +17,7 @@
17 17  * **Balance request** — an LP Member requested their balance at a POS terminal.
18 18  * **Card assigned** — a customer received an LP card.
19 19  * **Purchase completion** — a receipt was finalized.
20 -* **Purchase by friend** — an LP Member who registered as a [[referral>>doc:Main.General_information.Retailengine_Loyalty.Referral_system.WebHome]] made a purchase.
20 +* **Purchase by friend** — an LP Member who registered as a [[referral>>doc:Main.General_information.Loymax_Loyalty.Referral_system.WebHome]] made a purchase.
21 21  
22 22  {{id name="anchor1"/}}The table below lists available communication methods for in-store purchase events:
23 23  
... ... @@ -29,11 +29,13 @@
29 29  |Cashier message|[[Cashier message>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Cashier_message.WebHome]]|(((
30 30  A predefined message appears on the cashier’s screen.
31 31  )))
32 -|SMS|(% colspan="1" rowspan="5" %)[[{{id name="01"/}}Send message>>doc:Main.Usage.MMP.Marketing.Offers.Guide_to_actions.Message_sending .WebHome]]|(((
32 +|SMS|(% colspan="1" rowspan="5" %)[[{{id name="01"/}}Send message>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Message_sending.WebHome]]|(((
33 33  Short text-only messages are sent to LP Members’ phone numbers.
34 +Delivery can be implemented via providers [[Devino Telecom>>https://devinotele.com/ru/?client_id=16647889331001047333]], [[SmsTraffic>>https://www.smstraffic.ru/]], [[StreamTelecom>>https://stream-telecom.ru/]], or using the [[SMPP protocol>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Sms_gateways.Creating_SMPP_gateway.WebHome]].
34 34  )))
35 35  |Email|(((
36 36  Messages are sent to LP Members via email and may include formatted text, images, and links.
38 +Delivery is handled through the [[Devino Telecom>>https://devinotele.com/ru/?client_id=16647889331001047333]] provider or via the [[SMTP protocol>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Email_gateways.WebHome]].
37 37  )))
38 38  |Push|(((
39 39  Push notifications are delivered to smartphones of LP Members who have installed the LP’s mobile application. Messages may contain text only, image only, or both.
... ... @@ -41,9 +41,11 @@
41 41  )))
42 42  |Viber|(((
43 43  Instant messages are sent via Viber to LP Members registered on this messenger. Messages may contain text only, image only, text with a URL button, or text, image, and button combined.
46 +Delivery is implemented via [[providers>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Viber_gateways.WebHome]] Devino Telecom and SmsTraffic.
44 44  )))
45 45  |Social media|(((
46 -Messages are sent to LP Members who have accounts on social media. Messages may contain text only. Message templates must undergo prior moderation by the social media platform.
49 +Messages are sent to LP Members who have accounts on social media (e.g., VKontakte, Odnoklassniki, etc.). Messages may contain text only. Message templates must undergo prior moderation by the social media platform.
50 +Delivery is implemented through providers Devino Telecom and SmsTraffic.
47 47  )))
48 48  
49 49  (% class="box warningmessage" %)
... ... @@ -78,18 +78,18 @@
78 78  * **Social media group joined** — an LP Member joined a social network group.
79 79  * **Social media activity removal** — an LP Member deleted comments, likes, or reposts from their page.
80 80  * **Social media group exit** — an LP Member left a social network group.
81 -* **Inviting friend** — a customer or LP Member acted as a [[referrer>>doc:Main.General_information.Retailengine_Loyalty.Referral_system.WebHome]], and their referral entered the unique friend code during registration.
82 -* **Customer status change** — an LP Member’s [[status>>doc:Main.General_information.Retailengine_Loyalty.Status_system.WebHome]] changed due to an [[offer>>doc:Main.Usage.MMP.Marketing.Offers.Offers_catalog.Offers_with_cards.WebHome]], a [[recurring task>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Setting_regular_task_for_setting_statuses_to_users.WebHome]], or another trigger.
83 -* **Status calculation** — a status was assigned to an LP Member via a [[recurring task>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Status_assignment_event.WebHome]] or an offer with the [[Status assignment>>doc:Main.Usage.MMP.Marketing.Offers.Guide_to_actions.Status_calculation.WebHome]] action.
85 +* **Inviting friend** — a customer or LP Member acted as a [[referrer>>doc:Main.General_information.Loymax_Loyalty.Referral_system.WebHome]], and their referral entered the unique friend code during registration.
86 +* **Customer status change** — an LP Member’s [[status>>doc:Main.General_information.Loymax_Loyalty.Status_system.WebHome]] changed due to an [[offer>>doc:Main.Usage.MMP.Marketing.Offers.Offers_creation_examples.Offers_for_customer.Offers_from_members_status.WebHome]], a [[recurring task>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Setting_regular_task_for_setting_statuses_to_users.WebHome]], or another trigger.
87 +* **Status calculation** — a status was assigned to an LP Member via a [[recurring task>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Status_assignment_event.WebHome]] or an offer with the [[Status assignment>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Status_assignment.WebHome]] action.
84 84  
85 -The [[messaging method>>doc:||anchor="01"]] for the above actions is configured in the Retail Engine Platform by [[creating an offer>>doc:Main.Usage.MMP.Marketing.Offers.Offer_management.Offer_lifecycle.Offer_creation_guide.WebHome]] and selecting the [[Send message>>doc:Main.Usage.MMP.Marketing.Offers.Guide_to_actions.Message_sending .WebHome]] action for a specific [[event>>doc:Main.Usage.MMP.Marketing.Offers.Event_guide.WebHome]]. When setting up this action, you can apply [[filters>>doc:Main.Usage.MMP.Marketing.Offers.Guide_to_filters.WebHome]] and [[counters>>doc:Main.Usage.MMP.Marketing.Counters.WebHome]].
89 +The [[messaging method>>doc:||anchor="01"]] for the above actions is configured in the Loymax Platform by [[creating an offer>>doc:Main.Usage.MMP.Marketing.Offers.General_information.Offers_life_cycle.Creating_offers.WebHome]] and selecting the [[Send message>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Message_sending.WebHome]] action for a specific [[event>>doc:Main.Usage.MMP.Marketing.Offers.Event_catalog.WebHome]]. When setting up this action, you can apply [[filters>>doc:Main.Usage.MMP.Marketing.Offers.Filters.WebHome]] and [[counters>>doc:Main.Usage.MMP.Marketing.Counters.WebHome]].
86 86  
87 87  |(% style="border-color:#ffffff; width:60%" %)(((
88 -After inserting the appropriate [[metavariable>>doc:Main.Usage.MMP.System_settings.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]] values, the message will appear as follows:
92 +After inserting the appropriate [[metavariable>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]] values, the message will appear as follows:
89 89  
90 90  (% class="box" %)
91 91  (((
92 -##Dear Homer Simpson, your bonus account balances are:
96 +##Dear participant Homer Simpson, your bonus account balances are:
93 93  300 bonus points, 52 stars.##
94 94  )))
95 95  
... ... @@ -100,21 +100,21 @@
100 100  
101 101  **Example 1**
102 102  
103 -A customer registers in the System. The registration date serves as the starting point. If the LP Member makes no purchase within two weeks, they receive a message encouraging them to shop at the Partner’s store. If no purchase occurs, a second reminder is sent two weeks later.
107 +A customer registered in the System. The registration date serves as the starting point. If the LP Member makes no purchase within two weeks, they receive a message encouraging them to shop at the Partner’s store. If no purchase occurs, a second reminder is sent two weeks later.
104 104  
105 -|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="event_communication_1.png" width="700"/}}
109 +|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Group 2_1.png" width="700"/}}
106 106  
107 107  **Example 2**
108 108  
109 -A customer registers in the System. If the LP Member makes a purchase within the first two weeks—say, on day five—the next message is scheduled for two weeks after that purchase date.
113 +A customer registered in the System. If the LP Member makes a purchase within the first two weeks—say, on day five—the next message is scheduled for two weeks after that purchase date.
110 110  
111 -|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="event_communication_2.png" width="700"/}}
115 +|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Group 1_1.png" width="700"/}}
112 112  
113 113  {{showhide showmessage="Show examples of event communication use cases" hidemessage="Hide examples of event communication use cases"}}
114 114  (% class="table-bordered" style="width:auto" %)
115 115  (% class="info" %)|**No.**|**Description**|**Event triggering the message**|**Event canceling the message**
116 116  |1|LP Member makes their first purchase but doesn’t return to the store for two weeks.|Purchase completion|Purchase completion
117 -|2|Customer links their phone number but doesn’t complete the application form.|Phone linking|Application form update
121 +|2|Customer binds their phone number but doesn’t complete the application form.|Phone binding|Application form update
118 118  |3|LP Member doesn’t redeem bonus points from their card.|Purchase completion|Payment using bonus card
119 119  |4|LP Member links a social media profile but doesn’t engage in social mechanics.|Social profile linking|Social media activity
120 120  |5|Customer registers but doesn’t invite any referrals.|Registration completion|Friend invitation
... ... @@ -126,7 +126,7 @@
126 126  
127 127  To notify LP Members about upcoming bonus activation, configure a [[recurring task>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Setting_regular_tasks_when_bonuses_activation.WebHome]]. This notification is set up once in the System. If an LP Member has at least the minimum number of bonus points (specified in the recurring task settings) scheduled to activate (become available for redemption) in the defined number of days, they will receive a notification via the selected communication channel, indicating the bonus amount to be activated. All [[communication channels>>doc:Main.Usage.Communications_ways.Non-event_communication.WebHome||anchor="mailing_types"]] used for non-event communication are available for this notification type.
128 128  
129 -Example notification using a [[metavariable>>doc:Main.Usage.MMP.System_settings.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]]:
133 +Example notification using a [[metavariable>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]]:
130 130  
131 131  (% class="box" %)
132 132  (((
... ... @@ -137,7 +137,7 @@
137 137  
138 138  To notify LP Members about expiring bonus points, configure a [[recurring task>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Setting_regular_tasks_when_bonuses_expire.WebHome]]. This notification is also configured once. If an LP Member has at least the minimum number of bonus points (as defined in the recurring task) scheduled to expire in the specified number of days, they will receive a notification via the selected channel, stating the amount. All [[communication channels>>doc:Main.Usage.Communications_ways.Non-event_communication.WebHome||anchor="mailing_types"]] used for non-event communication are available for this purpose.
139 139  
140 -Example notification using a [[metavariable>>doc:Main.Usage.MMP.System_settings.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]]:
144 +Example notification using a [[metavariable>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]]:
141 141  
142 142  (% class="box" %)
143 143  (((
Created 2025/11/01 07:03
Last edited 2026/09/09 09:39

News
Updates
Tag cloud
Glossary
Site