--- title: "Related Data Criteria" slug: "related-data" updated: 2025-12-12T16:19:12Z published: 2025-12-12T16:19:12Z canonical: "docs.mapp.com/related-data" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.mapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Related Data Criteria Related Data criteria allow you to filter and target contacts based on data stored in **Related Data** or **eCommerce** tables. These criteria are typically used to: - check whether specific values exist in related datasets - evaluate how many related records are linked to a contact Related Data criteria can be used across Mapp Engage, for example in message personalization and Whiteboard campaigns. --- ## Related Data Condition Allows you to build conditions based on values stored in a Related Data dataset. This criterion evaluates attributes stored in a selected data view and applies operators based on the attribute’s data type. ### Settings | **Setting** | **Description** | | --- | --- | | Data View | Select a Related Data view | | Value Filter | Filter based on column values | | Number of Occurrences | Filter based on how often a condition occurs | ### More Details **Same row vs. different rows** - If multiple filters are added within a single Related Data Condition, all filters are evaluated against the same row in the dataset. Use this structure when all conditions must apply to one specific record. - If conditions may be fulfilled by different records in the dataset, configure each condition as a separate Related Data Condition. Each condition is evaluated independently, allowing different rows to satisfy different requirements. **Why this matters** - A single Related Data Condition always narrows down one record. - Multiple Related Data Conditions allow you to combine results from multiple records linked to the same contact. **Missing records in Related Data** - Segmentation can evaluate only related records that exist for a contact. - It is not possible to build conditions that target missing records across linked datasets. - Only existing joined records can be used in segmentation logic. **Additional notes** - By default, only the first 200 characters per contact are evaluated when using Related Data in segmentation. To adjust this limit, contact support. - Related Data views must be created in advance. See [Create Data Views for Cross-table Related Data Queries](/v1/docs/create-data-views-for-cross-table-related-data-queries). --- ## Transactions Uses the [System Transactions](/v1/docs/system-transactions) eCommerce table to segment contacts based on purchase-related data. This criterion evaluates transactional records linked to a contact, such as purchased products, order values, or quantities. ### Settings | **Setting** | **Description** | | --- | --- | | Value Filter | Filters based on attributes stored in the Transactions table | | Number of Occurrences | Defines how often a condition must occur | | In Timeframe | Restricts evaluation to a defined period | ### More Details - The Transactions criterion is based on the **system Transactions eCommerce table**. - Filters are evaluated against transactional records linked to a contact. - If multiple filters are defined within one Transactions criterion, they are evaluated against the **same transaction record**. - To allow conditions to be fulfilled by **different transactions**, configure multiple Transactions criteria. --- ## Abandoned Cart Selects contacts based on products or values stored in the [Abandoned Cart](/v1/docs/ecommerce-product-catalog) eCommerce table. This criterion is typically used to target contacts who added products to their cart but did not complete a purchase. ### Settings | **Setting** | **Description** | | --- | --- | | Value Filter | Filters based on cart product attributes | | Number of Occurrences | Defines how often a condition must occur | | In Timeframe | Restricts evaluation to a defined period | ### More Details - The Abandoned Cart criterion evaluates cart records linked to a contact. - Only existing cart records can be evaluated in segmentation. --- ## Abandoned Browse Identifies contacts based on product data stored in the [Abandoned Browse](/v1/docs/abandoned-browse) eCommerce table. This criterion is used to target contacts who viewed products but did not add them to the cart. ### Settings | **Setting** | **Description** | | --- | --- | | Value Filter | Filters based on browsed product attributes | | Number of Occurrences | Defines how often a condition must occur | | In Timeframe | Restricts evaluation to a defined period | ### More Details - Entries in the Abandoned Browse eCommerce table are automatically deleted after **30 days**. - Only existing browse records can be evaluated in segmentation. --- ## Wishlist Selects contacts based on products or values stored in the [Wishlist](/v1/docs/ecommerce-product-catalog) eCommerce table. This criterion allows you to target contacts based on items they explicitly saved for later. ### Settings | **Setting** | **Description** | | --- | --- | | Value Filter | Filters based on wishlist product attributes | | Number of Occurrences | Defines how often a condition must occur | | In Timeframe | Restricts evaluation to a defined period | ### More Details - Wishlist entries represent products explicitly saved by the contact. - Only existing wishlist records can be evaluated in segmentation. ## Related - [How-To](/segmentation-builder-how-tos.md)