# Localization & segmentation

### Localization <a href="#localization" id="localization"></a>

Struct PIM supports any number of languages. Each user is assigned one or more languages which they can view and perhaps edit.

Every attribute type, except Complex and GlobalListValue attributes in the system can be localized. Enabling localization on an attribute adds a dimension to the data entry of that field, allowing for separate data for each language created in the system.

### Dimensions & segments <a href="#dimensions-and-segments" id="dimensions-and-segments"></a>

Besides localization, Struct PIM supports the concept of dimensions with segments. Dimensions are created in the system and segments of that dimension is added to it.

When a dimension is created in the system, implementors get the option of making attributes dimension specific to one of the dimensions created in the system. When an attribute is made dimensionspecific, the attribute field allows for separate data for each segment in the dimension.

{% hint style="info" %}
**Example:** A company wants to be able to create targeted descriptions of products for each of their sales channel. In this case, a Dimension called "Sales channels" is created and a segment is added to that dimension for each sales channel eg. "Google" and "Amazon". Now, when the "Description" attribute is created, it is configured to be dimensionspecific to the Sales channels dimension. This allows for separate texts in the "Description" data field on products for Google and Amazon respectively.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.struct.com/pim3/fundamental-concepts/localization-and-segmentation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.