Administration, Governance, QA, and Troubleshooting
Administration covers users, roles, properties/workspaces, and activity governance. Understand product profiles (admin, editor, approver, observer), the approval workflow, and how properties/workspaces isolate teams and assets. Know the QA workflow: QA mode, preview links, and the Adobe Experience Cloud Debugger / Experience Platform Debugger to inspect Target requests and responses.
Troubleshooting patterns: no experience served (audience mismatch, activity not approved, mbox not firing), flicker (pre-hiding misconfigured), wrong experience (collision with another activity or audience overlap), reporting gaps (A4T misconfiguration, tracking server wrong), and profile issues (wrong identity key).
Traps: assuming preview links bypass all targeting (they bypass some but not all); forgetting that an activity must be approved and activated; confusing property/workspace scoping with audience targeting; overlooking that QA mode changes reporting behavior.
Rule of thumb: troubleshoot in order - is the mbox/scope firing? is the activity active and approved? does the visitor match the audience? is the offer rendering? Use the debugger at each step.
Worked example: a test shows zero traffic. Check: mbox fires in debugger (yes), activity status (approved, active), audience (visitor not matching geo rule), fix audience, and traffic resumes.