Adobe Audience Manager Business Practitioner Expert: Signals, Traits, and Rules-Based Trait Creation

Signals become traits

A signal is a key-value pair captured from a page or call (e.g., c_page=checkout). Signals are unclassified until a trait rule maps them to a trait. Trait rules use expressions with operators like equals, contains, starts with, and logical AND/OR/NOT. Rule-based traits are the workhorse; onboarded traits come from batch files; algorithmic traits use look-alike modeling.

Trait types and settings

Know rule-based, onboarded, and algorithmic traits, plus folder organization. Key trait settings: trait type (device vs cross-device), data source binding, event-based vs non-event, and recency/frequency implications. Trait population and unique trait count differ. Trait storage limits apply.

Common traps

• Operator precedence: AND binds tighter than OR; parentheses change meaning. A question may show a rule that looks right but groups differently.
• Case sensitivity and whitespace in equals vs contains.
• Confusing a signal (raw) with a trait (qualified).
• Assuming an unused signal is broken; it may simply be unclassified.

Worked example

Rule: c_page equals checkout AND c_cart contains shoes OR c_cart contains boots. Because AND evaluates before OR, this qualifies anyone with boots regardless of page. To require checkout for both, write c_page equals checkout AND (c_cart contains shoes OR c_cart contains boots). Rule of thumb: when a rule mixes AND and OR, parenthesize the intent and verify against the Trait Detail population trend.