Implement and Manage Activities
Building the activity
A Target activity has a name, objective/metric, audience, experiences, traffic allocation, and scheduling. The Visual Experience Composer (VEC) edits the page in a rendered view; the Form-Based Experience Composer builds offers without loading the page, useful for mboxes, emails, and API-driven content. Know when each is appropriate - a trap is selecting the VEC for content that has no live page to load.
Traffic allocation and goals
Fixed allocation splits traffic evenly; Auto-Allocate shifts traffic toward the best performer while keeping a control; Auto-Target personalizes per visitor using a profile. The success metric must be configured correctly - conversion events, revenue, or custom mboxes. Understand that the primary goal drives the automated algorithms, and secondary metrics are observational.
Targeting and sequencing
Experience targeting (XT) maps audiences to experiences; A/B tests assign visitors randomly. Multi-page activities and A/B with multiple touchpoints require consistent visitor assignment. Learn about activity collisions and priority: when two activities target the same page and audience, priority and allocation rules decide which renders.
QA and launch
Use the activity QA feature to preview with query-string parameters, forcing a specific experience without affecting reports. Verify audience qualification, offer rendering, and analytics firing before activating.
Worked rule of thumb
If two activities collide, raise priority on the more important one rather than editing audiences - priority is the designed conflict-resolution tool.
Common traps
Forgetting that QA mode traffic is excluded from reporting; launching without checking goal configuration; assuming Auto-Target works without sufficient conversion data.