> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/integrations/analytics-and-data/heap-analytics.md).

# Heap Analytics

**Heap** is a product-analytics platform that automatically captures how visitors interact with your pages and journeys — clicks, form fills, navigation — so you can analyze behavior and improve conversion without instrumenting each event by hand. PeakCommerce can feed Heap the events from your storefront and customer journeys, giving your growth and product teams a clear view of how customers move through buying and self-service flows.

This section covers:

* [Integrating Heap Analytics with PeakCommerce](/integrations/analytics-and-data/heap-analytics/integrating-heap-analytics-with-peakcommerce-for-user-behavior-tracking.md) — connect Heap and start tracking.
* [Type of information available in Heap](/integrations/analytics-and-data/heap-analytics/type-of-information-available-in-heap.md) — what PeakCommerce sends and what you can analyze.
* [Hiding sensitive elements within Heap](/integrations/analytics-and-data/heap-analytics/how-do-i-hide-sensitive-elements-within-heap.md) — keep personal and payment data out of capture.


---

# 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://docs.peakcommerce.com/integrations/analytics-and-data/heap-analytics.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.