# Breakdowns

### Overview

Breakdowns help you slice your funnel data by specific fields, like country, industry, or custom dimensions.

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FdaMFxQWkdLvDpet82WhN%2FScreenshot%202025-11-11%20at%205.04.14%E2%80%AFPM.png?alt=media&#x26;token=361acb2a-db6c-43c4-b3aa-e3b286803619" alt=""><figcaption></figcaption></figure>

### Prerequisites

* Your CRM integrations are connected and syncing (Salesforce, HubSpot, etc)&#x20;
* You know the exact **Integration > Object > Field** you want to use

### Steps

1. Go to: **Definitions** > **Breakdowns** and click **+ New Breakdown**
2. Give your breakdown a name

   Example: `Territory`
3. Pick your **Integration > Object > Field** in the **Source** section \
   Example: `Salesforce > Account > Territory`
   1. To use multiple fields in one breakdown, click **+ Add new data source** and select the data you want to add
   2. You can also use **Website** data as a base for your breakdown
4. Review Funnel Stage Activation\
   The breakdown will only apply to the highlighted goals. So if you filter your data by a breakdown value, the filter will affect only the highlighted Funnel Stages\
   &#x20;

   <figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2Fa8cLuDafHx1WPKIsj2aV%2FScreenshot%202025-11-26%20at%204.30.57%E2%80%AFPM.png?alt=media&#x26;token=d8226c70-8105-479c-9743-cd086d5a1e87" alt=""><figcaption></figcaption></figure>
5. Create mappings (two options):
   * **Keep Original Values**
     * If you prefer the raw values from the source without grouping, select **Keep Original Values**&#x20;
   * **Group Values** (recommended for tidy reporting)
     1. Click **Group Values** under **Mappings**
     2. Click **+ Add group** and name the group (this name shows in reports)
     3. **Select source(s)** to include for this condition
     4. Define the **logic/conditions** for which raw values will go in this group (e.g., `Territory contains West, Pacific NW`)
        1. *(Optional)* **+Add Condition** creates an AND condition to check for this group<br>

           <figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FlroDeo6RJninaqKBKAwT%2FScreenshot%202025-11-26%20at%204.17.21%E2%80%AFPM.png?alt=media&#x26;token=34dfb048-748a-4825-8c40-bac1ed864c52" alt=""><figcaption></figcaption></figure>
     5. Repeat for each group you need
     6. *(Optional)* Toggle **Group unmapped values to 'other'** to bucket any remaining values into **Other**. Otherwise the unmapped values will be skipped in your breakdown
6. Save the breakdown
   * After saving, allow **5–10 minutes** for the Breakdown to finish initializing and become available across applicable reports.&#x20;

### Troubleshooting

* Multiple objects or sources: If your Breakdown uses relation properties, allow 24–48 hours for relation mappings to complete.
* No values appearing: Verify if your data source is correct, synced and populated
  * Check permissions and data freshness in the integration settings.
  * Create a report using Any Action (Times Done). Breakdown by Action Properties - Action Name and the **Field** you are trying to use in your Breakdown, and check if the data source you're using contains the values you expect <br>

    <figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2F0Wclz5vbKRtmpYPabRTh%2FScreenshot%202025-11-26%20at%204.21.08%E2%80%AFPM.png?alt=media&#x26;token=48af4707-ed10-42d8-a955-2f3b649dd9ab" alt=""><figcaption></figcaption></figure>
* **Unexpected values in “Other”**: Review your **Group Values** logic for typos, or missing mappings&#x20;
  * Example: `US West` vs `US-West`
* **Mis-mapped values:** Grouping conditions apply top-to-bottom. Values will be mapped to the first condition that it satifies, it will not be mapped to multiple&#x20;
  * Put more specific mappings near the top to avoid accidentally mis-mapping&#x20;

### Examples

* **Single source**: `Salesforce > Account > Territory` grouped into `North America`, `EMEA`, `APAC`, `Other`.<br>

  <figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2F1j3wuWyNRu2LbTd2bZH9%2FScreenshot%202025-11-26%20at%205.03.39%E2%80%AFPM.png?alt=media&#x26;token=c1904b80-467c-49a3-a8b6-52353508e280" alt=""><figcaption></figcaption></figure>
* **Multi-source**: `HubSpot > Company > Industry` + `Salesforce > Account > Industry` unified into a single `Industry` Breakdown with consolidated buckets.<br>

  <figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2Fv3GCIgo4X9MLFOx9FMiS%2FScreenshot%202025-11-26%20at%205.01.59%E2%80%AFPM.png?alt=media&#x26;token=050423e5-cedc-478d-8724-e2437be31180" alt=""><figcaption></figcaption></figure>

## Self-migration

To get the most out of HockeyStack, we’re asking you to self-migrate your filters and breakdowns to the new Breakdowns section. The whole process should only take a few minutes.

#### How to migrate?

1. Identify all the breakdown defined properties. These are the ones marked as “Include in filters” that are *not* touchpoints (so exclude channel, asset, etc.).
2. Rename each property you plan to migrate by adding **\[OLD]** to its name.
3. Go to the Breakdowns page and create a new breakdown for each property you're migrating.
4. Replace the old defined properties with your new breakdowns.
5. Navigate to **Settings → Reporting and Tracking → Replace Property in All Definitions**.<br>

   <figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FPeQEQHa8qA5Wg9RZ0EY0%2FScreenshot%202025-11-26%20at%2017.00.23.png?alt=media&#x26;token=bd04efa3-0d44-4be5-b1a1-822787b34dfb" alt=""><figcaption></figcaption></figure>
6. In the first dropdown, select the property marked with **\[OLD]** and replace it with the correct breakdown.
7. Repeat this for every property you’re migrating.
8. Once everything is replaced, delete the old defined properties.

If you run into any edge cases that can’t be mapped in the new Breakdowns view, please reach out to [**support@hockeystack.com**](mailto:support@hockeystack.com)!


---

# 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.hockeystack.com/marketing-intelligence/breakdowns.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.