Filter Data applies conditions to your dataset and returns only the rows that match your criteria. Essential for extracting specific data subsets, analyzing targeted segments, or preparing focused datasets for further processing.


When to Use It

  • Filter high-performing products based on sales metrics
  • Extract data for specific date ranges or regions
  • Find records that meet multiple criteria simultaneously
  • Clean datasets by removing unwanted or irrelevant rows

Inputs

FieldTypeRequiredDescription
Data to FilterDataYesThe dataset you want to filter (from previous steps)
ConditionsConditionsYesFilter criteria based on column values and conditions

Outputs

OutputDescription
Filtered DataDataset containing only rows that meet your conditions

Credit Cost

Free to use - no credits required.


How It Works

Filter Data examines each row in your dataset and applies your conditions. Only rows that meet ALL your conditions are included in the filtered output (AND logic between multiple conditions).

Example:

Original Data:

campaign_namestatuscostclicks
Summer SaleActive1501200
Winter PromoPaused80500
Black FridayActive3002500
Test CampaignActive20100

Filter Conditions:

  • status equals “Active”
  • cost greater than 100

Filtered Result:

campaign_namestatuscostclicks
Summer SaleActive1501200
Black FridayActive3002500

Available Filter Conditions

ConditionDescriptionExample Use Case
EQUALSExact matchStatus equals “Active”
NOT_EQUALSDoes not match exactlyStatus not equals “Paused”
CONTAINSContains the textCampaign Name contains “Sale”
DOES_NOT_CONTAINDoes not contain the textCampaign Name does not contain “Test”
STARTS_WITHBegins with the textCampaign Name starts with “2024”
ENDS_WITHEnds with the textCampaign Name ends with “Mobile”
GREATER_THANNumeric comparisonCost greater than 100
LESS_THANNumeric comparisonClicks less than 1000
GREATER_THAN_OR_EQUALNumeric comparisonBudget greater than or equal to 500
LESS_THAN_OR_EQUALNumeric comparisonCost less than or equal to 200
REGEXP_MATCHRegular expression matchCampaign Name matches pattern
NOT_REGEXP_MATCHDoes not match regexCampaign Name does not match pattern
IN_LISTValue is in a listStatus in “Active,Enabled,Running”
NOT_IN_LISTValue is not in a listStatus not in “Deleted,Removed”
IS_NULLField is emptyNotes is null
IS_NOT_NULLField has any valueNotes is not null

Filter Examples

Example 1: Active High-Budget Campaigns

Conditions:

  • Field: “status” | Condition: “EQUALS” | Value: “Active”
  • Field: “budget” | Condition: “GREATER_THAN” | Value: “1000”

Result: Only active campaigns with budget over $1000

Example 2: Performance Analysis

Conditions:

  • Field: “clicks” | Condition: “GREATER_THAN” | Value: “500”
  • Field: “cost_per_click” | Condition: “LESS_THAN” | Value: “2.00”

Result: High-click campaigns with low cost per click

Example 3: Campaign Name Filtering

Conditions:

  • Field: “campaign_name” | Condition: “CONTAINS” | Value: “2024”
  • Field: “campaign_name” | Condition: “DOES_NOT_CONTAIN” | Value: “Test”

Result: 2024 campaigns excluding test campaigns

Example 4: Multi-Status Filtering

Conditions:

  • Field: “status” | Condition: “IN_LIST” | Value: “Active,Enabled,Running”

Result: Campaigns with any of the specified active statuses


Tips

Field Names:

  • Use exact column names from your data (case-sensitive)
  • Check your data structure first to confirm field names
  • Column names should match exactly what appears in your dataset headers

Condition Logic:

  • All conditions must be met (AND logic) for a row to be included
  • Use multiple Filter Data nodes for OR logic between different condition sets
  • Test with a small dataset first to verify your conditions work as expected

Data Types:

  • Use numeric comparisons (GREATER_THAN, LESS_THAN) for numbers
  • Use text comparisons (CONTAINS, EQUALS) for text fields
  • Date comparisons work with properly formatted date fields

Performance:

  • Filter early in your workflow to reduce data size for subsequent nodes
  • Use specific conditions to avoid processing unnecessary data
  • Consider the order of conditions - put most selective conditions first

FAQ