Personalized offers in the Loyalty Program
- Manage
- Actions
- Viewers
Choose the export format from the list below:
Options for exportFormat You can navigate through the options using arrow keys, the home and end keys. Select the currently highlighted option by pressing enter or space. Right and left arrows will move focus to the next possible option in the list. The Home key will bring focus to the start of the list and the END key to its end. Up and down arrows allow you to navigate quickly to the start of option categories.
-
Export as Open Document Text (ODT) format using the Office Server
-
Export as Rich Text Format (RTF) using the Office Server
-
Export as HyperText Markup Language (HTML)
Select the pages to export:
- Legend:
- Created Page
- Modified Extension Page
- Clean Extension Page
Questions related to configuration of attributes for personalized offers in the Loyalty Program: favorite products, favorite categories and personal offers.
If the Favorite Products mechanics is configured through the Personal products section of the Marketing Management Platform, the validity period for preferences will be the same for all selected products.
If the Favorite Products mechanics is implemented through a common attribute and import of its value for customers, then the validity period can be set separately for each product.
The same is true for favorite categories, as they are also imported into the common attribute of the customer.
No, it won't. For example, you can set up an offer that will provide preferences to Loyalty Program members for their favorite products/categories. However, if no preferences were given to the customer for any of his favorite products/categories (because no favorite products have been chosen or the validity period for the selected products has expired), a message will be printed on the receipt stating that the products have not been selected.
In such an offer, the period of preference duration for a specific product will be determined by the value from the attribute, and the period of message printing on the receipt will be determined by the validity period of the offer.
Favorite categories work on the basis of attributes. First, the JSON type attribute is created in the Customer attributes section of the Marketing Management Platform. The attribute parameters should include a JSON schema — rules that define the acceptable format of the attribute value and possible actions with individual value parameters.
For example:{"type":"object","properties":{"StartDate":{"type":"string","format":"date-time"},
"EndDate":{"type":"string","format":"date-time"},"GoodsId":{"type":"string","readOnly":true},
"PreferenceValue":{"type":"number","readOnly":true}}}You can specify the type and amount of the preference or not specify them at all. If the type and amount of the preference is specified, each category will have its own preferences. If omitted, the values from the offer will be used.
The attribute value contains an array of category identifiers and optionally the parameters of the provided preferences (type, size, period, etc.). Categories can be formed as product groups or as nodes of the product catalog (one node = one category). The attribute value contains either the UID of the product group or the ItemID of the catalog node.
To implement the Favorite Category mechanics with acceptance, a new parameter — acceptance attribute — is introduced into the JSON schema (and into the imported attribute value accordingly). The parameter is transmitted separately for each category and by default its value is false (the category is not selected). When the customer selects a category, the value of this parameter for the corresponding category changes to true (the category is selected). The offer filters products based on acceptance attribute (false — the filter does not work and the preference is not granted, true — the filter is triggered and the preference can be granted).
The attribute structure and the rules for changing them are identical for the mechanics:
- Favorite products imported into the customer's common attribute;
- Favorite categories imported into the customer's common attribute.
The structure of their attributes is identical, but the name of the parameter storing the identifier of the product/category is different. The attribute structure differs only for the mechanics of favorite products that is configured through the Personal products section of the Marketing Management Platform. It's the parameter values that change, not their set.
No, it is not possible to supplement the attribute.
If there are free cells of favorite products, then the same attribute is filled during selection of the remaining favorite products. The attribute will be overwritten upon occurence of the cells clearing date.
The attribute for favorite categories needs to be completely updated.
Favorite products created in the Personal Products section:
The parameters of the personal products are stored in the tables [dbo].[User_Attribute] and [dbo].[User_Attribute_PersonalOffer].
A separate record is created for each Loyalty Program member in the [dbo].[User_AttributeValue] table, which includes a data array with information about the cells of favorite products and general parameters (cell clearing period and default number of cells). An entry is created in this table only when the customer has referred to a specific attribute of personal products (when the customer decided to view the products available for selection).
Favorite categories and favorite products imported into a common attribute:
The attribute is created manually in the Marketing Management Platform. The created attribute is stored in the [User_Attribute] table as a JSON schema, and the [User_AttributeValue] table stores the JSON with categories.
Last edited 2024/02/22 09:57