Combine content personalizations for multisegment-belonging users

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Audience Targeting Rules Updater
• Labels:
  • fc_20_02
• Epic/Theme:
  • Personalization
  • Segmentation
• Epic Link: tango-content-set-priorities
• Sprint: TANGO | SP_30 | Feb19-Mar04

Motivation

​
The bug LPS-104108  motivated to develop a new configuration in order to mitigate a problem with multisegment-belonging users reported by the customer as a "lack of functionality".

The new configuration allows a user to view all the assets for all personalized views in a given content set, instead of just the asset for the most relevant personalized view. (See PTR-1478 for full context.)
​
When enabled, this configuration brings back a feature from Audience Targeting in previous version closely related to this one (again see PTR-1478 for full details).

This should not be a final solution since the problem needs further consideration, which will be undertaken when prioritized in the product backlog.

Persona

​
Any former user of Audience Targeting that has users belonging to multiple segments and content personalizations for them. Nevertheless, the development is not public as it has to be switched on from System Settings.

Requirements

​

1. Have one user
2. Have at least two segments that the user belongs to
3. Have another segment that the user does not belong to
4. Have a number of assets to work with
5. Have a manual content set with personalized views for each of the available segments
6. Have a dynamic content set with personalized views for each of the available segments
7. Enable configuration in system settings (System Settings > Assets > Content Sets) for both manual and dynamic cases
8. Page with asset publisher configured to display manual content set
9. Page with asset publisher configured to display dynamic content set

 

Acceptance Criteria

 

Note: This behavior should be independent of Experiences.​

Asset Publisher configured with manual content set *WITHOUT pagination shows assets for the two personalized views the user belongs to when the configuration is enabled*

• Given the asset publisher in the page configured without pagination and manual configuration enabled in system settings
• When the user visualizes the asset publisher
• Then the assets for the personalized views associated to the segments that the user belongs are displayed and only those (not even the default personalized view)
  ​
  Asset Publisher configured with dynamic content set WITHOUT pagination shows assets for the two personalized views the user belongs to when the configuration is enabled
• Given the asset publisher in the page configured without pagination and dynamic configuration enabled in system settings
• When the user visualizes the asset publisher
• Then the assets for the personalized views associated to the segments that the user belongs are displayed and only those (not even the default personalzied view)

Asset Publisher configured with manual content set *WITH pagination shows assets for the two personalized views the user belongs to when the configuration is enabled*

• Given the asset publisher in the page configured with pagination and manual configuration enabled in system settings
• When the user visualizes the asset publisher
• Then the assets for the personalized views associated to the segments that the user belongs are displayed and only those (not even the default personalized view)
  ​
  Asset Publisher configured with dynamic content set WITH pagination shows assets for the two personalized views the user belongs to when the configuration is enabled
• Given the asset publisher in the page configured with pagination and dynamic configuration enabled in system settings
• When the user visualizes the asset publisher
• Then the assets for the personalized views associated to the segments that the user belongs are displayed and only those (not even the default personalized view)

​Test Scenarios

Test Scenarios

AC ID	Test Strategy	Test Scenarios	Is it covered by FrontEnd ? (JS-Unit)	Is it covered by BackEnd? (unit or integration)	Poshi?
01	Smoke	Asset Publisher configured with manual content set WITHOUT pagination shows assets for the two personalized views the user belongs to when the configuration is enabled	No	No	-
02	Smoke	Asset Publisher configured with dynamic content set WITHOUT pagination shows assets for the two personalized views the user belongs to when the configuration is enabled	No	No	-
03	Smoke	Asset Publisher configured with manual content set WITH pagination shows assets for the two personalized views the user belongs to when the configuration is enabled	No	No	-
04	Smoke	Asset Publisher configured with dynamic content set WITH pagination shows assets for the two personalized views the user belongs to when the configuration is enabled	No	No	-
05	Sanity	Asset Publisher configured with manual content set does not show assets for the personalized views that the user doesn't belongs to when the configuration is enabled	No	No	-
06	Sanity	Asset Publisher configured with dynamic content set does not show assets for the personalized views that the user doesn't belongs to when the configuration is enabled	No	No	-