Configure, Administer, and Maintain Target
Account structure and permissions
Target administration rests on properties (workspace-like divisions of users, activities, audiences, and offers) and user roles (Approver, Editor, Observer, and product-admin capabilities). Enterprise permissions let you restrict who can create, approve, or edit within a property. Exam questions often hinge on the difference between a user who can edit an activity and one who can approve it - an Editor cannot activate a pending approval without approval rights.
The at.js implementation
Know the anatomy of the library: the at.js file, the targetGlobalSettings configuration, and the adobe.target.getOffer / applyOffer flow that fetches and renders content. Response tokens expose mbox parameters and profile attributes for analytics integrations. The mboxDefault fallback content prevents blank flashes if Target is unavailable. A recurring trap is confusing mbox parameters (session-scoped, passed per request) with profile attributes (persistent, stored on the visitor profile).
Audiences, offers, and the asset library
Audiences combine rules on geo, device, browser, traffic source, profile attributes, and custom parameters. Understand how to build a custom audience from a profile script versus a rule-based audience. Offers live in the offer library and can be HTML, JSON, or redirect offers; reusable offers reduce maintenance.
Maintenance and governance
Activities expire, offers get stale, and integrations break. Regular audits include checking activity end dates, reviewing unused audiences and offers, and validating that the Adobe Experience Platform / Analytics integration still maps response tokens correctly.
Worked rule of thumb
Before debugging content, confirm the visitor qualifies for the audience and the activity is active and within schedule - most "content not showing" tickets resolve there.