> 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.md).

# Event Tracking

- [Addressable Pixel](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-pixel.md)
- [Pixel via Google Tag Manager (GTM)](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-pixel/pixel-via-google-tag-manager-gtm.md)
- [Google Tag Manager Template - Migration Guide](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-pixel/pixel-via-google-tag-manager-gtm/google-tag-manager-template-migration-guide.md)
- [DEPRECATED: Pixel via Google Tag Manager](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-pixel/pixel-via-google-tag-manager-gtm/deprecated-pixel-via-google-tag-manager.md)
- [CID Integration via Addressable Pixel](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-pixel/cid-integration-via-addressable-pixel.md)
- [Pixel via Javascript SDK (JS)](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-pixel/pixel-via-javascript-sdk-js.md)
- [Content Security Policy (CSP)](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-pixel/content-security-policy-csp.md)
- [Additional Steps for Single Page Application (SPA)](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-pixel/additional-steps-for-single-page-application-spa.md): If your website is a Single-Page Application or Progressive Web App, you may need one additional step so PageView events are tracked on client-side navigations.
- [Addressable Event API](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api.md)
- [Postback Event API Setup Guide: Pixel & S2S](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/postback-event-api-setup-guide-pixel-and-s2s.md): Track events with Addressable's server-to-server postback
- [Postback Event API Setup Guide: Cookie Fetch & S2S](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/postback-event-api-setup-guide-cookie-fetch-and-s2s.md): Track events with Addressable's server-to-server postback
- [Image Request + S2S Postbacks](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/image-request-+-s2s-postbacks.md): Track events with Addressable's server-to-server postback
- [Image Pixel](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/image-pixel.md): Track events with Addressable's image pixel
- [Postback Event API Setup Guide: S2S Only](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/postback-event-api-setup-guide-s2s-only.md): This setup is intended for cases where the Addressable Pixel cannot be implemented, and events need to be sent directly from the server using the Addressable Event API.
- [Events API - Reference](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/events-api-reference.md): The Event's API, also know as the S2S (Server-to-Server) API is used in place of Pixel tracking when there's a 3rd party platforms/applications.
- [Event API Attribution](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/event-api-attribution.md)
- [Attribution with Addressable Pixel (Recommended)](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/event-api-attribution/attribution-with-addressable-pixel-recommended.md)
- [Attribution Without the Addressable Pixel](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/event-api-attribution/attribution-without-the-addressable-pixel.md): Some organizations have compliance policies that restrict the use of tracking pixels. If your organization enforces a no-pixel policy - read the below.


---

# 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.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.