> 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/brand-api-reference/reference/actions.md).

# Actions

#### What is an action?

The [action](/brand-api-reference/reference/actions/models.md) object represents [conversion events](/brand-api-reference/reference/conversions.md) that have been credited to partners and are eligible for a payout. 

{% hint style="warning" %}
**Warning:** Action data is retained for 750 days. Older actions cannot be retrieved via the API.
{% endhint %}

The actions object itself contains three main types of information:

1. Details about the conversion event itself (e.g., `OrderId`)
2. Details about the winning click (e.g., `AdId`)
3. Details about the payout calculated by the impact.com system (e.g., `Payout`)

#### Components of an action

An action may contain 1 or more [items](/brand-api-reference/reference/actions/models.md). Items within an action typically represent individual products that are a part of the conversion event. For instance, if you are tracking a retail sale, the items could be each type of product purchased by the consumer. If you are tracking subscriptions, the item could represent the subscription level a customer signed up for.

[Action updates](broken://pages/1a6de104b26417e257c86144a5fe44ffa4994007) allow you to stay up-to-date on the details and current status of all actions processed by the impact.com system. The API functions as a changelog, showing both the initial tracking of a new action and each subsequent modification made. Each record is at a line-item level, meaning that if an action represents a sale of 2 shirts at $40 USD each and 1 hat at $6.99 USD, there will be one initial record for the 2 shirts and another for the 1 hat. If the customer then decides to return 1 shirt, another record will be created showing a difference in quantity, sale amount, and payout associated with the line item. Other sorts of modifications include disposition updates (e.g., when a booked hotel room results in a confirmed stay).

{% hint style="success" %}
**Note:** new `ActionUpdates` will not be created when an action locks or is paid as those details can be inferred from the dates represented.
{% endhint %}

#### Submitting action data

When submitting action data via this API, first decide if this submission method is right for you:


---

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