Traffic rules (allow / block)

Whitelist or block leads by field or email domain, before routing.

Traffic rules filter leads at ingest, the moment the flow and campaign are known — before the Mask score and before routing. They're the simple, explicit allow/block layer that sits alongside the Mask's risk scoring and Custom Rules.

Scope

Every rule is attached to a scope: global (all traffic), a single flow, or a single campaign. More specific scopes stack on top of global ones.

Kind & action

• Kind = field (any lead field, e.g. country, or a free param) or email_domain.
• Action = block — a matching lead is rejected on the spot, with the rule named as the reason.
• Action = allow — behaves as a whitelist per kind: if any allow rule of a kind exists, a lead must match one of them, or it's blocked as “not in allowlist”. With no allow rule of a kind, that kind imposes no whitelist.

Example

The predicate lives in the rule's config — for instance, allow only tier-1 geos on a flow:

Rules evaluate in order (by position). Caps and working hours aren't traffic rules — they live on route recipients (see “Caps, holds & quality”).