Wiki source code of 6. E-Commerce
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | (% class="lead" %) |
| |
4.1 | 2 | Smart Communications allows you to automate communications related to e-commerce business processes. |
| |
1.1 | 3 | |
| 4 | (% class="box" %) | ||
| 5 | ((( | ||
| 6 | {{toc/}} | ||
| 7 | ))) | ||
| 8 | |||
| 9 | = Key features = | ||
| 10 | |||
| |
4.1 | 11 | Smart Communications provides the following key integration capabilities with e-commerce systems: |
| |
1.1 | 12 | |
| 13 | * receiving information about changes in the composition and status of an [[order>>doc:Main.Smart_Communications.SMC_Use.E-Commerce.Orders.WebHome]]; | ||
| |
3.1 | 14 | * receiving information about [[web events>>doc:.Web_events.WebHome||anchor="H41243E43743C43E43643D43E441442438"]]; |
| 15 | * working with any set of [[containers>>doc:Main.Smart_Communications.SMC_integration.JS_tracker.WebHome||anchor="HWorkingwithcontainers"]]: cart, favorites, wishlist, bookmarks, etc.; | ||
| 16 | * trigger-based [[messaging campaigns>>doc:Main.Smart_Communications.SMC_Use.Campaigns.WebHome]] based on order-related events, web events, and container-related events; | ||
| |
1.1 | 17 | * [[segmentation>>doc:Main.Smart_Communications.SMC_Use.Customers.User_segments.Segment_builder.WebHome]] based on orders, containers, and web events; |
| |
3.1 | 18 | * [[mass messaging>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.WebHome]] to segments; |
| 19 | * message personalization using the [[template engine>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Template_engine.WebHome]] – inserting order attributes, order line items, products in a container, and web event context data into messages. | ||
| |
1.1 | 20 | |
| 21 | (% class="box infomessage" %) | ||
| 22 | ((( | ||
| |
4.1 | 23 | The Smart Communications integration architecture with e-commerce systems is described in a [[separate article>>doc:Main.Smart_Communications.SMC_integration.Ecom_integration.WebHome]]. |
| |
1.1 | 24 | ))) |
| 25 | |||
| 26 | = Orders = | ||
| 27 | |||
| |
4.1 | 28 | An order is the central object in e-commerce. In Smart Communications, an order is a dynamic object consisting of order line items and having a set of attributes that can change over time. The order composition, delivery address, payment method, etc., can all change. Additionally, an order has three sets of statuses (general status, delivery status, payment status), which can also change independently of each other. For more details on order functionality, see the [[separate article>>doc:Main.Smart_Communications.SMC_Use.E-Commerce.Orders.WebHome]]. |
| |
1.1 | 29 | |
| |
4.1 | 30 | Like all objects in Smart Communications, orders and order line items have a configurable set of [[fields>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Data_field.WebHome]]: system fields that are always present and required for the System to function correctly, and custom fields created according to the Partner's needs. |
| |
1.1 | 31 | |
| |
4.1 | 32 | Order information can be sent to Smart Communications through various channels: |
| |
1.1 | 33 | |
| |
4.1 | 34 | * [[JS tracker>>doc:Main.Smart_Communications.SMC_integration.JS_tracker.WebHome]]. A small JavaScript code snippet is placed on the Partner's website, automatically transmitting information about customer actions on the site to Smart Communications. One such action is placing an order. |
| 35 | * [[Mobile SDK>>doc:Main.Smart_Communications.SMC_integration.MobileSDK.WebHome]]. Code is integrated into the Partner's mobile application to enable calls to the Retail Engine backend. If a customer places an order in the mobile app, this information is automatically transmitted to Smart Communications. | ||
| 36 | * [[REST API>>doc:Main.Smart_Communications.SMC_integration.Data_exchange.SmC_API.WebHome]]. The Partner's master system can transmit order information to Smart Communications via REST API calls (using [[Eorder>>doc:Main.Smart_Communications.SMC_integration.Data_exchange.SmC_API.SmC_API_methods.Eorder.WebHome]] methods for working with orders). | ||
| |
1.1 | 37 | |
| 38 | = Events = | ||
| 39 | |||
| |
4.1 | 40 | Smart Communications can receive information about customer activity in the form of [[events>>doc:Main.Smart_Communications.SMC_Use.Events_SmC.WebHome]] and [[web events>>doc:Main.Smart_Communications.SMC_Use.E-Commerce.Web_events.WebHome]]. |
| |
1.1 | 41 | |
| |
4.1 | 42 | A web event always represents some customer action on a website or in a mobile application. Smart Communications includes a set of preconfigured web events (such as placing an order, viewing a product, or adding a product to a container), and custom web events can also be configured. |
| |
1.1 | 43 | |
| 44 | Events are not necessarily directly related to customer actions; for example, a courier might miss a customer at home, or a customer's RFM segment might change. | ||
| 45 | |||
| 46 | = Containers = | ||
| 47 | |||
| |
4.1 | 48 | A [[container>>doc:Main.Smart_Communications.SMC_integration.JS_tracker.WebHome||anchor="HWorkingwithcontainers"]] is an individual customer product list. Smart Communications includes one system container that cannot be deleted – the **Cart**. It also supports creating any number of custom containers (e.g., Favorites, Notify When Available, etc.). |
| |
1.1 | 49 | |
| |
3.1 | 50 | The [[JS tracker>>doc:Main.Smart_Communications.SMC_integration.JS_tracker.WebHome||anchor="HAddingproducttoacontainer"]] allows tracking events of adding/removing products to/from a container. These events can be used as campaign triggers. Container contents can be used to filter customers in the [[Segment builder>>doc:Main.Smart_Communications.SMC_Use.Customers.User_segments.Segment_builder.WebHome]] and can also be inserted into message text. |
| |
1.1 | 51 | |
| 52 | = Using data = | ||
| 53 | |||
| |
5.1 | 54 | Order, event, and container data are used for building segments and in mass messages and campaigns. |
| |
1.1 | 55 | |
| |
3.1 | 56 | The [[Segment builder>>doc:Main.Smart_Communications.SMC_Use.Customers.User_segments.Segment_builder.WebHome]] allows filtering customers by various parameters related to orders, events, and containers. Segments can be used for sending mass messagings and for analytics. |
| |
1.1 | 57 | |
| |
3.1 | 58 | The message [[template engine>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Template_engine.WebHome]] allows personalizing messages by adding order, event, and container data for a specific customer. Additionally, the template engine can block message delivery to customers who do not meet a specified condition (for example, sending a message with a promo code only to customers who have fewer than 5 orders and whose last order was placed more than a month ago). |
| |
1.1 | 59 | |
| 60 | (% class="box" %) | ||
| 61 | ((( | ||
| 62 | **See also:** | ||
| 63 | |||
| |
3.1 | 64 | * [[Integration with e-commerce systems>>doc:Main.Smart_Communications.SMC_integration.Ecom_integration.WebHome]] |
| |
1.1 | 65 | * [[Orders>>doc:Main.Smart_Communications.SMC_Use.E-Commerce.Orders.WebHome]] |
| |
3.1 | 66 | * [[Events>>doc:Main.Smart_Communications.SMC_Use.Events_SmC.WebHome]] |
| 67 | * [[JS tracker>>doc:Main.Smart_Communications.SMC_integration.JS_tracker.WebHome]] | ||
| 68 | * [[Mobile SDK>>doc:Main.Smart_Communications.SMC_integration.MobileSDK.WebHome]] | ||
| 69 | * [[Smart Communications API>>doc:Main.Smart_Communications.SMC_integration.Data_exchange.SmC_API.WebHome]] | ||
| |
1.1 | 70 | ))) |