> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/opt-in-to-the-impactcom-consortium.md).
# Opt-in to the impact.com Consortium
The impact.com Consortium is the highest level of cross-device matching. By opting to use impact.com's identity Consortium, you can gain more insight into how your consumers are moving across devices as they move through the conversion path.
All data is anonymized and the identifier that impact.com uses to link cross-channel insights is never shared with its users. At no point will impact.com share any identifiable data with other brands.
{% hint style="warning" %}
**Important:** When opting into the impact.com Consortium, you agree to share and receive anonymized touchpoints of tracked traffic with other brands—you do not lose ownership of your data.
{% endhint %}
#### Opt-in to the impact.com Consortium
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. On the right, under *Tracking*, select **General**.
3.  Toggle on **Identity Matching**.
4. Select **Opt-in to the Impact consortium**.
5. Select **Save**.
---
# 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://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/opt-in-to-the-impactcom-consortium.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.
