> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/integrations/heap.md). # Heap Integrating Zigpoll with Heap gives you powerful new ways to collect, analyze, and act on customer feedback. By connecting a Zigpoll and Heap, you can track survey completion events and response data via your Heap dashboard. *** ### Step 1: Copy your Heap App Id 1. Log into your Heap Dashboard 2. Navigate to Account > Manage > Projects. 3. Select the project you want to connect with Zigpoll. 4. Copy the app ID of the project (listed under the environments section). More info can be found here: *** ### Step 2: Enter your information in the Zigpoll dashboard 1. Log into your Zigpoll Dashboard 2. Click Integrations > Heap 3. Enable the Heap integration, enter your App Id from the previous step. *** That's it! Now, whenever you receive a survey completion the event data will be passed through into your Heap dashboard. When a respondent provides a phone number, it is normalized to E.164 format and included as a `phone` event property. --- # 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.zigpoll.com/integrations/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.