The filter builder lets you build audiences from data in your warehouse using the same dropdown filters you use for regular MoEngage segments. You pick attributes and events from a list rather than writing a SQL query, so you do not need to involve your analytics team to create or change a segment. MoEngage builds the SQL for you and runs it against your warehouse. Your data stays where it is. This is one of two ways to build a warehouse segment. For a comparison with the SQL method, refer to Warehouse Segments - Overview.

​

Build a Segment

Building an audience and acting on it are two separate steps. You define filters and run them to get a count, and the result lands in Query results, where you turn it into a segment, a campaign, or an export. To build a warehouse segment, perform the following steps:

1. On the sidebar menu in MoEngage, click Segment > Warehouse Segments. The Warehouse Segments page appears.
2. Select your warehouse connection from the dropdown beside the page title. The attributes and events mapped from that connection load into the filter dropdowns.
3. Select the Filter tab.
4. Build your audience in the filter block. Each block filters on either a User property or a User behavior. Use the toggle to switch between them.
   • To narrow the same block further, click + Nested Filter.
   • To add a separate condition, click + Filter.
   • To remove everyone matching a condition instead of including them, select Exclude Users.
   • To start over, click Reset Filters.
5. Click Show count. MoEngage builds the SQL, runs it against your warehouse, and adds a row to Query results below.
6. In Query results, click the ellipsis icon on the row and select what to do with the audience. For more information, refer to Act on the Result.

​

Filter on User Properties

Select User property in a filter block to filter on the properties mapped from your user master table. Each row reads as attribute, operator, then value. The value dropdown lets you compare the attribute against a Constant value you type, or against another attribute. Only properties your data team mapped appear here, under the display names they gave them. Columns that were skipped during mapping are not available. If a property you expect is missing, ask your data team to map it in Warehouse Schema.

​

Filter on User Behavior

Select User behavior in a filter block to filter on what users did. Choose Has Executed or Has Not Executed, select the event, then set how many times and over what period. Two links appear under the filter:

• + Attributes narrows the filter to specific event attribute values, such as an order above a certain amount.
• + Aggregation filters on a computed value across the matching events rather than on a count of them.

Only events and attributes your data team mapped appear here. The event names are the display names set on each event schema.

​

Event Occurrence Operators

Set how many times a user performed the event:

​

Operators by Data Type

Available operators depend on the MoEngage data type your team mapped the column to. You can also compare one attribute against another, and use special date filters, as you can in rule-based segments. For more information, refer to Filters in Segmentation.

​

Read the Query Results

Every time you click Show count, MoEngage adds a row to Query results. Each row records what you ran and what it returned. Click the refresh icon to re-run a query without rebuilding the filters.

​

Act on the Result

Click the ellipsis icon on a query result row to choose what to do with the audience.

​

When Queries Run

MoEngage queries your warehouse at three points: when you click Show count, when you re-run a query result or a saved custom segment, and automatically at campaign run time for any campaign using a segment built this way.

​

After You Create a Custom Segment

A custom segment created from a query result behaves like any other custom segment on the All Segments page, where it appears with the type Warehouse - filter. To show only these segments, select that type in the Select Segment Type list. You can view, edit, duplicate, archive, and create a campaign from the segment. For more information, refer to Manage Segments. The segment detail page shows its type, source connection, creation date, last run time, user count, reachability, and edit history. Running the segment from this page refreshes the user count by re-querying your warehouse. Exports return MoEngage attributes. MoEngage cannot resolve warehouse attribute values during an export, so warehouse columns are not included.

​

Limitations

The filter builder does not support:

• All Users segments. Every warehouse segment needs at least one filter.
• Value suggestions. Attribute value dropdowns stay empty, so type values manually.
• Analyse. A warehouse segment cannot be used as the audience for an analysis.
• Custom segment, affinity, and analytics filters inside a warehouse segment.

​

Unsupported Attribute Types

Attributes of these types cannot be filtered on, because they are not mappable in a warehouse schema:

• Object and object array attributes.
• Location attributes.
• Boolean arrays and date arrays.

For the full list of what can and cannot be mapped, refer to Data Types.

​

Unsupported Aggregations

Aggregating on a warehouse attribute is not available yet. The following aggregations are not supported at all:

• Median.
• Change and percentage change.

​

One Connection per Query

A query reads from one warehouse connection. To combine data across connections, create a custom segment per connection and combine those on the standard segment builder.

​

When a Segment Breaks

A warehouse segment depends on the warehouse tables behind it staying as they were mapped. If a column is renamed, a table is dropped, or a data type changes, the segment stops working. If a segment stops returning a count, ask your data team to check the mapping in Warehouse Schema. Once it is corrected, run the segment again.

​

Frequently Asked Questions