> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/model-your-data/model-amplifications/attribution-channel-mapping.md). # Attribution channel mapping ## Attribution channel mapping {% hint style="info" %} Note: Our Model Amplifications feature **only accepts files in CSV format at this time.** Please make sure the files you upload are CSV files. {% endhint %} ## Overview Chord provides an out-of-the-box mapping for pages to the attribution channel. However, brands sometimes have sources and channels that they want to track outside the standard Chord mapping. This configuration replaces the Chord mapping with the brand's custom mapping and adds the additional detail of being able to assign a Sub-Channel to the sources. ### How it works The configuration allows the brand to define the channel of the page based on a combination of the following options: * **Medium** - the UTM Medium for the page * **Source** - the UTM Souce for the page * **GCLID** - whether the page view has a google click id (GCLID) or not * **Query** - any additional UTM parameters in the query including things like utm\_campaign, product or variant id, utm\_term, or utm\_content. * **Referrer** - any referrer details. For each of these, the brand can define the listed field condition's operator - Equal, Not Equal, Contains, Does Not Contain. For example- `Medium Does Not Contain Paid` and `Source Equals Facebook` could be `Organic Social`.The configuration first evaluates the page utm details and then evaluates the referrer. --- # 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.chord.co/model-your-data/model-amplifications/attribution-channel-mapping.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.