> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/analytics/metrics/group-by-aliases.md).

# Group by aliases

Combine group by keys that mean the same thing into one named alias, so you can report on them together.

**Group by** splits a widget into segments, like traffic by device or sales by product category. Sometimes the same information lives under different keys. For example, one feed sends a `color` property and another sends `colour`.

A group by alias combines two or more group by keys under one name, so you can report on them as a single group by.

## Before you begin

* You need edit rights to manage aliases.
* Aliases belong to a container, and every dashboard in that container can use them.

## Create an alias

{% stepper %}
{% step %}

#### Open Group by aliases

Go to **Analytics** → **Metrics** and open the **Group by aliases** tab.
{% endstep %}

{% step %}

#### Name the alias

Enter a name in the **Create new alias** field. This is the name you'll see when grouping a widget, so make it clear, like "Color."
{% endstep %}

{% step %}

#### Select the keys

Under **Keys**, select at least two group by keys to combine. You can choose any group by except other aliases.
{% endstep %}

{% step %}

#### Save

Click **Save**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Aliases work best when each row only has a value for one of the keys, such as property names that differ between feeds or locales.
{% endhint %}

## Use an alias in a widget

When you edit a widget, open the **Group by** dropdown. Your aliases appear in their own **Aliases** section, listed by name.

## Delete an alias

Click the delete icon next to the alias, then click **Save**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.crobox.com/how-to-guides/analytics/metrics/group-by-aliases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.