Key takeaways

In this module, you learned how to:

• A template rule automatically propagates a structural change to any page that matches a URL condition. Configured under Page Delivery (via the gear icon in the VEC), a template rule tells Target which other pages should inherit the experience modification you've made. The critical requirement is that all targeted pages must share the same CSS structure — if the CSS differs, the change won't apply correctly. A URL condition like "contains /magazine" defines which pages are in scope.
• A multipage test differs from a template rule test in how pages are added and how changes are applied. A template rule applies the same change everywhere the rule matches automatically. A multipage test requires you to manually add each specific page using "add additional pages" in the configure menu, and each added page can have its own distinct, page-specific experience design. Use multipage tests when the experiences across pages need to be different from each other, not just a uniform change at scale.
• A single Target activity can hold up to 30,000 experiences. This is not a typo — the platform is built to support massive-scale variation testing, whether you're testing thousands of CTA copy combinations, layout variations, or interconnected page series across a multipage funnel.
• The Objective field is one of the few places in Target for documenting activity context. Unlike most analytics tools, Target's activity builder has limited space for notes. The Objective field is important precisely because it persists with the activity — especially when a secondary metric only exists in some experiences. If Experience A has no checkout button but Experiences B and C do, documenting that in the Objective field prevents future team members from mistakenly thinking something is broken when they see zero conversions for that metric on Experience A.
• When you truly want only one experience served to all visitors, use Experience Targeting instead of an A/B test. An A/B test requires at least two experiences. Setting the split to 0%/100% is a valid QA technique for verifying report instrumentation, but in production use, Experience Targeting is the appropriate activity type for delivering a single experience to a defined audience without the forced two-experience constraint.