LOCALISATION | What are Variable & Fixed Store Segments

Modified on Thu, 31 Aug, 2023 at 10:30 AM

To support Basic Targeting / Localisation across your Retail Display Network, Brands are able to create and use Store Segments. 


Ensuring that your Organisation's Localisation Strategy is used to define your Store Segment Strategy. This will ensure that Brands can align Localisation Efforts across all customer touch-points.


Within the Personalisation Hub Platform we support 2 Different Types of Store Segments:

  1. FIXED STORE SEGMENTS - These are Controlled and Only Visible via HQ-Admin. They are Not Visible to Store Staff. Typically used for serviceability and demographic targeting.
  2. VARIABLE STORE SEGMENTS - These are Controlled and Visible across both HQ-Admin and Retail-Admin (Staff Tablet) Sites. Typically used where Store Managers require a certain level of control (e.g. Out of Stock situations).


When Creating Audiences using Store Segments in AEM, please refer to the Table below:


Segment TypeDescriptionBoost RangeVariable
Fixed Store SegmentFixed Store segments are only visible via HQ Admin and can only be edited by HQ.

50 - 99location-store/displays/0/display_segmentation/formatted_fixed_store_segments
Variable Store SegmentVariable Store segments are visible and editable by both HQ and Retail Staff (via Retail Admin - Store Tablet interface).

50 - 99location-store/displays/0/display_segmentation/formatted_variable_store_segments
Consolidated Store SegmentThis field consolidates both Fixed Store Segments as well as Variable Store Segments. This would be used where you may alternate between using different segment types. Only a single Audience/Segment needs to be created to support both 1 & 2 above.50 - 99location-store/displays/0/display_segmentation/formatted_store_segments

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article