> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/report-examples-and-insights/properties-and-configuration/building-a-campaign-asset-grouping-property.md).
# Building a Campaign / Asset Grouping property
It is quite useful to create groupings out of your more granular touchpoint properties. For example, you might want to group your campaigns by Region, Theme, Objective. Or you might want to group your website pages by their specific Product Area or Target Audience.
To start, create a new defined property.
Use the existing Campaign or Asset properties to build up the groupings.
**Example:**
Optionally, **after all of the mappings,** you could add a catch-all mapping that says "Campaign is not empty -> map to Ungrouped". It is important that this mapping is at the very end. Because the Defined Property is executed from top to bottom, if you add this catch-all in the middle, it will mess up the grouping of all the mappings that come after it.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.hockeystack.com/marketing-intelligence/report-examples-and-insights/properties-and-configuration/building-a-campaign-asset-grouping-property.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.