Customer Segmentation Table
The Customer Segmentation table lists which customers belong to each segment at any point in time. One row per customer per segment instance. Learn more about customer segmentation.
Table GuideWhat You Can Answer With This Table
- Which customers are in a specific segment? — filter by
segment_id- How has segment membership changed over time? — compare customer counts across
instance_event_date, optionally group bysegment_byBefore You Query
- A segment is a group of customers matching defined rules. A segment instance is a snapshot of that segment at a point in time (generated daily or every other day).
- To match results with the Customer Segments UI, filter for the most recent segment instance per segment. Without this, queries include all historical instances and totals will appear inflated.
- The join key is
customer_identity. Depending onsegment_by, this contains either an email address or a customer ID. When joining to other tables, match against the corresponding field (e.g.,customer_idon the Orders table, oremail_addresson the Customers table).Key Relationships
Table Join Key Use This Join To Customers customer_identitytocustomer_idoremail_addressUnderstand who is in each segment using profile attributes Orders customer_identitytocustomer_idorcustomer_emailCompare what segment members bought and spent Pixel Orders customer_identitytocustomer_idorcustomer_emailAnalyze which channels or campaigns drove segment members' orders Customer Segmentation Analytics segment_id+instance_event_dateCompare segment performance around a pinned_event_dateusing pre-aggregated metricsWhen to Use a Different Table
- Use Customer Segmentation Analytics table when you need segment performance metrics such as revenue, AOV, or purchase frequency. The Customer Segmentation table is for segment membership.
- Use Customers table when you need customer profiles without segment context. The Customer Segmentation table is for segment membership.
Dimensions
Dimensions are immutable properties that can be used for grouping data.
| Title | ID | Type | Description |
|---|---|---|---|
| Customer Identity | customer_identity | string | The identity of the customer in the segment. Can be either Example values: |
| Instance Created Date | instance_created_date | date | The timestamp when the segment instance (run/snapshot) was generated. Example value: |
| Schedule | schedule | string | The recurring schedule for running the segment. Example values: |
| Segment By | segment_by | string | The audience type used to group customers in the segment. Example value: |
| Segment Created Date | segment_created_date | date | The date when the segment was originally created. Example value: |
| Segment ID | segment_id | string | The unique identifier for a segment. Example value: |
| Segment Instance ID | segment_instance_id | string | The unique identifier for a specific segment instance (run/snapshot). Example value: |
| Segment Name | segment_name | string | The human-readable name of the segment, Example values: |
| 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: |
| 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: |
Measures
Measures are numeric fields that can be aggregated and/or combined to calculate new metrics.
| Title | ID | Type | Description |
|---|---|---|---|
| Number of Customers | num_of_customers | numeric | The total number of unique customers included in the segment instance. |
| Number of Orders | num_of_orders | numeric | The total number of orders placed by customers in the segment during the relevant time window. |
| Total Revenue | total_revenue | numeric | The total revenue generated by customers in the segment during the relevant time window. |
Updated 6 days ago