Experiences and Activities
What to know
This domain covers building activities: experience creation, offer/content editing (Visual Experience Composer vs. Form-Based Experience Composer), activity settings, goals and settings (success metrics, reporting audiences), activity priorities, and collision handling. Candidates should understand the VEC workflow (select element, modify, preview), code editor and custom code limitations, experience fragments reuse, and the difference between activity-level and experience-level audiences. Also know activity states (draft, active, inactive, archived), QA/preview links, and approval workflows if applicable.
Traps in questions
- Mixing up where audiences are applied: activity-level audience gates entry; experience-level audience determines which experience a visitor sees within the activity.
- Forgetting that the Form-Based Composer is needed when the page cannot be loaded in the VEC (e.g., mbox-only or non-web contexts).
- Assuming custom code runs in the VEC preview exactly as in production; script timing and SPA behavior differ.
- Priority and collision traps: higher priority wins when activities overlap on the same audience/page.
Worked example / rule of thumb
You need to test a hero banner on a page that requires login and cannot render in the VEC. Use the Form-Based Experience Composer with an mbox and an offer. Rule of thumb: VEC for visual DOM changes; Form-Based for mbox/offer delivery or non-renderable pages. For collisions, set explicit priorities and use reporting audiences to segment results; never rely on launch order alone.