> 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/activate/event-streaming/destinations/attribution-and-affiliate/impact.md).

# Impact

Impact is an affiliate and partnership management platform. Chord reports conversions to Impact from the browser and from the server, so Impact can credit each sale to the partner that drove it.

## What each version does

* [**Impact browser**](/activate/event-streaming/destinations/attribution-and-affiliate/impact/impact-browser.md) loads Impact's Universal Tracking Tag (UTT) in the shopper's browser. It identifies the visitor and reports conversions from the page. In the destination catalog in Chord, you add it as **Impact (Device Mode)**.
* [**Impact server**](/activate/event-streaming/destinations/attribution-and-affiliate/impact/impact-server.md) runs on Chord's servers and sends conversions and page loads to Impact's tracking APIs. In the destination catalog in Chord, you add it as **Impact**. It can also forward page, identify and other track events as page loads.

## Why use both

The browser version catches on-page behavior through Impact's own tag. The server version survives ad blockers and closed tabs. Use the browser version when you need browser-based attribution through the UTT script, and add the server version for conversions that must not depend on the shopper's browser.

{% hint style="warning" %}
The two versions read the order ID differently. When an `Order Completed` event carries both `cart_id` and `order_id`, the browser version sends the cart ID and the server version sends the order ID. Impact then receives two different order IDs for the same order.
{% endhint %}

## Set up

* [Impact browser](/activate/event-streaming/destinations/attribution-and-affiliate/impact/impact-browser.md)
* [Impact server](/activate/event-streaming/destinations/attribution-and-affiliate/impact/impact-server.md)


---

# 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/activate/event-streaming/destinations/attribution-and-affiliate/impact.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.