---
updatedAt: 2026-09-16T11:05:32.000Z
agentTools:
  projectIndex: https://triplewhale.readme.io/llms.txt
---

# Post-Purchase Survey Table

post_purchase_survey_table

The Post-Purchase Survey table stores customer survey responses collected after purchase. One row per question-answer pair. Includes survey platform, question text, and self-reported sources.

> 📋 Table Guide
>
> **What You Can Answer With This Table**
>
> * What sources do customers most commonly cite for how they found you? — group by `answer` filtered to discovery questions
> * What response patterns appear by survey platform or question type? — group by `survey_type`, `question_type`, `answer`
>
> **Before You Query**
>
> * **Required field:** `event_date`
>
> **Key Relationships**
>
> | Table                                                     | Join Key   | Use This Join To                                                       |
> | :-------------------------------------------------------- | :--------- | :--------------------------------------------------------------------- |
> | [Orders](https://triplewhale.readme.io/docs/orders-table) | `order_id` | Analyze survey responses by purchase revenue, products, or fulfillment |
>
> <br />
>
> **When to Use a Different Table**
>
> * Use [Pixel Orders table](https://triplewhale.readme.io/docs/pixel-orders-table) when you need system-attributed marketing sources per order from Triple Whale Pixel tracking. The Post-Purchase Survey table is for self-reported survey responses.
>
> *[View the full Triple Whale Data Ontology →](https://triplewhale.readme.io/docs/triple-whale-data-ontology)*

***

# Dimensions

Dimensions are immutable properties that can be used for grouping data.

<Table align={["left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Title
      </th>

      <th>
        ID
      </th>

      <th>
        Type
      </th>

      <th>
        Description
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Event Hour
      </td>

      <td>
        `event_hour`
      </td>

      <td>
        string
      </td>

      <td>
        The hour of the day the post-purchase survey was submitted, according to a 24-hour clock. Based on the shop time zone at the moment of the event (or the user time zone, if no sales platform is connected).

        Example values: `07`, `16`, `21`
      </td>
    </tr>

    <tr>
      <td>
        Event Date
      </td>

      <td>
        `event_date`
      </td>

      <td>
        date
      </td>

      <td>
        The date the post-purchase survey was submitted. Based on the shop time zone at the moment of the event (or the user time zone, if no sales platform is connected).
      </td>
    </tr>

    <tr>
      <td>
        Event Day
      </td>

      <td>
        `event_date.day`
      </td>

      <td>
        date
      </td>

      <td>
        The day the event occurred. Derived from `event_date`.
      </td>
    </tr>

    <tr>
      <td>
        Event Week
      </td>

      <td>
        `event_date.week`
      </td>

      <td>
        date
      </td>

      <td>
        The Sunday of the week during which the event occurred. Derived from `event_date`.
      </td>
    </tr>

    <tr>
      <td>
        Event Month
      </td>

      <td>
        `event_date.month`
      </td>

      <td>
        date
      </td>

      <td>
        The month during which the event occurred. Derived from `event_date`.
      </td>
    </tr>

    <tr>
      <td>
        Event Quarter
      </td>

      <td>
        `event_date.quarter`
      </td>

      <td>
        date
      </td>

      <td>
        The first month of the quarter during which the event occurred. Derived from `event_date`.
      </td>
    </tr>

    <tr>
      <td>
        Event Year
      </td>

      <td>
        `event_date.year`
      </td>

      <td>
        date
      </td>

      <td>
        The year during which the event occurred. Derived from `event_date`.
      </td>
    </tr>

    <tr>
      <td>
        Answer
      </td>

      <td>
        `answer`
      </td>

      <td>
        string
      </td>

      <td>
        The response provided by the customer to the survey question.

        Example values: `Online search`, `Social media`, `From a friend`
      </td>
    </tr>

    <tr>
      <td>
        Customer Email
      </td>

      <td>
        `customer_email`
      </td>

      <td>
        string
      </td>

      <td>
        The customer’s email address.

        Example value: `customer@example.com`
      </td>
    </tr>

    <tr>
      <td>
        Customer ID
      </td>

      <td>
        `customer_id`
      </td>

      <td>
        string
      </td>

      <td>
        The unique customer ID. Assigned by the main shop platform.

        Example value: `5209503793328`
      </td>
    </tr>

    <tr>
      <td>
        Customer Phone
      </td>

      <td>
        `customer_phone`
      </td>

      <td>
        string
      </td>

      <td>
        The customer's phone number.

        Example value: `18005550199`
      </td>
    </tr>

    <tr>
      <td>
        Order ID
      </td>

      <td>
        `order_id`
      </td>

      <td>
        string
      </td>

      <td>
        The unique order ID. Assigned by the main shop platform.

        Example value: `4930225799243`
      </td>
    </tr>

    <tr>
      <td>
        Survey Question
      </td>

      <td>
        `question`
      </td>

      <td>
        string
      </td>

      <td>
        The specific survey question asked to the customer.

        Example value: `How did you first hear about us?`
      </td>
    </tr>

    <tr>
      <td>
        Question Type
      </td>

      <td>
        `question_type`
      </td>

      <td>
        string
      </td>

      <td>
        The type of the question asked.

        Example values: `standard`, `custom`
      </td>
    </tr>

    <tr>
      <td>
        Shop ID
      </td>

      <td>
        `shop_id`
      </td>

      <td>
        string
      </td>

      <td>
        The unique ID of the shop (often corresponds to the shop domain). Can be used to group or filter data by shop in multi-store reports.

        Example values: `example-US.myshopify.com`, `example-EU.myshopify.com`
      </td>
    </tr>

    <tr>
      <td>
        Shop Name
      </td>

      <td>
        `shop_name`
      </td>

      <td>
        string
      </td>

      <td>
        The name of the shop. Can be used to group or filter data by shop in multi-store reports.

        Example values: `example-US`, `example-EU`
      </td>
    </tr>

    <tr>
      <td>
        Source
      </td>

      <td>
        `source`
      </td>

      <td>
        string
      </td>

      <td>
        The traffic source or referral channel that directed the customer to the survey.

        Example values: `google-ads`, `facebook-ads`, `snapchat-ads`

        [See full list of standardized PPS source IDs](https://triplewhale.readme.io/docs/post-purchase-survey-pps-standardized-source-ids#/)
      </td>
    </tr>

    <tr>
      <td>
        Survey Type
      </td>

      <td>
        `survey_type`
      </td>

      <td>
        string
      </td>

      <td>
        The post-purchase survey provider.

        Example values: `KNO`, `FAIRING`
      </td>
    </tr>
  </tbody>
</Table>