How to deliver personalized experiences with Adobe Target and Edge Delivery Services

Part 1: Form-Based Activity — Hero A/B Test

What to emphasize

• Authors create hero variants as DA fragments — they never touch Target
• Marketers pick the fragment as an offer in Target and configure the traffic split
• The homepage-hero-mbox decision scope is requested at page load
• 50/50 split runs automatically — no URL parameters, no cookies to manage
• This pattern works for any "swap a section" personalization

Steps

1. Show the live homepage — point out the current hero ("The Science of Wealth Preservation"). This is the control experience.
2. Open the variant fragment in DA — show the hero-variant-b fragment in DA — different headline ("Your Blueprint for Financial Independence") and a softer CTA.
3. Show the "Send to Target" flow — DA → Prepare → Send to Adobe Target → offer appears in Target as an HTML offer.
4. Open Target → Activity — show the Form-Based Composer: mbox = homepage-hero-mbox, Experiences A (control) / B (variant), 50/50 split.
5. Activate and preview Variant B — hero swaps to "Your Blueprint for Financial Independence."
6. Key talking point: The author created the content. The marketer wired the targeting. No developer involved for the live activity.

Part 2: Form-Based XT — Teaser Personalization by Audience

What to emphasize

• Experience Targeting (XT) delivers different content per audience — not random like A/B
• Uses Target-native "New Visitors" audience — no RT-CDP or AEP datasets required
• Authors create the teaser fragment; marketers assign it to the audience in Target
• Multiple audiences are prioritized (first match wins)

Steps

1. Show the default teaser on homepage — "Check out our library of beginner-friendly guides..." This is what returning visitors see.
2. Open the new-visitor teaser fragment in DA — fragments/offers/learn-home-teaser — "New here? Start with the basics."
3. Open Target → Homepage Teaser XT — show the XT flow: Experience B (New Visitors) → new teaser offer, Experience A (All Visitors) → default.
4. Preview the New Visitors experience — teaser swaps to the beginner-focused message.
5. Key talking point: One line of metadata (target: on) on the page is all it takes. The plugin handles the rest — fetch, decide, render.

Part 3: VEC Activity — Page-Level Audience Targeting

What to emphasize

• Visual Experience Composer (VEC) — marketers make changes directly in the Target UI without touching code or DA
• Ideal for quick copy tweaks, headline tests, and seasonal messaging
• Changes are delivered as DOM actions — no fragments needed
• Audience targeting: New Visitors, Returning Visitors, All Visitors — each sees a different h1 on the Products page

Steps

1. Show the products page — default h1 says "All Products." This is the fallback experience for All Visitors.

2. Open Target → Products Page VEC activity — show 3 experiences with h1 changes made entirely inside the Target VEC.

3. Walk through each experience:

   • New Visitors → "Start with the Basics"
   • Returning Visitors → "Level up your Strategy"
   • All Visitors (fallback) → "All Products"

4. Preview each experience in Target — show the h1 swapping per audience segment.

5. Key talking point: The marketer made these headline changes entirely inside Target. No code deploy needed. When the activity ends, the original content returns automatically.

Part 4: Analytics & Measurement

What to emphasize

• Single Web SDK call sends data to both Target AND Analytics — no dual-tagging
• Adobe Tags (Launch) provides rule-based analytics for custom events (CTA clicks, product card clicks)
• Page views flow automatically to Analytics via the datastream
• A4T is available as an upgrade path (enhancement) — switch the reporting source in any activity to unify experiment data in Analytics Workspace
• Real-time debugging via AEP Debugger extension

Steps

1. Show the network call — open DevTools → Network → filter interact → show the single edge call that returns Target decisions AND sends the page view to Analytics.
2. Open AEP Debugger (if installed) — show Target tab (propositions returned) + Analytics tab (page view hit confirmed).
3. Show Analytics Workspace — open the project, show Page Views by Page dimension → hits from demo.bbird.live are landing.
4. Key talking point: One integration, one edge call — Target gets personalization decisions, Analytics gets behavioral data. Each solution reports independently with no conflicts.

Part 5: Performance — No Lighthouse Regression

What to emphasize

• The #1 objection to personalization: "it will kill my page speed scores"
• aem-martech plugin uses eager loading — personalization resolves in parallel with first section render
• No render-blocking scripts, no layout shift from late content swap
• Lighthouse scores stay at 100 on both personalized pages
• Deep PSI tool shows side-by-side proof

Steps

1. Open the Deep PSI tool — Deep PSI comparison
2. Show both pages scoring 100 — overall Performance score unchanged after integrating Target.
3. Call out the architecture reason — the plugin fires alloy in loadEager inside a Promise.all alongside section rendering. If Target responds within 1s, content is swapped before first paint. If it doesn't, the page renders default content (graceful timeout).
4. Key talking point: "We added real-time personalization — three active Target activities — and the Lighthouse score didn't move. That's the benefit of the aem-martech architecture: performance and personalization aren't tradeoffs."

Related Articles