NS8 User Guides

NS8 Protect Operators

The conditional operators used within NS8 Protect for criteria and rules.

Conditional operators determine how a condition applies to a NS8 Protect criteria field. Every field will have only the operators that apply to that particular field. The operators available are listed below:

  • equal: The chosen field must equal the criteria specified. For fields that have Boolean (true/false) values, they will be limited to these criteria. For example, EQ8 Score must equal 200 will identify only orders with an EQ8 Score of exactly 200.
  • not equal: The chosen field must not equal the criteria specified. For example, "EQ8 Score must not equal 200" will identify orders with an EQ8 Score that is anything other than 200.
  • contains: The chosen field must contain the criteria specified. For example, "email address contains 'gmail'" will identify email addresses that contain the string "gmail."
  • doesn't contain: The chosen field must not contain the criteria specified. For example, email address doesn't contain 'gmail' will identify email addresses that do not contain the string "gmail."
  • begins with: The chosen field will begin with the criteria specified. For example, "email address begins with 'Joe'" will identify email addresses that begin with the the string "Joe."
  • not begins with: The chosen field will not begin with the criteria specified. For example, "email address not begins with 'Joe'" will identify email addresses that do not begin with the the string "Joe."
  • is set: The chosen field will not be blank or null. For example, "campaign is set" will identify only orders where the "campaign" field contains data.
  • is not set: The chosen field will be blank or null. For example, "campaign is not set" will identify only orders where the "campaign" field contains no data.

NS8 Protect Operators


The conditional operators used within NS8 Protect for criteria and rules.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.