AD0-E406 Adobe Target Business practitioner Expert Exam Topics and Questions

Planning and strategy sets the foundation for everything else in this exam. At 31%, it is the second-largest topic by weight, and it costs candidates who treat it as "soft" theory. The real demand here is translating messy business language into testable, measurable optimization goals, then making defensible decisions about what to run, in what order, and with how many visitors.

– From business goals to testable hypotheses

The exam will put you in scenarios where a stakeholder gives you a KPI, a conversion rate, or a revenue target and expects you to turn it into an optimization goal. That translation step is where candidates stumble: a KPI like "increase checkout revenue" needs to be decomposed into a specific, measurable change you can test. Once you have the goal, you need to construct a hypothesis that names the change, the expected direction, and the reason behind it. The exam also asks you to evaluate hypotheses someone else has written, so you need to know what makes one valid: a clear baseline, a single variable, a predicted outcome, and a rationale grounded in evidence. A hypothesis that says "changing the button color will help" fails on at least two of those counts. Practise spotting the missing element rather than memorising a formula.

– Prioritisation, sample size, and analytics sourcing

Once you have a backlog of test ideas, the exam asks you to rank them. The prioritisation framework the vendor expects is not just gut feel: you need to weigh business impact, implementation effort, and realistic lift potential together. A high-effort, low-traffic page rarely earns the top slot regardless of how exciting the idea sounds.

Sample size is a frequent trap. The Adobe Sample Size Calculator inputs include baseline conversion rate, minimum detectable effect, and confidence level. Changing any one of them shifts the required sample dramatically, and the exam tests whether you understand the direction and magnitude of those shifts, not just that the tool exists.

Finally, you need to know when to use Target's native reporting versus routing data through Adobe Analytics (A4T). The decision turns on factors like cross-session attribution needs and which metrics already live in Analytics. The exam presents scenarios and asks you to pick the right source, so understand the practical reasons for each choice rather than memorising a rule.

– Audiences, success metrics, and KPI alignment

Audience requirements feed directly into activity design: you need to assess who the activity targets, whether that audience is large enough to reach significance in a reasonable timeframe, and whether the audience definition matches the business goal. An activity targeting all visitors when the KPI only applies to returning purchasers is a planning failure, and the exam will surface exactly that kind of mismatch.

Success metrics split into primary and secondary, and the distinction matters. The primary metric drives the statistical conclusion; secondary metrics add context but do not determine the winner. Candidates lose marks by either conflating the two or by picking a primary metric that is technically measurable but not aligned to the stated KPI. Work through scenarios where the obvious metric and the right metric are different things: that is where the exam applies pressure.

How Planning and strategy is tested

At 31% of the exam, this topic generates a significant share of items, and most of them are scenario-based. You will be handed a business situation, a dataset, or a partial hypothesis and asked to make a judgment call. Items reward the ability to identify what is missing or wrong in a planning artifact, such as a hypothesis that lacks a measurable outcome or a prioritisation decision that ignores traffic volume.

Sample size calculator items are particularly precise: the exam expects you to know which input changes which output and in which direction. Guessing the general shape of the relationship is not enough.

The analytics sourcing question is a classic either/or scenario where both options are defensible on the surface. Items reward selecting the source that fits the specific constraints in the scenario, not the one that sounds more sophisticated.

Candidates most often lose marks by applying general testing theory rather than Adobe Target-specific logic, and by treating audience assessment as a checkbox rather than a constraint that drives every downstream decision.

After planning comes execution, and at 42% this is the heaviest topic on the exam by a wide margin. The breadth here is the challenge: you are expected to know the procedural steps for creating every major activity type, understand when each composer is the right tool, and manage audiences and settings with enough precision that you can catch a misconfiguration in a scenario. Expect a large share of your exam time to be spent here.

– Visual Experience Composer vs. Form-Based Composer

The exam does not simply ask you to define the two composers. It presents scenarios and expects you to identify which one applies and why. The Visual Experience Composer works in a browser-rendered view and is suited to standard web pages where you need to manipulate elements visually. The Form-Based Composer operates without a visual rendering layer, making it the right choice for email, single-page application areas that the VEC cannot reach, and non-HTML environments like JSON offers.

Beyond the selection decision, you need to know the procedural steps for creating an experience inside each one. In the VEC that includes selecting elements, applying modifications, and managing multiple experiences within the same activity. In the Form-Based Composer it means defining locations and content manually. The exam will describe a partially completed setup and ask what comes next or what is wrong, so you need the workflow in the right order, not just the general concept.

– Activity types: A/B, XT, MVT, and AP

Each activity type has a distinct purpose, and the exam tests whether you can match the type to the scenario as well as execute the creation steps correctly.

A/B testing splits traffic between variations to find a winner. Experience Targeting (XT) delivers a specific experience to a specific audience without a statistical winner: it is rules-based, not hypothesis-driven. Multivariate testing (MVT) tests combinations of changes across multiple locations simultaneously and uses Experience Performance reports to isolate which element contributes most to lift. Automated Personalization (AP) uses machine learning to match visitors to offers at the individual level; you do not define the winner manually.

The exam asks about AP at the conceptual level: what problem it solves and when it is appropriate, rather than step-by-step configuration. For A/B, XT, and MVT, expect procedural questions: what settings you configure, in what order, and what each setting controls. Mixing up XT and A/B is a common error because both involve multiple experiences.

– Recommendations, Audiences, Goals, and QA

Recommendations activities add another layer: you are configuring criteria, designs, and collections on top of the standard activity workflow. The exam tests the creation procedure and the relationship between those components, not the recommendation algorithm internals.

Audience creation in Target requires knowing the available attribute categories (visitor profile, traffic source, technology, and so on) and how to combine rules with AND and OR logic. A scenario might describe a business requirement and ask you to build the audience definition that matches it precisely. Getting the boolean logic wrong produces an audience that is either too broad or too narrow.

Goals and Settings is where you define success metrics, set the priority, configure the reporting source, and schedule the activity. Each field has a downstream effect. Activity QA mode lets you preview and validate experiences before going live using a shareable URL that forces a specific experience. The exam tests the purpose and mechanics of QA mode, including who can use the QA link and what it does to normal visitor bucketing.

How Configuring, Executing and Managing is tested

With 42% of the exam weight, this topic dominates the item count. Most items are procedural or scenario-based: a setup is described, something is incomplete or wrong, and you identify the fix or the next step. Items reward knowing the exact sequence of the activity creation workflow, not a general familiarity with the interface.

Activity type selection is a consistent source of difficulty. Scenarios are written so that two activity types could plausibly fit, and items reward the one that matches the specific business constraint in the scenario, such as the need for individual-level personalization versus a simple split test.

Audience logic is another trap. Candidates who understand each attribute category individually still lose marks when AND versus OR logic produces an unexpected audience size. Work through audience scenarios where the logic is ambiguous.

QA procedures and Goals and Settings configurations are tested in detail. The exam expects you to know which settings interact with each other, not just what each field means in isolation. Breadth of procedural knowledge across all activity types is the core demand.

Execution without interpretation is incomplete, and this topic tests whether you can close the loop. At 17%, it is smaller than the first two topics but it rewards a specific kind of analytical precision that many practitioners underestimate. The questions here are less about knowing where to click and more about knowing what the numbers mean, when to trust them, and when the test design itself is the problem.

– Report settings, AP reports, and MVT performance

Report settings determine what appears in a Target report: the date range, the counting methodology, the metric displayed, and how conversions are attributed. Changing the counting methodology (such as switching from "impression" to "visitor") can shift the numbers significantly. The exam tests whether you understand what each setting controls and how to configure a report to answer a specific business question.

Automated Personalization Summary reports differ structurally from A/B and XT reports. They show offer-level performance and the contribution of the automated model rather than experience-level lift with a clear winner. Candidates who try to read an AP report the same way they read an A/B report will draw wrong conclusions, and the exam exploits that expectation.

MVT Experience Performance reports require a different lens again. The goal is to identify which element or combination of elements drives the result, not simply which full experience won. Reading the contribution of individual locations is the skill the exam tests here.

– Sample size, A/B testing pitfalls, and declaring a winner

The Sample Size Calculator appears in this topic as a validation tool, not just a planning tool. After an activity runs, you need to assess whether the results are statistically sound: did the activity collect enough observations to support the conclusion? The exam presents report scenarios and asks you to evaluate whether the data justifies a decision.

Common A/B testing problems include peeking (stopping a test early when one variation looks ahead), running too many variations without adjusting the required sample size, and novelty effects inflating early results. The exam asks you to identify which problem is present in a described scenario and what should have been done differently.

Declaring a winner requires combining observed lift, confidence level, and business objectives. A variation with strong lift but low confidence is not a winner. A variation that reaches statistical significance but delivers lift below the minimum business threshold may also not justify rollout. Items reward applying all three criteria together rather than defaulting to the one that looks most favorable.

How Analyzing and Reporting is tested

At 17%, this topic produces a focused set of items that tend to be analytical rather than procedural. You will be given a report scenario, a set of numbers, or a description of test conditions and asked to evaluate what they mean or what should happen next.

Items reward the ability to distinguish between a statistically valid result and one that looks valid on the surface. The peeking problem is a classic item: a test was stopped early, the numbers looked good, and the question is whether the conclusion holds. Items reward identifying the flaw in the decision process.

AP report items reward understanding that the output is structurally different from other report types, not just that it uses machine learning. Candidates who have only worked with A/B reports in practice often misread AP summary data under time pressure.

Sample size validation questions require you to apply the calculator logic in reverse: given the results, was the sample sufficient? Work through scenarios where the observed confidence level and the actual sample size point in different directions. That tension is where marks are won and lost.

Troubleshooting is the smallest topic at 10%, but it is one where preparation pays disproportionately. Candidates who have not deliberately practised diagnosing Target issues tend to rely on vague intuition, and that approach does not hold up against scenario-based items. The three sub-topics here are tightly scoped, which means you can cover them thoroughly without a large time investment.

How Troubleshooting is tested

Items in this topic present a described problem, a partially working activity, or a suspicious report and ask you to identify the cause or the diagnostic step. Activity qualification issues are a frequent scenario: a visitor should qualify for an activity but does not, or qualifies when they should not. Items reward working through the qualification logic systematically, checking audience rules, activity status, URL conditions, and profile attributes in the right order rather than jumping to a conclusion.

Browser debugging tool items focus on the Experience Cloud Debugger. You need to know what information it surfaces, what a healthy Target request looks like in that output, and how to use it to confirm whether an mbox is firing and whether the correct activity and experience are being delivered.

Metrics and reporting verification rounds out the topic. Items reward knowing how to confirm that a conversion metric is firing correctly and that report data reflects actual visitor behavior. Candidates lose marks by conflating an implementation problem with a configuration problem: the two have different diagnostic paths, and the exam distinguishes between them.