> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/destinations/analytics/heap.md). # Heap Heap, part of Contentsquare, is a digital analytics platform that automatically captures every user interaction, such as clicks, taps, form submissions and page views. It lets you define events after the fact, without re-instrumenting your code. Chord sends events to Heap from the browser and from the server. ## What each version does * [**Heap browser**](/activate/event-streaming/destinations/analytics/heap/heap-browser.md) loads the Heap browser SDK in the shopper's browser and sends events from there. Because events originate in the browser, it enables Heap's automatic interaction capture, session replay and heatmap features. In the destination catalog in Chord, you add it as **Heap (Device Mode)**. * [**Heap server**](/activate/event-streaming/destinations/analytics/heap/heap-server.md) sends events to Heap's server-side HTTP API from Chord's servers, so it is not affected by ad blockers or browser restrictions. In the destination catalog in Chord, you add it as **Heap**. ## Why use both The browser version catches on-page behavior and enables session replay and heatmaps. The server version survives ad blockers and closed tabs, and captures events that occur outside the browser. Using both gives you the most coverage. ## Duplicate events Chord doesn't send Heap an event ID, so the two versions don't deduplicate against each other. If you run both, the same event can reach Heap from the browser and from the server. ## Set up * [Heap browser](/activate/event-streaming/destinations/analytics/heap/heap-browser.md) * [Heap server](/activate/event-streaming/destinations/analytics/heap/heap-server.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://docs.chord.co/activate/event-streaming/destinations/analytics/heap.md?ask=&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.