> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/partner-api-reference/reference/webhooks.md).

# Webhooks

Event Notification Postbacks are standard HTTP notifications that can notify you when an action, click, or other event occurs. Event Postbacks can be configured to feed event data into your internal reporting systems, giving an up-to-date view of your events.

## View Event Notification Postbacks

1. From the top navigation bar, select![](/files/XkvyO0qRRvv1s6OTj7Bq)**\[Menu] → Settings.**
2. Under *Technical*, select [**Event Notifications**](https://app.impact.com/secure/mediapartner/accountSettings/view-edit-pingback-settings-flow.ihtml).

## Enable Event Postbacks

The instructions below will help you configure the five types of Event Postbacks.

* **Action Lifecycle Events** will issue an HTTP request to a specified URL (and any included parameters) when an action is tracked, modified, or reversed.
* **Tracking Value Request Events** will issue an HTTP request to a specified URL (and any included parameters) when tracking requests are created.
* **Action Clearing Events** will issue an HTTP request to a specified URL (and any included parameters) when actions are cleared.
* **Action Inquiry Events** will issue an HTTP request to a specified URL (and any included parameters) when action inquiries are created or resolved.
* **Job Completion Events** will issue an HTTP request to a specified URL (and any additional parameters) when a job has been completed for a Report Export or Click Export.

1. From the [**Event Notification Postbacks**](https://app.impact.com/secure/mediapartner/accountSettings/view-edit-pingback-settings-flow.ihtml) screen, hover over the **heading you want to enable** and select  **\[Edit]** on the right side.
2. Add the **URL** that impact.com should use for Event Postbacks, along with any **optional parameters** in the URL. Refer to the section below for a full list of these parameters and an example URL (for the `GET` method).
3. Using the HTTP Method: `GET` is the recommended option, as optional parameters can be passed directly in the URL. Select `POST` if instead your system requires impact.com to submit the data in a request body.
   * If you use the `POST` method, select the **Body Format** from the radio dials.
4. Select **Save** to complete the process.

{% hint style="success" %}
**Note:** Step 3 does not apply to Action Inquiry Events—the query strings are selected using checkboxes instead.
{% endhint %}


---

# 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://integrations.impact.com/partner-api-reference/reference/webhooks.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.