Retail Engine, 2026

Changes for page Event communication

From 5.1 to 6.1 From 13.1 to 14.1

From 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

To version 13.1

edited by Anastasia Lozinskaia
on 2026/09/09 03:29

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.arylov
++XWiki.alozinskaia

Content

@@ -1,7 +1,7 @@
  (% class="lead" %)
--Communications triggered by events that happen in the Loymax system are classified as event communication.
++Communications triggered by events that happen in the Retail Engine system are classified as event communication.
--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.
++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.
  The following types of event communication are available in the System:
@@ -17,37 +17,32 @@
  * **Balance request** — an LP Member requested their balance at a POS terminal.
  * **Card assigned** — a customer received an LP card.
  * **Purchase completion** — a receipt was finalized.
--* **Purchase by friend** — an LP Member who registered as a [[referral>>doc:Main.General_information.Loymax_Loyalty.Referral_system.WebHome]] made a purchase.
++* **Purchase by friend** — an LP Member who registered as a [[referral>>doc:Main.General_information.Retailengine_Loyalty.Referral_system.WebHome]] made a purchase.
  {{id name="anchor1"/}}The table below lists available communication methods for in-store purchase events:
  (% class="table-bordered" %)
  (% class="info" %)|**Messaging method**|**Action**|**Description**
--|Message to receipt|[[Message to receipt>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Cheque_message.WebHome]]|(((
++|Message to receipt|[[Message to receipt>>doc:Main.Usage.MMP.Marketing.Offers.Guide_to_actions.Message_to_receipt.WebHome]]|(((
  A predefined message appears on the customer’s receipt.
  )))
--|Cashier message|[[Cashier message>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Cashier_message.WebHome]]|(((
++|Cashier message|[[Cashier message>>doc:Main.Usage.MMP.Marketing.Offers.Guide_to_actions.Message_to_cashier.WebHome]]|(((
  A predefined message appears on the cashier’s screen.
  )))
--|SMS|(% colspan="1" rowspan="5" %)[[{{id name="01"/}}Send message>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Message_sending.WebHome]]|(((
++|SMS|(% colspan="1" rowspan="5" %)[[{{id name="01"/}}Send message>>doc:Main.Usage.MMP.Marketing.Offers.Guide_to_actions.Message_sending .WebHome]]|(((
  Short text-only messages are sent to LP Members’ phone numbers.
--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]].
  )))
  |Email|(((
  Messages are sent to LP Members via email and may include formatted text, images, and links.
--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]].
  )))
  |Push|(((
  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.
--Delivery is performed via the [[Microsoft Azure>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Push_gateways.Configuration_push_with_azure.WebHome]] messaging platform or through providers [[Firebase Cloud Messaging and Apple Push Notification>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Push_gateways_FCM.WebHome]] and [[Huawei Mobile Services>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Push_gateways_HMS.WebHome]].
  )))
  |Viber|(((
  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.
--Delivery is implemented via [[providers>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Viber_gateways.WebHome]] Devino Telecom and SmsTraffic.
  )))
  |Social media|(((
--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.
--Delivery is implemented through providers Devino Telecom and SmsTraffic.
++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.
  )))
  (% class="box warningmessage" %)
@@ -56,9 +56,9 @@
  )))
  |(% style="border-color:#ffffff" %)(((
--When configuring the **Message to receipt**, **Cashier message**, and **Send message** actions, you can use [[filters>>doc:Main.Usage.MMP.Marketing.Offers.Filters.WebHome]] and [[counters>>doc:Main.Usage.MMP.Marketing.Counters.WebHome]].
++When configuring the **Message to receipt**, **Cashier message**, and **Send message** actions, you can use [[filters>>doc:Main.Usage.MMP.Marketing.Offers.Guide_to_filters.WebHome]] and [[counters>>doc:Main.Usage.MMP.Marketing.Counters.WebHome]].
--An example of a receipt message using [[metavariables>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]] is shown on the right. For more details on message templates and metavariables, refer to the corresponding [[section>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.WebHome]].
++An example of a receipt message using [[metavariables>>doc:Main.Usage.MMP.System_settings.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]] is shown on the right. For more details on message templates and metavariables, refer to the corresponding [[section>>doc:Main.Usage.MMP.System_settings.Notification_templates_and_metavariables.WebHome]].
  After substituting the appropriate metavariable values, the message will appear as follows:
@@ -82,18 +82,18 @@
  * **Social media group joined** — an LP Member joined a social network group.
  * **Social media activity removal** — an LP Member deleted comments, likes, or reposts from their page.
  * **Social media group exit** — an LP Member left a social network group.
--* **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.
--* **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.
--* **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.
++* **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.
++* **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.
++* **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.
--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]].
++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]].
  |(% style="border-color:#ffffff; width:60%" %)(((
--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:
++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:
  (% class="box" %)
  (((
--##Dear participant Homer Simpson, your bonus account balances are:
++##Dear Homer Simpson, your bonus account balances are:
 bonus points, 52 stars.##
  )))
@@ -104,21 +104,21 @@
  **Example 1**
--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.
++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.
--|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Group 2_1.png" width="700"/}}
++|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="event_communication_1.png" width="700"/}}
  **Example 2**
--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.
++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.
--|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Group 1_1.png" width="700"/}}
++|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="event_communication_2.png" width="700"/}}
  {{showhide showmessage="Show examples of event communication use cases" hidemessage="Hide examples of event communication use cases"}}
  (% class="table-bordered" style="width:auto" %)
  (% class="info" %)|**No.**|**Description**|**Event triggering the message**|**Event canceling the message**
  |1|LP Member makes their first purchase but doesn’t return to the store for two weeks.|Purchase completion|Purchase completion
--|2|Customer binds their phone number but doesn’t complete the application form.|Phone binding|Application form update
++|2|Customer links their phone number but doesn’t complete the application form.|Phone linking|Application form update
  |3|LP Member doesn’t redeem bonus points from their card.|Purchase completion|Payment using bonus card
  |4|LP Member links a social media profile but doesn’t engage in social mechanics.|Social profile linking|Social media activity
  |5|Customer registers but doesn’t invite any referrals.|Registration completion|Friend invitation
@@ -130,7 +130,7 @@
  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.
--Example notification using a [[metavariable>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]]:
++Example notification using a [[metavariable>>doc:Main.Usage.MMP.System_settings.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]]:
  (% class="box" %)
  (((
@@ -141,7 +141,7 @@
  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.
--Example notification using a [[metavariable>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]]:
++Example notification using a [[metavariable>>doc:Main.Usage.MMP.System_settings.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]]:
  (% class="box" %)
  (((

Created 2025/11/01 07:03
Last edited 2026/09/09 09:39

News
Updates
Tag cloud
Glossary
Site

Navigation

Changes for page Event communication

Summary

Details