| Audience | Platform admins and marketers |
| Prerequisites |
|
Configure settings that apply across AI Decisioning, to individual agents, and to individual messages.
Overview
AI Decisioning settings are configured at three levels:
- Shared configuration applies across agents or provides resources that multiple agents can use. Go to AI Decisioning → Configuration to access it.
- Agent configuration controls how an individual agent evaluates users, optimizes, and sends messages. Open the agent's Configuration tab.
- Message configuration controls behavior specific to an individual message. Open the message's Configuration tab.
Use the most broadly applicable level for a rule. For example, configure an SMS opt-in rule at the channel level when it should apply to every agent using SMS, rather than recreating the rule for each agent.
Shared configuration
Go to AI Decisioning → Configuration to manage settings that apply across agents.
Control channel availability and eligibility
Use Channels to control which destinations agents can use and which users are eligible to receive messages through each channel.
Channel eligibility is useful for rules that should apply everywhere the channel is used, such as SMS opt-in or regional restrictions. A user must also satisfy any applicable agent- and message-level eligibility rules.

Set cross-agent scheduling rules
Use Scheduling for frequency limits and quiet hours that should apply across agents.
You can configure:
- Global frequency limits — Limit how often a user can receive messages across all agents.
- Channel frequency limits — Limit how often a user can receive messages through a specific channel.
- Quiet hours — Prevent messages during specific times, configured per channel and evaluated using each user's local time zone.
When multiple frequency limits apply, a send must satisfy all of them. Agent-specific scheduling restrictions are configured on the agent instead.

Resolve conflicts between agents
Use Agent prioritization when the same user can qualify for multiple agents during the same evaluation window.
Configure priorities and weights to determine which agent takes precedence. You can use simulated performance to evaluate the expected effect of prioritization changes before applying them.

Define data available to agents
Use Feature Matrix to define which warehouse attributes and behavioral data AI Decisioning can use for evaluation and analysis.
Feature matrices are shared resources, but each agent selects the feature matrix it uses. The matrix must match the agent's parent model. For more information, see User feature matrix.
Create a feature matrix
- Go to AI Decisioning → Configuration → Feature Matrix.
- Select + New feature matrix.
- Select the parent model.
- Enter a name.
- Select Create feature matrix.
- Select the columns AI Decisioning should use.

Configure send tracking
Configure send event tracking on a channel when you want AI Decisioning to match recommendations with delivery events from your warehouse.
Send event tracking is required for delivery-related reporting such as send success, send comparison, and channel send success.
To configure it:
- Go to AI Decisioning → Configuration → Channels.
- Select a channel.
- Under Send event tracking, select the event model that represents sends.
- Configure any additional matching or attribution settings needed for your data.

Without send event tracking, delivery-related Insights views can't report send status for that channel.
Agent configuration
Open an agent's Configuration tab for settings that apply only to that agent.
You select a parent model for each agent when you create it. Agents in the same decision engine must use parent models from the same data source. For more information, see Prepare data for AI Decisioning.
Control who the agent can evaluate
Configure the agent's target audience and eligibility conditions. Agent eligibility applies in addition to shared channel eligibility and any message-level eligibility.

Define goals and select data
Use Goals to define the outcomes the agent should optimize when selecting messages. Messages inherit these goals and can't change them independently.
Use Feature matrix to select which feature matrix the agent uses. The feature matrix must match the agent's parent model.
Control what data is sent downstream
By default, trigger sync payloads include all columns from the agent's parent model. Use Synced user columns to limit which parent-model fields are included. Use Additional user columns when you need to include properties from related models.

Set agent-specific delivery limits
Configure agent-level frequency limits, scheduling, and time zone behavior when the restrictions should apply only to this agent. Shared scheduling rules still apply.
- Time zone column — A parent-model field containing a UTC offset or IANA time zone.
- Fallback time zone — The time zone used when no user-level value is available. If left blank, the fallback is
America/Los_Angeles.

Use Smart suppression to reduce low-impact sends based on predicted user value.
For more details on agent settings, see Agents.
Message configuration
Open a message's Configuration tab for settings that apply only to one message.
Use message eligibility when a condition should apply to a particular message rather than the entire agent or channel. Use tags to categorize messages for learning and analysis, and collections when a message should include dynamically selected products or content.
Messages inherit goals from their parent agent. To change the goals a message contributes toward, update the agent.
For more details on message settings, see Messages.
What's next
-
Configure an AI Decisioning destination: