> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/impact/configuration.md).

# Configuration

Let's review all the fields in the form and how to use them while adding the Impact channel.

<figure><img src="/files/kP7dEFAlXr22m5ChWydj" alt=""><figcaption></figcaption></figure>

### Campaign ID

The unique identifier for your Impact affiliate campaign. This ID is sent with every page view and conversion event to identify which campaign the traffic and conversions belong to. It's required for both page tracking and conversion reporting.

### Account SID

Your Impact account's unique identifier used for API authentication and routing. This SID is used in the API endpoint URL and for Basic authentication when sending conversion events to Impact's API.

### Access Token

The authentication token that provides access to your Impact account's API endpoints. This token is combined with your Account SID to create Basic authentication headers when making API calls to Impact's conversion tracking endpoints.

### Conversion Events

A mapping configuration that links your browser events to specific Impact Event Type IDs. When a browser event occurs (like a purchase or cart addition), the provider looks up the corresponding Impact Event Type ID from this mapping and sends the conversion data to Impact using that ID. This ensures proper event categorization and tracking in your Impact dashboard.

**Event Type ID**\
Enter the Event Type ID from your Impact dashboard for the specific conversion event. This ID tells Impact which type of conversion is being tracked and how to categorize it in your reports.

**Browser Event**\
Select the browser event you want to map (Lead, Subscribe, Purchase, InitiateCheckout, AddToCart, ViewContent) or type a custom event name. This event will trigger the conversion tracking when it occurs on your website.

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.edgetag.io/channels/impact/configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.