Key takeaways

In this module, you learned how to:

• Auto-allocate uses a "Multi-Armed Bandit" algorithm to balance learning with winning. Once a winning experience begins to emerge, approximately 80% of new visitors are directed to it while the remaining 20% is distributed across all experiences — including the winner — for ongoing learning. This reserve allows Target to detect if a previously winning experience starts declining and another rises, rather than locking in on potentially stale results.
• The allocation method is locked once an activity goes live and collects traffic. If you need to change from manual allocation to auto-allocate (or vice versa) after a test has already launched, the setting is grayed out to protect the integrity of the data already collected. The workaround is to copy the activity, configure the new version with the desired allocation method, and activate the copy — leaving the original intact.
• An Experience Fragment must be published from AEM before it appears in Target. An Experience Fragment (XF) is a reusable composite of AEM components — combining content, layout, images, and CTA buttons into a self-contained unit. To make it available in a Target activity, you click on the XF thumbnail (not the text) in AEM and choose Publish. Once published, it automatically appears in Target's offer selection without any additional configuration.
• Save HTML offers to the Offers library when you plan to reuse them across multiple activities. An HTML offer can be created inline inside a single activity for one-time use, or saved to the shared Offers library for reuse. Saving to the library means you only build the offer once — any activity can then reference it, and you avoid recreating the same code in each new test.
• Multiple conversion elements act as OR conditions — any one click counts. When you visually select multiple page elements (such as several CTA buttons) as a single conversion goal, Target treats them as OR logic: a visitor who clicks any one of the selected elements triggers the conversion. You only need to define this goal once — it applies globally across all experiences in the activity and does not need to be set per experience.