> For the complete documentation index, see [llms.txt](https://addressable.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/event-api-attribution.md).

# Event API Attribution

In order to have proper attribution after setting up the Events API, you need to do additional steps. There's a start-to-finish walkthrough that can be [found here](/knowledge-base/event-tracking/addressable-event-api/postback-event-api-setup-guide-pixel-and-s2s.md), otherwise **continue** to understand only the steps required to set up attribution after the Event API has been configured.

### Path to Attribution Set up

#### **(1) Recommended**: Addressable Pixel + Postback API

* Use this if you can install the Addressable Pixel on your site.
* This is the recommended setup for campaign attribution and is the easiest to maintain.
* Next steps: [Follow the guide](/knowledge-base/event-tracking/addressable-event-api/event-api-attribution/attribution-with-addressable-pixel-recommended.md)

#### **(2) Fallback**: Postback API only (No Pixel)

* Only use this if you **do not have** a pixel set up on your Addressable account.
* Some organizations have compliance policies that restrict tracking pixels.
* If you have a true “no pixel” policy, follow the S2S-only setup.
* Next steps: [Follow the guide](/knowledge-base/event-tracking/addressable-event-api/event-api-attribution/attribution-without-the-addressable-pixel.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://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/event-api-attribution.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.