Adobe Target Architect Master study plan

Diagram the end-to-end request flow from browser or app to at.js/Web SDK, the edge, and the decision engine, labeling each hop

Compare at.js and Web SDK (Alloy) on data layer, identity, and event handling, and write a one-page selection rationale for two scenarios

Explain how mbox parameters, profile scripts, and server-side APIs (Delivery API) differ in where they execute and what they can access

Map the at.js/Web SDK prerequisites (launch property, data elements, identity sync) into an implementation checklist

Distinguish when to use A/B, MVT, XT, Automated Personalization, and Recommendations based on traffic, number of variables, and goal

Design a full activity spec (goal metric, success event, audience, traffic allocation, duration) for an A/B test and an XT activity

Calculate required sample size and minimum detectable effect for a proposed test and justify the traffic split

Identify the traffic and data requirements that make Automated Personalization and Recommendations viable, and note their failure modes

Build audiences from multiple sources (custom, geo, technology, profile, Analytics/AAM segments) and explain their refresh behavior

Write three personalization strategies that map audience segments to experiences and justify the targeting rules

Explain how profile attributes, first-party IDs, and segment membership drive eligibility at decision time

Design a priority and conflict-resolution plan for overlapping audiences and activities

Define success metrics, report suites, and conversion events that map to business goals for each activity type

Interpret A/B and AP reports (lift, confidence, segments) and identify when a result is not yet actionable

Explain how Recommendations and Automated Personalization reports differ from standard A/B reporting

Set up a measurement plan that ties activity goals to downstream Analytics metrics

Trace how Target shares audiences and profile data with Analytics, Audience Manager, AEP, and Campaign, and where identity stitching occurs

Configure (in a sandbox or documented steps) an A4T integration and describe how report data flows back

Describe the data flow for activating a Target audience in Campaign and for ingesting AEP segments into Target

Identify integration failure points (ID mismatch, report suite config, segment sync lag) and their diagnostics

Write implementation steps for at.js/Web SDK including data layer, identity, and event tracking for a sample page

Describe how to handle mobile and offline channels (mobile SDK, server-side, offline decisioning) and their constraints

Apply data governance rules: consent, data retention, PII handling, and what must not be passed to Target

Map privacy and security requirements (consent gating, encryption, access control) to configuration decisions

Build a QA plan for activities (preview links, QA mode, response tokens, experience validation) and a pre-launch checklist

Diagnose common issues: activity not delivering, audience mismatch, flicker, and reporting discrepancies, with a triage sequence

Define admin governance: user roles, approvals, activity naming conventions, and workspace structure

Explain how response tokens and debug tooling support troubleshooting and audit

Synthesize all domains into a single end-to-end solution design for a hypothetical client

Complete a timed practice set and review every missed item against the source domain

Re-verify weak areas identified in earlier weeks and close knowledge gaps

Rehearse explaining architecture and governance trade-offs aloud as an architect would