Data Model and Schema Management
What you must understand
Adobe Campaign Classic's data model is defined by schemas (XML) that generate SQL tables. Candidates must know the recipient schema (nms:recipient) as the default target, how to extend it, and the role of the target mapping that links a schema to delivery targeting. Understand enumerations, links (1-1, 1-N, N-N with a link table), keys and indexes, and the namespace convention.
Traps that appear in questions
- Extending vs. replacing. Extending the recipient schema adds fields; replacing it changes the target and breaks existing deliveries and reports. Questions often imply "add a field" but describe "new target."
- Schema vs. table. Editing a schema does not always regenerate the table immediately; a database update wizard step is required.
- Link direction. A 1-N link on the recipient does not automatically give you a reverse join in queries; you must navigate the link.
- Enumeration storage. Enum values are stored as internal codes, not labels - reports and exports may show codes.
Rule of thumb
Any structural change follows: edit schema → update database structure → verify indexes → test a query. Skipping the database update is the most common exam trap.
Worked example
You add a custom loyaltyTier enumeration to the recipient. After saving the schema, you must run the database structure update so the column exists, then confirm the enumeration's internal values map to the labels your personalization expects.