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

How do survey responses break down by survey platform? — group by survey_type

What feedback patterns appear for specific question types? — group by question_type, answer

Before You Query

Required field: event_date

Key Relationships
Table Join Key What the Join Enables
Orders order_id Full order details for the associated purchase (revenue, products, fulfillment)

When to Use a Different Table

Need system-attributed marketing sources per order (tracked via the Triple Whale Pixel with ad platform metadata enrichment, not self-reported) → Pixel Orders table. PPS captures what customers say brought them; Pixel Orders captures which ads were actually clicked.

View the full Triple Whale Data Ontology →

Table	Join Key	What the Join Enables
Orders	`order_id`	Full order details for the associated purchase (revenue, products, fulfillment)

Dimensions

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

Title	ID	Type	Description
Event Hour	`event_hour`	string	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`
Event Date	`event_date`	date	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).
Event Day	`event_date.day`	date	The day the event occurred. Derived from `event_date`.
Event Week	`event_date.week`	date	The Sunday of the week during which the event occurred. Derived from `event_date`.
Event Month	`event_date.month`	date	The month during which the event occurred. Derived from `event_date`.
Event Quarter	`event_date.quarter`	date	The first month of the quarter during which the event occurred. Derived from `event_date`.
Event Year	`event_date.year`	date	The year during which the event occurred. Derived from `event_date`.
Answer	`answer`	string	The response provided by the customer to the survey question. Example values: `Online search`, `Social media`, `From a friend`
Customer Email	`customer_email`	string	The customer’s email address. Example value: `[email protected]`
Customer ID	`customer_id`	string	The unique customer ID. Assigned by the main shop platform. Example value: `5209503793328`
Customer Phone	`customer_phone`	string	The customer's phone number. Example value: `18005550199`
Order ID	`order_id`	string	The unique order ID. Assigned by the main shop platform. Example value: `4930225799243`
Survey Question	`question`	string	The specific survey question asked to the customer. Example value: `How did you first hear about us?`
Question Type	`question_type`	string	The type of the question asked. Example values: `standard`, `custom`
Shop ID	`shop_id`	string	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`
Shop Name	`shop_name`	string	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`
Source	`source`	string	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
Survey Type (Platform)	`survey_type`	string	The post-purchase survey platform used. Example values: `KNO`, `TW-survey`, `FAIRING`

Updated 3 days ago