How do trigger rules work?

Trigger rules monitor verification traffic for an integration and automatically switch the verification mode when a threshold is crossed. Use them to escalate to stricter checking under suspicious traffic, and optionally revert automatically when traffic normalizes.

How it works:

Each rule watches a specific event type within a rolling time window. When the count of that event meets your condition, the integration switches to the mode you specified. All rules are evaluated on every verification call — the highest-priority matching mode always wins, so rule order does not matter.

Rule fields:

  • • Event — What to count: invalid (any failed verification, including disposable), disposable (disposable provider specifically), or valid (successful verifications)
  • • Operator — Comparison: >, >=, =, <=, or <
  • • Count — Threshold number (e.g. 5)
  • • Window — Rolling time window in seconds (e.g. 60)
  • • Switch to — The mode to activate: Fast Check (lowest priority — use to revert), Deep Verification, or Send to Verify (highest priority)

Priority — when multiple rules match:

All rules are checked on every call. If more than one matches simultaneously, the highest-priority mode takes effect:

Fast Check  <  Deep Verification  <  Send to Verify

A Send to Verify rule always overrides a Deep Verification rule when both conditions are met, regardless of which rule was created first.

Reverting to Fast Check:

Add a rule with Switch to: Fast Check and Event: valid to automatically revert when traffic normalizes. Because Fast Check has the lowest priority, it only takes effect when no escalation rule is also matching at the same time. For example, once 10 or more valid emails arrive within 60 seconds and no invalid threshold is being met, the integration reverts to Fast Check.

Example — escalation with automatic revert:

The following three rules work together. Rule order does not matter — the highest-priority matching mode always wins.

Event: invalid  |  > 10  |  in 3600s  |  Switch to: Deep Verification
Event: invalid  |  > 30  |  in 3600s  |  Switch to: Send to Verify
Event: valid    |  > 10  |  in 60s    |  Switch to: Fast Check

Over 10 invalids in the past hour → Deep Verification. Over 30 invalids → Send to Verify (higher priority wins). Once over 10 valid emails arrive within 60 seconds and neither invalid rule is firing, the integration reverts to Fast Check.

How evaluation works:

  • • Every verification call evaluates all trigger rules for the integration.
  • • If multiple rules match, the highest-priority mode wins: Fast Check → Deep Verification → Send to Verify.
  • • A mode change takes effect from the next verification request. The current request completes using the mode that was active when it started.
  • • If the integration is already in the target mode, no update is made.