> 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): In this guide, you'll learn how to set up the Addressable Pixel using Google Tag Manager using the Addressable Template.
- [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)
- [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](https://addressable.gitbook.io/knowledge-base/event-tracking/addressable-event-api/postback-event-api-setup-guide.md): Track events with Addressable's server-to-server postback
- [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 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://addressable.gitbook.io/knowledge-base/event-tracking.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.