How to Add and Create Rules

Rules allow you to automatically assign or remove Meta Fields based on visitor attributes and behavior. By defining conditions and actions, you can automate visitor classification and ensure metadata remains accurate and up to date.

Creating a New Rule

Creating a New Rule

To create a new rule:

  1. Navigate to Meta Fields > Rules.
  2. Click Create Rule.
  3. Configure the rule settings, conditions, and actions.
  4. Click Create Rule to save and activate the rule.

Rule Settings

Rule Name

Enter a descriptive name that clearly identifies the purpose of the rule.

Examples:

  • Outdoor Interest Visitors
  • Pricing Page Visitors
  • High-Value Customers

Enabled

Use the Enabled toggle to control whether the rule is active.

  • Enabled – The rule is evaluated during processing.
  • Disabled – The rule is saved but will not be applied.

Configuring Conditions

Conditions determine when a rule should be triggered.

Each condition consists of:

  • A field to evaluate (such as URL, referrer, or other supported attributes)
  • An operator (such as contains, equals, starts with, etc.)
  • A value to compare against

Example

Field Operator Value
URL contains /pricing

This condition matches visitors who have viewed a URL containing /pricing .

Logical Operators

Rules support logical operators to combine multiple conditions.

OR

The rule is triggered when any condition is true.

Example:

  • URL contains /pricing
  • URL contains /plans

The rule applies if either condition is met.

AND

The rule is triggered only when all conditions are true.

Example:

  • URL contains /pricing
  • Country equals United States

The rule applies only when both conditions are satisfied.

Using NOT

Enable the NOT option to invert a condition.

Example:

  • NOT URL contains /blog

This condition matches visitors who have not visited a URL containing /blog .

Creating Condition Groups

Click Group to create nested condition groups.

Groups allow you to build more advanced logic such as:

(URL contains "/pricing" OR URL contains "/plans")
AND
(Country equals "United States")

This structure provides greater flexibility when creating complex audience rules.


Configuring Meta Field Actions

Actions determine what happens when rule conditions are met.

Action Type

Select the action to perform.

Common action types include:

  • Add – Assign selected Meta Fields to matching visitors.
  • Remove – Remove selected Meta Fields from matching visitors.

Select Meta Fields

Choose one or more Meta Fields that will be affected by the rule.

Example:

Action Type: Add

Meta Field: Pricing Interest

When the rule conditions are met, the Pricing Interest Meta Field is automatically assigned.


Adding Notes

Use the Note section to document the rule's purpose, ownership, or special considerations.

Example:

Assigns the Pricing Interest Meta Field to visitors who view pricing-related pages.
Maintained by the Marketing Operations team.

Notes help administrators understand and maintain rules over time.


Example Rule

Goal

Assign the "Pricing Interest" Meta Field to visitors who view pricing-related content.

Configuration

Rule Name

Pricing Page Visitors

Conditions

  • URL contains /pricing
  • OR URL contains /plans

Action

  • Action Type: Add
  • Meta Field: Pricing Interest

Status

  • Enabled

When visitors access either pricing-related page, the Pricing Interest Meta Field is automatically assigned.


Best Practices

  • Use clear and descriptive rule names.
  • Keep rule logic as simple as possible.
  • Add notes to explain business purpose and ownership.
  • Test rule conditions before enabling them in production.
  • Regularly review and remove outdated rules.
  • Use groups for complex logic instead of creating multiple overlapping rules.

Properly configured rules help automate visitor classification, improve audience segmentation, and ensure Meta Fields remain accurate and actionable across your organization.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.