> 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/triple-whale.md).

# Triple Whale

Get the most out of Zigpoll and Triple Whale

**Step #1: Create your integration**

1. Get your Api Key from Triple Whale. You can access your key by following the steps here: <https://kb.triplewhale.com/en/articles/8116412-creating-and-managing-api-keys>​
2. In Zigpoll: Go to **Integrations** in the account sidebar and enable the Triple Whale Integration
3. Enter your api key into the input fields and press save.

**Step #2: Collect Your Data**

Once your integration has been completed, any post purchase survey submissions that are captured from any survey on your website will be added into your Triple Whale dashboard at the same time.

**What is sent**

Every answered question is sent to Triple Whale as its own post-purchase survey record, from every survey on the account.

Triple Whale matches each record to an order, so a response is only sent when it is tied to a Shopify order: surveys shown on the checkout, thank you and order status pages, and surveys Zigpoll emails after an order, which carry the order they were sent for. A response with no order, such as a survey link you share yourself, is not sent.

To send only some of your surveys, pick them under **Surveys to send** on the Triple Whale integration and save. With none picked, every survey is sent.

Each record carries the question (`question_id` is the question's handle, `question_text` its title) and the answer exactly as the customer gave it, in the language of your survey.

**Attribution (Total Impact)**

When a survey has an attribution question ("How did you hear about us?"), Zigpoll marks that answer for Triple Whale's attribution models and marks the survey's other answers as not part of attribution:

* The attribution answer is sent with `include_in_attribution` set to `true`. Every other answer in the same response is sent with `false`.
* When the answer names a platform Triple Whale tracks, Zigpoll also sends Triple Whale's standardized `source`, so the answer is grouped with that channel instead of appearing as a separate one:

| Answer names          | `source`        |
| --------------------- | --------------- |
| Facebook or Instagram | `facebook-ads`  |
| Google                | `google-ads`    |
| Bing                  | `bing`          |
| TikTok                | `tiktok-ads`    |
| Pinterest             | `pinterest-ads` |
| Snapchat              | `snapchat-ads`  |
| Reddit                | `reddit`        |
| LinkedIn              | `linkedin`      |
| X / Twitter           | `twitter-ads`   |

Any other answer (a friend, a podcast, email, several channels picked at once) is sent without a `source`, and Triple Whale reads the channel from the answer text.

"Email" and "SMS" name a channel rather than a platform, and Triple Whale's ids are per tool (`klaviyo`, `mailchimp`, `attentive`, `postscript`...). Choose the tool you send with under **Email answers** and **SMS answers** on the Triple Whale integration, and those answers are sent with its id. Left on "Let Triple Whale decide", they are sent without a `source`.

There is no setting for this. Zigpoll finds the attribution question the same way it does for [reported attribution metadata](/embed/poll-metadata/special-variables.md#reported-attribution-metadata): a question counts when three or more of its fixed answer options read as distinct channels, in any language. An "Other" write-in and a follow-up question ("Which one?") are read too. If a response did not answer an attribution question, no flag is sent and Triple Whale decides from the question text.


---

# 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/triple-whale.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.