Administration and Configuration
What to know
Administration covers setup and governance. Understand user roles and permissions (Approver, Editor, Observer, and product admin), workspaces and property tokens, implementation (at.js vs. Web SDK, global mbox, mbox parameters), hosts/groups, activity approval workflows, and audit/change history. Know enterprise settings such as default reporting source, Adobe Experience Cloud integration, and data governance/privacy considerations.
Traps in questions
- Confusing workspaces (organizational separation of activities/audiences) with properties/property tokens (implementation separation).
- Assuming any user can approve activities - approval requires the Approver role and may be gated by workflow settings.
- Overlooking privacy/consent settings that block data collection or personalization.
- Forgetting that implementation choice (at.js vs. Web SDK) affects available features and data flow.
Worked example / rule of thumb
A team wants to isolate activities for two brands and control who can edit each. Use workspaces for organizational separation and assign role-based permissions; use property tokens to separate implementation data flow. Rule of thumb: workspaces = people and activities; properties = implementation and data. Confirm approval workflow and privacy settings before launch to avoid blocked or unapproved activities.