How we move from picking one winner for everyone to delivering the right experience for each user — using tools we already have.
Instead of testing one variant vs. another globally, test which experience works best for each situation.
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:
This maps directly to the pain points we already know about:
Users who stall mid-checkout get targeted reassurance — not the same messaging as someone who's already confident.
Product browsers who compare 3+ items get comparison-focused layouts. Decisive buyers get a streamlined path to cart.
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.
We already distinguish between learning tests and optimization tests. Context Hub makes learning tests dramatically more valuable.
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.
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.
Currently a static statement on the product page. With Context Hub, it adapts.
Show "For first-time testers" — normalizes the experience, reduces anxiety
Show "For ongoing monitoring" — frames around continuity and routine
Show "For specific symptoms" — mirrors their search-driven intent
We've already identified this as a major leak fix. Context Hub lets us serve the right depth of guidance.
Detailed step-by-step reassurance — walk them through the full process with trust signals
Short, frictionless version — just the essentials, no hand-holding
Simplified + visual — icon-driven steps optimized for small screens
Users compare multiple products heavily. Context Hub lets us match messaging to behavior.
Benefit-first messaging — lead with what the test does and why it matters
Comparison-focused messaging — highlight differentiators and "most popular" signals
"Recommended" badges — reduce decision fatigue with curated suggestions
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 product carousel — user clicked into men's health category, so the featured products fragment swaps to match
Default "most popular" carousel — no category signal, show the standard bestsellers fragment
Seasonal health carousel — driven by time-of-year data (allergy season, flu season) via Context Hub date signals
Using Adobe Target + Context Hub, we shift from "pick a winner" to "keep multiple winners, each for the right audience."
Automatically shifts traffic toward the winning variant as statistical confidence builds — faster decisions, less wasted traffic.
Uses machine learning to identify the best experience for each visitor based on their profile — multiple winners coexist.
Once a pattern is validated, promote it to a permanent personalization rule — no manual intervention needed.
Right now the roadmap flows linearly. Context Hub turns it into a compounding cycle.
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.
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 |
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.
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.
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.
The store exposes hour, day, month, and year. Combined with external data feeds, we can build time-sensitive and seasonal personalization without code changes.
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.
device.category for targeting (not isMobile, which has shown unreliable results in testing).
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.
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.
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.
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.
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.
Four scoped applications we can build now — each one proves a pattern, delivers immediate value, and ladders into the broader strategy.
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.
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.
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.
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.
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.