Related Data

Overview

The Related Data criteria allow you to filter and target audiences based on data stored in your Related Data or eCommerce tables. These criteria can be configured to check:

• Whether a specific value exists within the related data.

• The number of records in a related dataset associated with a particular user.

You can apply Related Data criteria across various areas of Mapp Engage, including:

• Email personalization – to tailor content based on user-specific data.

• Whiteboard campaigns – for automated and dynamic segmentation.

• Other engagement strategies where user-related data plays a role.

Navigation Path

1. Navigate to Audience​ > ​Segmentation > Segmentation Builder

2. Create a new segment.

3. Select the required criteria from the Related Data section:
   

Available Segmentation Criteria

1 Related Data Condition

With the ​Related Data Condition, you can create simple queries to related data sets. This criterion creates segments based on the values in the related data attributes for the contact. The logic of the segment criteria depends on the type of data stored in the attribute. The system offers different operators for different types of data.

Note: By default, only the first 200 characters will be read and used per contact to include them in this segment. So, if the related data entry is 400 characters long, only the first half may be used to add the contact to segments. If you would like to customize this limit, please contact us.

1.1 Using values from the same row of the dataset

For conditions based on multiple values in the same row of the dataset, all the criteria must be defined in the same ​Related Data Condition. To define these criteria, use the ​Add Filter option.

Example 1

Delete contacts who have purchased a product on a certain date. The implicit logical operator here is always AND. For conditions based on multiple values that can be in different rows, define each criterion as a separate ​Related Data Condition.

Example 2

Select contacts who purchased a certain product type AND made any purchase on a certain date. The two criteria can be true in the same row or two different rows. In this example, OR logic can be used instead.

1.2 Using Joined Data Views vs AND Operator

Please find more information about this use case here: Using Joined Data Views vs AND Operator.

2 Transaction

The ​Transactions criterion uses the System Transactions eCommerce table.

3 Abandoned Cart

Selects contacts with certain products and/or product value in their cart and uses the Abandoned Cart eCommerce table.

4 Abandoned Browse

Identifies contacts for whom the Abandoned Browse eCommerce table contains the specified product data. Please note that entries in the Abandoned Browse eCommerce table that contain products added for a user more than 30 days ago are automatically deleted.

5 Wishlist

Selects contacts with certain products and/or product values on their wishlist and uses the Wishlist eCommerce table.

Configuration

1 Data View

This selection only applies to the Related Data Condition criterion. It allows you to select a related data view from a drop-down list. The view will be available for selection once created in the Related Data area. For more information, see this how-to article: Create Data Views for Cross-table Related Data Queries.

2 Value filter and Number of Occurrences

In this section, you can select a column from the Related Data Set or eCommerce table.

Once you select the column, options to select the operator and enter the value will appear. For all eCommerce tables (Transactions, Abandoned Cart, Abandoned Browse, and Wishlist), the columns are predefined and to be selected from a drop-down list.

You can add up to ten filters to data columns by clicking the Add Filter button.

2.1 Configure the value filter

1. Select the Column. The following columns are predefined:

   • For Transactions: orderID, productSKU, productName, productPrice, productQuantity, returnedQuantity, imageURL, productURL, category, brand, variant, storeID, currency, discountValue, purchaseSource, discountPercentage

   • For Abandoned Cart, Abandoned Browse and Wishlist: productSKU, productPrice

2. Choose Operator:

   • Equals / Does not equal

   • Contains / Does not contain

   • Starts with / Does not start with

   • Ensd with / Does not end with

   • Is empty / Is not empty

3. Enter Value

4. Include Empty Values: Select Yes / No. Note: this option must be defined for all operators except Is empty / Is not empty. The default value is Yes.

2.1 Configure the number of occurrences

This section defines the number of occurrences and adds contacts outside the data set. Three operators specify how the search conditions should be applied, and all these operators specify the number of occurrences the engine should search for.

1. Choose Operator:

   • Equals: selects the exact amount of occurrences found in the Data Set.

     • If zero is selected, the contacts in this dataset with no such records will be returned.

     • If selected, you get the option to Include contacts out of dataset (see point 3 below).

   • Is greater than: selects more records than the specified value

   • Is less than: selects fewer records than the specified value.

     • You can enter any value from 2 to 999.

     • If selected, you get the option to Include contacts out of dataset (see point 3 below).

2. Enter Value

3. This option is set to No by default. If you select Yes, contacts from the selected dataset with no data stored in it will also be included.

   Example:

   We want to create a segment with all contacts not interested in T-shirts. The following data is available:

   Contact	Interest
   Donald	T-Shirts
   John	Pants
   Amy	Bags
   Christina	no data is available

   • Result if No is selected: John, Amy

   • Result if Yes is selected: John, Amy, Christina

3 In Timeframe

This option is available for the Transaction, Abandoned Cart, Abandoned Browse and Wishlist criteria. It’s unavailable for the Related Data Condition.

3.1 Configure the timeframe

1. Select Date Type:

   • Specific Date

   • Specific Date Range

   • Relative Date

   • Relative Date Range

2. Define the option Relative to Run Date:

   • Before

   • On run

   • After

3. (optional) Check the Ignore year checkbox if you want the configuration to apply to each year. If left unchecked (default), it will apply to the current year only.

For more information about the time frame definitions in Mapp Engage, see Date Picker in Mapp Engage.