Strategy & Roadmap

Leveraging Context Hub to Transform How Labcorp Tests & Personalizes

How we move from picking one winner for everyone to delivering the right experience for each user — using tools we already have.

1

From Testing Pages to Testing Contexts

Instead of testing one variant vs. another globally, test which experience works best for each situation.

Traditional A/B Test

All traffic enters
↓ 50 / 50 split
Variant A — everyone sees this
Variant B — everyone sees this
↓
Pick one winner for all users
→

Context-Driven Test

Context Hub reads signals
↓ route by context
Variant A → high-intent users
Variant B → hesitant users
Variant C → first-time users
↓
Multiple winners, each for the right audience

How it works: Context Hub + Target together

Context Hub reads signals and swaps content at the component level — individual headlines, CTAs, images, and even full Experience Fragments (carousels, product modules, entire sections). Target handles A/B testing, traffic splitting, and code-level changes. The combination of the two is where the real power lives.

Context Hub unifies the signals that tell us who is on the page and what they need:

👤 Logged-in vs. anonymous 🔍 Health intent (symptom vs. wellness) 📊 Behavioral signals (scroll, compare, hesitate) 📱 Device & location 🔗 Referral source 🛒 Prior product views / cart 📋 External data (API / JSON feeds)

This maps directly to the pain points we already know about:

⏸

Mid-Funnel Hesitation

Users who stall mid-checkout get targeted reassurance — not the same messaging as someone who's already confident.

⚖

Comparers vs. Decisive Buyers

Product browsers who compare 3+ items get comparison-focused layouts. Decisive buyers get a streamlined path to cart.

🔄

Logged-In vs. Anonymous Users

We know if a user is logged in — we just can't see who they are (HIPAA). That's still enough to differentiate: anonymous visitors get education and trust signals, logged-in users get a streamlined experience.

2

Turn Learning Tests into Segmentation Discovery

We already distinguish between learning tests and optimization tests. Context Hub makes learning tests dramatically more valuable.

Without Context Hub

Run learning test
↓
Learn: "Trust clusters improve conversion"
↓
Single insight, broadly applied
→

With Context Hub

Run learning test + segment analysis
↓
Learn: "Trust clusters work for first-time, high-anxiety users — not repeat buyers"
↓
That becomes a rule
That becomes a segment
That becomes a permanent personalization strategy

The key shift

Testing feeds long-term personalization instead of just producing one-off wins. Every learning test becomes a brick in our personalization foundation — not a standalone report.

3

Personalize the Highest-Impact Tests in Our Roadmap

Some of our existing test concepts are perfect candidates for Context Hub layering. Since Context Hub swaps content at the component level — individual text fields, images, and even entire Experience Fragments — these are all achievable today.

"Who Is This For" Statement

Currently a static statement on the product page. With Context Hub, it adapts.

New Users

Show "For first-time testers" — normalizes the experience, reduces anxiety

Repeat Users

Show "For ongoing monitoring" — frames around continuity and routine

High-Intent

Show "For specific symptoms" — mirrors their search-driven intent

"What Happens Next" — Checkout Guidance

We've already identified this as a major leak fix. Context Hub lets us serve the right depth of guidance.

High-Anxiety

Detailed step-by-step reassurance — walk them through the full process with trust signals

Confident

Short, frictionless version — just the essentials, no hand-holding

Mobile

Simplified + visual — icon-driven steps optimized for small screens

Product Card Optimization — Comparers

Users compare multiple products heavily. Context Hub lets us match messaging to behavior.

New Users

Benefit-first messaging — lead with what the test does and why it matters

Comparers

Comparison-focused messaging — highlight differentiators and "most popular" signals

Indecisive

"Recommended" badges — reduce decision fatigue with curated suggestions

Experience Fragments as Offers New Capability

Context Hub can now serve entire Experience Fragments as offers — not just individual field swaps. This means full carousels, product modules, or section blocks can change based on context.

Men's Health

Men's health product carousel — user clicked into men's health category, so the featured products fragment swaps to match

General

Default "most popular" carousel — no category signal, show the standard bestsellers fragment

Seasonal

Seasonal health carousel — driven by time-of-year data (allergy season, flu season) via Context Hub date signals

4

Replace Static A/B Tests with Adaptive Testing

Using Adobe Target + Context Hub, we shift from "pick a winner" to "keep multiple winners, each for the right audience."

1
Start with A/B test — standard experiment, variants assigned randomly
2
System learns — identifies which variant wins per segment
3
Shift to Auto-Target — traffic automatically routes to the best variant per context
4
Permanent personalization — what started as a test becomes an always-on rule

Auto-Allocate

Automatically shifts traffic toward the winning variant as statistical confidence builds — faster decisions, less wasted traffic.

Auto-Target

Uses machine learning to identify the best experience for each visitor based on their profile — multiple winners coexist.

Always-On Rules

Once a pattern is validated, promote it to a permanent personalization rule — no manual intervention needed.

5

Build a Feedback Loop into Our Roadmap

Right now the roadmap flows linearly. Context Hub turns it into a compounding cycle.

Current Flow

Test
↓
Win
↓
Move on
→

Context Hub Flow

Test — run the experiment
↓
Identify segment differences
↓
Create audience — save the segment
↓
Personalize — deploy to that audience
↓
Retest — refine and compound

Q1 quick wins → Q2–Q4 strategic advantage

This is already our stated goal. The feedback loop is the mechanism that makes it real — each test compounds into the next, building a personalization engine instead of a list of one-off experiments.

6

Where This Really Increases Our Value

Personalization is a top priority across Labcorp. We've made a significant Adobe investment — and Context Hub gives us a way to start delivering on that investment right now, with tools that are already in the box. Here's how that changes our positioning.

Without Context Hub With Context Hub
The person running tests The person designing how Labcorp learns about and adapts to its customers
One-off wins Compounding personalization strategy
Personalization blocked until AJO & CDP Delivering personalization now with tools already available
Test → report → next test Test → segment → personalize → retest
Testing → Personalization → Roadmap
7

What We Can Do Right Now

Based on the Context Hub store data and our initial POC work, these are actionable today — no new tooling, no waiting for CDP or AJO.

1

External Data-Driven Content Control

Context Hub can pull in external data via API as a JSON feed — with real-time polling, the page updates while users are still on it. The POC proved this out using a Google Sheet, but the capability extends to any external data source that returns JSON. Important: segments read one data point at a time. But we can combine data points with AND/OR operators and stack them with other segments (e.g., "IF data field = 'sale' AND month = March"). Each data point we want to use needs to be mapped individually.

external API / JSON feed polling: real-time AND/OR operators
Example: An external data source returns a "seasonal_focus" field set to "allergy." A segment checks: IF seasonal_focus = "allergy" → swap the hero banner component to the allergy-focused variant. Stack it: IF seasonal_focus = "allergy" AND month is March–May → show the seasonal banner only during actual allergy season. Marketing controls the flag from the data source, zero deploys needed.
2

Geo-Based PSC Messaging

Geolocation is available down to street level — city, region, postal code, even lat/long. Caveat: we need to create a discrete audience for each location we want to target (e.g., "Charlotte metro," "Raleigh-Durham"). Context Hub can't dynamically resolve "nearest PSC" — but it can match a user's region to a pre-built audience. Target may also support more abstract geo rules, which we can explore as a next step.

store.geolocation.address.city store.geolocation.address.region store.geolocation.address.postalCode 1 audience per location
Example: Build audiences for top 5–10 PSC-dense metros. Users matching "Charlotte metro" audience see a "Walk in today — 12 locations near you" CTA. Users not matching any geo audience get the default "Find a location" with PSC finder link. Start with high-volume markets, expand as the pattern proves out.
3

Time-of-Day & Seasonal Messaging

The store exposes hour, day, month, and year. Combined with external data feeds, we can build time-sensitive and seasonal personalization without code changes.

store.surferinfo.hour store.surferinfo.month store.surferinfo.day
Example: Morning users (before 2pm) see "Order today, visit today" urgency messaging. Evening users see "Schedule for tomorrow morning." Summer months surface allergy panels; winter months push flu and respiratory tests. Seasonal health content is a natural fit for this signal.
4

Device-Specific Component Variants

Device type, category, OS, and screen resolution are all in the store. Worth noting: many device-based changes can be handled with just CSS/JS media queries — Context Hub isn't needed for simple responsive layout. Where Context Hub adds value is when device is combined with other signals (mobile + first-time + hesitant) or when we're swapping entirely different content, not just reflowing a layout.

store.surferinfo.device.category store.surferinfo.device.type best as compound signal
Example: Device alone = CSS. But mobile + anonymous + evening = Context Hub. That compound signal serves a completely different "What happens next" checkout component — not just a responsive reflow, but different content, different trust signals, different CTA. Use device.category for targeting (not isMobile, which has shown unreliable results in testing).
5

Logged-In vs. Anonymous Targeting

The profile store has an authorizableId field — "anonymous" for unknown users, a user path for logged-in users. HIPAA limits what profile data we can access, but the logged-in signal alone is powerful.

store.profile.authorizableId store.profile.displayName
Example: Anonymous users see the "Who is this for?" education statement and trust clusters. Logged-in users skip the hand-holding and see a streamlined "Reorder" or "Continue browsing" experience instead. We know they're logged in — we just can't see who they are.
6

Behavioral Signals via Cookie Tracking

The pattern: custom JS sets a cookie when a user takes an action (clicks a link, scrolls to a point, views a product). A custom script segment in Context Hub reads that cookie and resolves it into a segment. Key detail: each behavior we want to track needs its own JS + segment wiring — it's not automatic event capture. But once wired, the segment persists across pages via the cookie.

store.segmentation.segments[] custom JS → set cookie custom script segment → read cookie
Example: User clicks into "Men's Health" category → JS sets a cookie category_interest=mens_health. On the next page (All Products), a custom script segment reads that cookie and fires. The product listing Experience Fragment swaps to show men's health tests first. Each category needs its own cookie + segment mapping, but the pattern is repeatable.
7

Browser & Platform Awareness

Browser family, version, and OS are in the store. Our POC already includes a working "Chrome vs. not-Chrome" segment that swaps both text and images on the page.

store.surferinfo.browser.family store.surferinfo.browser.version store.surferinfo.os.name
Example: Apple users (Safari / iOS) see "Add to Apple Health" messaging where relevant. Android/Chrome users see "Download your results" instead. Low-value on its own, but powerful when stacked with other signals.

These stack.

The real power is combining signals — mobile + first visit + evening + allergy season = a very specific experience tailored to that exact context. Each signal above is a building block. Context Hub resolves them all on every page load, and segments can use AND/OR compound conditions. Start with single-signal tests, then layer as we learn which combinations matter.

Constraints to Know

Per-page configuration

Context Hub personalization is configured on a per-page basis. If we want the same personalization on 10 pages, we configure it 10 times. Experience Fragments help — configure the fragment once, reference it across pages — but the targeting rules themselves still need to be set up per page. This means rollout should start with the highest-traffic pages (PDP, checkout, homepage) rather than trying to go site-wide.

Audience setup overhead

Each targeting condition needs a discrete audience or segment built in AEM. Geo-targeting "Charlotte metro" is one audience; "Raleigh-Durham" is another. Behavioral segments each need custom JS + cookie + script wiring. External data reads map one data point at a time. None of this is hard — but it's manual, and the setup scales linearly with the number of conditions we want to target. Worth planning for in scoping.

8

Recommended First Moves

Four scoped applications we can build now — each one proves a pattern, delivers immediate value, and ladders into the broader strategy.

1

Logged-In vs. Anonymous Homepage

Low Complexity

The simplest, clearest signal we have. Logged-in users get a streamlined experience focused on reordering and quick access. Anonymous users get education, trust signals, and "how it works" guidance.

This is a single segment (authorizableId), one page (homepage), and component-level text/image swaps. We can have it running quickly and it immediately demonstrates personalization to stakeholders.

Signal
Logged-in vs. anonymous
Page
Homepage
What Changes
Hero headline, featured section, CTA text
2

Seasonal Product Spotlight via External Data

Low Complexity

An external data feed controls which seasonal category gets featured — allergy panels in spring, flu tests in fall, STI awareness in April. Marketing updates the data source; the homepage or PDP hero swaps automatically.

Proves the external data integration pattern. Zero deploys, marketing-controlled, and visually obvious to anyone watching the site. Great for demonstrating the value of Context Hub to leadership.

Signal
External API / JSON feed
Page
Homepage or category landing
What Changes
Hero banner, featured products Experience Fragment
3

Time-of-Day Checkout Messaging

Low Complexity

Morning users see "Order now, visit a PSC today" urgency. Evening users see "Schedule your visit for tomorrow morning." Directly addresses the checkout hesitation we've already identified as a major leak.

No dev caveats on this one — time-of-day is a clean, native signal. It's a focused test on one high-impact page (checkout) with a clear conversion metric to measure against.

Signal
Hour of day
Page
Checkout
What Changes
"What happens next" guidance, CTA copy, urgency framing
4

Category Interest Carry-Through

Medium Complexity

User browses "Men's Health" → cookie is set → when they navigate to All Products or return later, the product listing prioritizes men's health tests. The experience remembers what they care about.

This one requires custom JS to set the cookie and a custom script segment to read it. Slightly more wiring than the others, but it proves the behavioral tracking pattern that unlocks the comparer/hesitator targeting in our broader strategy.

Signal
Cookie (category page visit)
Page
Products listing
What Changes
Product order, featured carousel Experience Fragment

Each one is small enough to scope, tangible enough to demo, and ladders into the full strategy.

We don't need to approve "Context Hub as a concept" — we approve these 4 builds, prove the patterns work, and expand from there.