> 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/attribution/adding-a-self-reported-source-to-your-unified-channel-defined-property.md).
# Self-reported attribution
Start by gathering all of the values in your self-reported source. Build a table report. Use your Self Reported Source field from Action Properties as the breakdown. For a column add Any Action, Times Done.
Now you have all of the values from your self-reported source field. Review your values and create buckets for the self-reported fields. These buckets might include channels you’ve defined in your mappings. In some cases, you might create an entirely new bucket. For example take values like: “linkedin”, “company page”, “Al’s linkedin post”
and group them into: **LinkedIn Organic**
Next, navigate to your Unified Channel Defined Property. Click Properties > Unified Channel > ellipsis on the left > Edit
Create a new mapping. Combine Action Name is Contact Created AND your “self-reported source field” is \[FILL IN VALUE]. Use OR logic or REGEX to map many values into the same bucket. Lastly, map these to existing channels in your Unified Channel or create new channel mappings.
---
# 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/attribution/adding-a-self-reported-source-to-your-unified-channel-defined-property.md?ask=&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.
