Custom Conditions
Filter which events a Custom Webhook forwards using field-level rules.
Custom Conditions let you control exactly which events a Custom Webhook receives. Only events matching all your rules get forwarded.
Custom Conditions are available only on Custom Webhook destinations. Marketing and Analytics destinations auto-forward all standard events.
How rules work
Each rule: field name → operator → value. Multiple rules = AND logic. No rules = all toggled events forwarded.
Operators
| Operator | What it does | Example |
|---|---|---|
| equals | Exact match | currency equals USD |
| not equals | Excludes a value | name not equals page_view |
| contains | Substring match | url contains /checkout |
| regex | Regex match | email regex ^.*@company\.com$ |
| exists | Field present | order_id exists |
| not exists | Field absent | test_flag not exists |
For exists / not exists, the value field is ignored.
Adding rules
Open the Conditions tab (during setup or via ⚙️). Click + Add rule to add a row. Click 🗑️ to remove one. Rules are drag-reorderable.
Examples
- Forward only purchases:
name equals purchase - Restrict to Turkey:
country equals TR - Exclude test traffic:
test_mode not exists - Match checkout URLs:
url regex \/checkout\/(confirm|success)$
Things to know
- An event must be toggled on in the Events tab and pass all conditions to be forwarded.
- If Consent Mode is also on, the event must pass both checks.
- Field names are case-sensitive.
Was this page helpful?