Meta Ads Filters

The Meta Ads connector supports filtering data at the API request level. Filters let you narrow the selection down to specific campaigns, ad sets, ads, or metric values.

Types of Filters

Campaign Filter (campaign_filter)

Filtering by campaign name or ID.

Supported operators:

• EQUAL — exact match
• NOT_EQUAL — not equal
• CONTAIN — contains substring
• NOT_CONTAIN — does not contain substring

Logic: AND, OR

Entity: campaign

Examples:

• Campaign name contains "Black Friday" → campaign.name CONTAIN "Black Friday"
• Exclude the campaign with ID 123456 → campaign.id NOT_EQUAL "123456"

Ad Set Filter (adset_filter)

Filtering by ad set name or ID.

Supported operators:

• EQUAL — exact match
• NOT_EQUAL — not equal
• CONTAIN — contains substring
• NOT_CONTAIN — does not contain substring

Logic: AND, OR

Entity: adset

Ad Filter (ad_filter)

Filtering by ad name or ID.

Supported operators:

• EQUAL — exact match
• NOT_EQUAL — not equal
• CONTAIN — contains substring
• NOT_CONTAIN — does not contain substring

Logic: AND, OR

Entity: ad

Metric Filter (metric_filter)

Filtering by numeric metric values.

Supported operators:

• EQUAL — equal
• NOT_EQUAL — not equal
• GREATER_THAN — greater than
• LESS_THAN — less than

Logic: AND, OR

Entity: insights

Examples:

• Spend greater than 100 → spend GREATER_THAN 100
• CTR less than 1% → ctr LESS_THAN 1
• Impressions greater than 1000 and clicks greater than 50 → impressions GREATER_THAN 1000 AND clicks GREATER_THAN 50

Logical Operators

Filters can be combined using logical operators:

AND

Both conditions must be true at the same time.

campaign.name CONTAIN "Sale" AND spend GREATER_THAN 50

OR

At least one condition must be true.

campaign.name CONTAIN "Spring" OR campaign.name CONTAIN "Summer"

Operator Precedence

When combining AND and OR in a single filter:

• AND has higher precedence than OR
• Use grouping to explicitly control precedence

Applying Filters

Filters are applied at the Graph API request level, which means:

1. Filtering before aggregation: data is filtered on Meta's side before being passed to LightLead
2. Traffic savings: reduces the volume of data transferred
3. Faster requests: less data = faster response

Limitations

• Filters on creative fields (thumbnail_url, body, link, video_id) are not supported at the API level
• Text filters are case-insensitive
• The maximum number of conditions in a single request is limited by the Graph API's constraints

Related Pages

• Entities and Fields
• Metrics
• Request Parameters
• Usage Examples