Document status: RELEASED
Date:
Version Requirements are found under Chain Web Release Notes
Highlights | |
|---|---|
Release version: 2.9.230  |
|
Communicate with members regardless of member terms
(TFS: 164742, 169546, 169770 and 173285)
When creating a member campaign (all types) or a member segment it is possible to include members who have not agreed to be segmented on (not accepted segmentation terms/data analysis), as well as members who have not accepted member terms (incomplete member profiles). Furthermore, when creating a distribution, it is possible to include members who are not subscribed to the selected distribution channel(s). This allows retail chains to communicate important information to all their members for non-marketing purposes.
The user must have access role: “ManageSegmentationGDPR” for this functionality to be visible.
1 - When building the member segment, three checkboxes will appear. The first checkbox will always be ticked, as this is the default for all member segmentations. The user will then have the option to include “members that have not accepted member terms” and “members that have not accepted segmentation terms” in the member segment. The number of members shown in the dashboard will automatically change when ticking one of the checkboxes, seeing as you will including more members into the segment.
2 - When target group is completed and the user moves on to the distribution step, a new checkbox is available. This checkbox will only appear if the checkbox for member terms or segmentation terms is ticked in the member segmentation step. This checkbox allows you to send a distribution to members who are not subscribed to the selected distribution channel(s).
Most likely, a notable portion of the members will not have a phone number or an email address registered, thus making it impossible to communicate with these members.
Using this functionality for marketing purposes may result in breach of GDPR legislation.
For GDPR and security reasons, members who are unsubscribed to the selected distribution channel(s) will automatically be removed from the mailing list in MailChimp after distribution is completed.
This is only supported in MailChimp
Requirements: |
|---|
LoyaltyCampaign version 2.3.2 |
MailChimpIntegration version 2.4.9 |
POS Services 7.75.03300 |
Bonus Campaign
(TFS: 169548, 169549, 169510, 169551 and 174453)
Retail chains can create member campaigns to increase members' bonus level (% return on bonus) for a specific period of time for specific items. The additional bonus is calculated by Reporting after the member has triggered the coupon and made a purchase. The mix type is called “Increased bonus level for selected items” and contains two variations which price rules can be created from. The field for campaign bonus can be left blank in the price rule to define it in the offer of the member campaign.
Fixed bonus level for all members - The user can add a % bonus level which will apply for all members regardless of their current bonus level.
Extra bonus for all members - The user can add a % bonus level in which the members' current bonus levels will increase by. For instance, if the user adds 10%, this means that all members who currently have 10% bonus level will get 20%, those who has 20% will get 30% and so on.
When creating a member campaign and the bonus price rule is selected, the user can choose whether the coupon can be used an unlimited number of times or a defined number of times. If the user selects “unlimited”, the offer can reused unlimited number of times during the campaign period.
Once the offer datils and coupon layout is complete, the user must select which items the offer should apply for during the campaign period. The user will be presented with three different methods of item selection.
Add items - The user can choose to add items, item groups, item lists and item group list using a search bar (same as today).
Select brand and item groups NEW - The user can choose a brand that will generate a list of all item groups that falls under this brand in the item hierarchy. Additionally, the user can filter the item groups shown by adding one or more departments. It is then possible to either tick each item group desired, or select all item groups and remove those unwanted. This often the more efficient way to add many item groups.
All items in the store NEW - This selection will automatically include all items for a given store. The store is automatically assigned based on which stores the campaign was created for. For instance, when creating the campaign, the user chooses “selected stores” and “Store 1”, then all items in Store 1 will apply for the price rule. If “all stores” is chosen, then the price rule will apply for all stores.
If overlapping bonus campaigns are set up and applies to the same member, the following business rules applies:
If multiple x % extra campaigns, the highest % will be used
If multiple "new level = y %" campaigns, the highest % will be used
If both "+ x %" and "new level y %", then "+ x %" will always be used.
Requirements |
|---|
Reporting v.59 |
POS 3.0.0.116 |
POS Services 7.75.03300 |
Segmentation Performance Improvement
(TFS: 171364)
The member segmentation performance has been improved.
New parameter “SegmentationServiceSimpleCacheLifetimeSeconds” has been introduced which is used for setting the time value (seconds) and it determines for how long the empty filter group segmentation is cached. By default, the parameter 3600 means that every 1 hour (3600 seconds) the segmentation is cached, resulting in complex segmentations being loaded significantly faster.
By default, SegmentationServiceSimpleCacheLifetimeSeconds is set to value 3600 and it is not visible in the POS Services Host config file, however it is possible to manually add this parameter as follows:
Requirements: |
|---|
POS Services 7.70.2318 |
POS Services 7.73.3011 |
POS Services 7.75.03300 |
Improvements
Modules | Description |
|---|---|
Member Campaign | Retry mechanism for test groups (TFS: 170012) A retry mechanism has been added to AB campaigns. It is possible to retry the activation of all test groups, if an error occurs causing the campaign or one or more test groups not to be activated.  Validation of test period vs campaign period (TFS: 170058) Validation for test group period vs campaign period is added for AB testing campaigns. This means it is not possible for the length of the test period to exceed the length of the campaign period. This is done to avoid any potential mistakes by the user. Support control groups in potential reach (TFS: 171817) An issue which caused the distribution count in campaign dashboard and analysis tab to display an incorrect number is corrected for standard campaigns with a control group and A/B campaigns with control and test group. Error displaying customer menu from offer (TFS: 169920) An issue where text was invisible in the side menu during the creation of a standard campaign is corrected. Swedish spelling improvements (TFS: 172802) Swedish spelling improvements has been added in campaign wizard and event-driven campaigns details. Incomplete offer setup (TFS: 172859) Several price rules did not trigger a warning when trying to activate a campaign with an incomplete offer. This has been corrected. |
Price Rules | Display price rule 26 & 28 similarly (TFS: 149875) The Price Rule from mix 28 is displayed in exactly the same way as the Price Rule for mix 26. That means the 'Discount' field is placed at the bottom, below 'Min Receipt Amount' field. This is changed to make the user experience more consistent. |
System | Add license for AB testing (TFS: 172770) A license is added for the AB Testing functionality. This functionality will by default not be available for users that are not System Administrators. Requirement: System parameter: LicensingEnabled must be set to true. |
3rd party integration | Surveillance of APSIS jobs (TFS: 172923) 'MemberExport' and 'ResponseImport' do not get 'Faulted' status when APSIS Configuration is missing for loyalty programs not configured to use APSIS. The 'Completed with Warnings' status is displayed instead. This is corrected to avoid unnecessary error messages to enhance efficiency of surveillance. Requirement: ApsisIntegration 1.8.1 (or higher) |