Adobe CJA Business Practitioner Pro study plan

Map the end-to-end Customer Journey Analytics data flow (Experience Platform dataset → connection → data view → Workspace project) and draw it for a fictional multi-channel retailer.

Distinguish event, profile, lookup, and summary dataset types and match each to at least two reporting use cases.

Specify the schema prerequisites for a working connection: XDM class, primary identity namespace, timestamp field, and deduplication key.

Select and justify a person ID for the retailer scenario, documenting the impact of that choice on cross-device reporting.

Configure a practice connection that includes one event dataset and one lookup dataset, then verify field availability on the connection detail screen.

Compare field-based and graph-based stitching and defend one choice for a known cross-device identity gap.

Explain how data retention windows and dataset-level settings change historical reporting, and record the tradeoffs in writing.

Draft a data view skeleton covering session settings, container definitions, calendar type, and default attribution.

Curate at least ten components in the draft data view by renaming, describing, tagging, and approving them, and hide components that would confuse business users.

Walk through derived fields and state two reporting problems they solve that data view components alone do not.

Convert a business question list into a field-to-component mapping, marking each field as dimension or metric.

Format components correctly: currency, percentage, decimal precision, and date formats for at least five components.

Set participation and attribution behavior per metric and explain in writing how repeated instances of a value are counted.

Detect and remove duplicate or near-duplicate components across data views and document the naming standard that prevents recurrence.

Test the curated data view by building a small table that confirms each curated component returns expected values.

Build a freeform table with nested dimension breakdowns and apply the correct metrics for each business question.

Apply filters inside a panel and confirm the panel-level context changes results as expected.

Choose and justify at least three visualization types (for example bar, line, scatter, and donut) against the shape of the underlying data.

Configure an attribution panel, a fallout panel, and a flow panel, and interpret one insight from each.

Configure a date comparison and a percent-of-total view to answer a trend question in a single table.

Analyze a multi-step journey in a flow or journey visualization and identify the largest drop-off step.

Build a cohort or retention table and describe what the retention curve implies for the business.

Create a basic segment using the correct container level (visitor, visit, or hit) and verify its population count.

Build a sequential segment that includes a step, an exclusion, and a time constraint.

Publish one segment as an audience to Real-Time CDP and confirm the destination configuration.

Build a calculated metric from two existing metrics and validate the result against a manually computed value.

Create an advanced calculated metric using an attribution function and explain the function's effect on the output.

Test metric compatibility across segments and document which combinations break or return unexpected results.

Compare a segment built on a data view component with one built on a derived field and note the behavioral difference.

Share a curated segment and calculated metric set with a mock stakeholder group using tags and descriptions.

Compare last-touch, first-touch, linear, participation, and position-based models on the same dataset and quantify the difference in channel credit.

Trace how stitching and person ID choices change cross-channel journey reporting, and document one limitation of each approach.

Apply data usage labels and a data usage policy to a dataset, then explain how the policy constrains downstream use.

Configure or audit data retention, IP obfuscation, and privacy request handling, and list the admin roles involved in each.

Map product profiles and permissions to a three-person team so each person has least-privilege access.

Translate a business objective into a measurement plan with KPIs, required data, and the analysis that answers each question.

Write a five-slide insight narrative that leads with the recommendation and supports it with a Workspace visualization.

Complete a timed 60-question practice set spanning all seven domains and log every miss by domain and root cause.

Re-drill the three weakest objectives identified in the error log until each is explained aloud without notes.

Assemble a one-page exam-day reference of session settings, attribution behavior, container rules, and governance limits.