Module quiz

1. A Target-only feature that adds Analytics metrics to the Target interface without pushing data to Analytics
2. Any Adobe Target activity that uses Adobe Analytics metrics for its primary goal and pushes test results into the Analytics interface, giving marketers Target's experimentation paired with Analytics' superior reporting and segmentation capabilities
3. A feature that requires a separate implementation for each individual activity
4. A feature available only for Experience Targeting and Automated Personalization activities

1. A/B Test
2. Multivariate Test
3. Experience Targeting
4. Automated Personalization

1. The ability to name experiences and set a priority level for the activity
2. The ability to add multiple goal metrics in the Target interface, since you will analyze the activity in Analytics where you can add as many metrics as needed without pre-selecting them in Target
3. The ability to use audiences for targeting and to preview experiences with QA links
4. The ability to name the activity and set a test duration

1. There is no admin setting. Each marketer must manually select Analytics as the reporting source every time
2. An admin can set an account-level default reporting source, forcing all activities to use Analytics, keeping all in Target's native reporting, or leaving it as a per-marketer choice at the goals and settings step
3. The reporting source is determined by the workspace the activity belongs to, not an admin setting
4. The reporting source is set at the property level in Adobe Tags and cannot be changed in Target

1. Wait until midnight to activate the activity to align with the hourly batch cycle
2. There is no way to reduce A4T latency. It is always exactly 90 minutes
3. Save the A4T activity before pushing it live. This initiates the classification process early so that once the test goes live, data appears within normal report suite latency rather than the worst-case window
4. Activate the activity and then immediately pause it for 30 minutes before resuming