Our customer has highly regionalised content and various user groups. They are directly impacted by the deprecation of segments, because they are an integrated part of their current solution. Currently, around 200 segments have been created. This feature request is to provide you all the required information about the use case. If required, our customer is open for deeper discussions on the topic.
What is the problem you are trying to solve?
Our customer needs to make content available based on a selection of:
- business units
- countries/regions
- user groups
- cookie data.
This means that they assign roles and personalise collections based on a combination of multiple user groups and country assignments.
The user groups are managed in Microsoft Entra and imported into Liferay. The countries, as well as other user attributes, are imported into Liferay during SAML authentication.
Example: Portal homepages:
On the Portal homepage, tiles link to the sites. The online shop is accessible to dealers, retail- and sales customers from the EMEA, Americas, India, Australia and Southern Africa regions; distributors, retail and sales customers from other regions are granted access to different shops or none at all. The content available to these user groups also differ. Whilst dealers are permitted to view our price lists, customers are not allowed to access this information. Naturally, there are also price lists for different regions.
They use segments to assign the combination of groups and countries to different roles, to which we then grant authorisation for the tiles and content.
Example for Segments:
-
DEALERS-France:
User Group equals 6000_F AND DEALERS
→ Dealers which are assiciated with their Company in France -
Indian-Region-Users:
User Group equals RetailCustomer OR DEALERS OR SalesCustomer
AND
Country equals Bangladesh Or Bhutan Or India Or Indien Or Maldives Or Maledives OR Nepal
→ Retail Customers, Sales Customers or Dealers from the Indian Region -
WORKSHOP-CONS:
User Group equals 8000_PMIB AND WORKSHOP AND CONS
→ Construction machines content managed by Spain for certfies Workshops
Example of jobs on the global website:
Here they use collections which are organised differently for regions such as Spain or India than for EMEA.
The HR departments in each region offer different services and, naturally, have different points of contact and legal requirements.
To personalise the collections, we use the segments derived directly from the country assignments. Similarly, our company and product information is filtered and displayed according to region.
Example for Segments:
- REGION-Spain:
Cookies Equals country_id=36190 OR country_id=36144
→ Cookies set for Spain or Portugal
Example: internal services for our global staff
We currently serve staff from four different business divisions, which are in turn subdivided into individual companies.
These individual companies differ not only by country but also by product group. Internal users therefore have the company and country specified in their user attributes and are members of an internal user group, a company group and groups that specify the product area.
Thanks to this segmentation, internal users only see company content and offerings relevant to their country and product group.
Specifically, service information, for example, is provided depending on the products sold in the region and the product groups.
Example for Segments:
-
IMX-Users:
User Group Equals IMX OR Slovenia SI
→ Two Companies for one product group -
P-USERS:
User Group Equals P_USERS Or IMX Or PL2M Or America PA Or Andean Or Brasil (… 20+ more countries)
→ All P Group Members
What is your project about? (e. g. Intranet, Partner Portal, Enterprise Website, etc)
Global Websites, Product Websites, Microsites, Intranet and Partner Portal for 3 brands, Partner Portal for a 4th brand
What is your proposed solution? (optional)
Keeping segments alive or use another mechanism with the same functionality