# API

{% hint style="warning" %}
This section is intended for developers utilizing our APIs to add channels.
{% endhint %}

Below you will find the keys to generate secrets payloads for adding or updating a channel via the [Script API](https://docs.edgetag.io/api/api/script).

Refer to the [configuration page](/channels/impact/configuration.md) for detailed information on the purpose and usage of each input.

### IMPACT\_CAMPAIGN\_ID

In this secret, you would store the Campaign ID from your Impact account.

**Example Value**\
1000

**Type**\
IDENTIFIER

**Optional**\
false

### IMPACT\_ACCOUNT\_SID

In this secret, you would store the Account SID from your Impact account.

**Example Value**\
ILRgLVwtSGCR5542673FyBbN72ifH65535

**Type**\
Text

**Optional**\
false

### IMPACT\_ACCESS\_TOKEN

In this secret, you would store the Access Token from your Impact account.

**Example Value**\
2423423423423423

**Type**\
PASSWORD

**Optional**\
false

### IMPACT\_CONVERSIONS

In this secret, you would store the conversion event mappings as a JSON string.

**Example Value**

```json
[
  {
    "event": "Purchase",
    "id": "36154"
  },
  {
    "event": "AddToCart",
    "id": "36155"
  }
]
```

**Type**\
Text

**Optional**\
false

{% hint style="warning" %}
This field contains a JSON array where each object maps a browser event name to an Impact Event Type ID. The event names can be predefined (Lead, Subscribe, Purchase, InitiateCheckout, AddToCart, ViewContent) or custom user-defined events. 
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.edgetag.io/channels/impact/api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.