A/B Test Demo — Adobe Target

What is an A/B Test?

An A/B test (or split test) compares two or more versions of a page element to see which performs better against a specified goal metric. Traffic is randomly split between variations, and statistical analysis determines the winner.

When to Use

Testing new page layouts or designs
Comparing CTA copy or button colors
Validating hypothesis-driven changes
When you need clean statistical proof

Key Characteristics

Even traffic split (configurable)
Requires sufficient sample size
Manual winner declaration
Supports up to 5 experiences + control

How It Works

1

sendEvent with decisionScopes

2

Target resolves activity & experience

3

Proposition returned to browser

4

Manually render content

5

Send propositionDisplay event

6

Track interactions & conversions

⚙️ Web SDK Configuration

This page uses a single sendEvent call with renderDecisions: true to handle both composers. VEC modifications are auto-applied by the SDK, while form-based propositions are manually rendered.

// Alloy Web SDK v2.24.0 — Single call handles both VEC + Form-Based
alloy("sendEvent", {
  renderDecisions: true,   // Auto-apply VEC modifications
  personalization: {
    decisionScopes: ["wz_ab_exp1"] // Form-based scope
  }
}).then(function(result) {
  // VEC props → auto-rendered (renderAttempted: true)
  // Form props → result.propositions (manual render)
});

📐 Experience Composers

Adobe Target offers two ways to author experiences. This page demonstrates both approaches working together in a single A/B test activity.

🎨 Visual Experience Composer (VEC)

WYSIWYG editor — modify page elements visually
Target identifies elements via CSS selectors
Uses renderDecisions: true
SDK auto-applies DOM modifications
Propositions scoped to __view__
Best for: visual changes to existing page elements

📝 Form-Based Experience Composer

Non-visual interface — content delivered to named locations
Uses custom decisionScopes (e.g. wz_ab_exp1)
Propositions fetched & manually rendered
Full control over rendering logic
Supports HTML, JSON, and redirect offers
Best for: headless, email, kiosks, SPAs

🎨 VEC Demo — Hero Banner

The hero banner below contains elements targetable via the Visual Experience Composer. When a VEC activity is active in Adobe Target, the SDK automatically modifies these elements using CSS selectors — no manual rendering required.

Waiting for VEC propositions…

Limited Time Offer

Discover Our Latest Collection

Explore premium products curated just for you. Free shipping on all orders over $50.

Shop Now →

#vec-hero-ab #vec-headline-ab #vec-subtitle-ab #vec-cta-ab

💡 Create an A/B activity in Adobe Target using the VEC pointed at this page URL. Target will load the page, let you visually click & modify elements (text, styles, images), and deliver those changes automatically via renderDecisions: true.

📝 Form-Based Demo — wz_ab_exp1

The experience below is resolved by Adobe Target using the Form-Based Experience Composer. The Web SDK requests the wz_ab_exp1 decision scope, receives a proposition, and renders the assigned experience manually.

▶ Experience Delivery

Requesting Experience from Adobe Target…

Experience A

<p>Experience A for a/b test</p>

Experience B

<p>Experience B for a/b test</p>

📋 Proposition Details

No proposition data yet

Initializing Web SDK…

🔬 A/B Test VEC + Form-Based