> 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-grouping-property.md).

# Building a Campaign Grouping property

Cross-channel campaigns are used to track engagement across multiple touchpoints such as email outreach, paid advertising, webinars, and blog content—all centered around a unified campaign message. The Campaign grouping property lets you group all those touches into a single campaign umbrella so you can track engagement and attribution across all channels, under one name.

Please find a quick video explaining how to create cross-channel/integrated campaigns.

{% embed url="<https://www.loom.com/share/62134ada6cae4d7d95c6dd826320604f>" %}

To do this, create a new defined property, then use existing Campaign or Asset-related properties to construct your groupings.

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2F0ZviRb6bvsAYPCrY4db6%2Fimage.png?alt=media&amp;token=ee6ee681-2126-4368-9128-a6572db35129" alt=""><figcaption></figcaption></figure>

Once values are assigned to Campaign property, you can use this property in attribution reports to see which campaigns drove traffic, conversions, or influenced pipeline.

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FASOPbaxRgH2Bq6yCryA2%2Fimage.png?alt=media&amp;token=57edb9c6-e859-48ed-8b43-628480fbd5b1" alt=""><figcaption></figcaption></figure>


---

# 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.hockeystack.com/marketing-intelligence/report-examples-and-insights/properties-and-configuration/building-a-campaign-grouping-property.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.