Homepage personalization — build tracker

The approved homepage adjustments, split by what needs dev and what doesn't

Jane has approved moving forward with the homepage adjustments. This tracker splits them into two lanes: No-Dev items Jacqueline can author and publish herself, and Build items that run on the Target ↔ ContextHub pipeline. The plumbing for the Build lane is now proven, so the remaining work is content and QA — not feasibility.

✓

Pipeline proven — Target can read ContextHub

Trone and Jacqueline built a working proof-of-concept on New vs. returning messaging. That was the one hard question; with it answered, every Build-lane item below is a matter of authoring the experience and QA'ing it, not proving it's possible.

No-Dev Authoring only — Jacqueline can build & publish, no dev time
Build Targeted / personalized — runs on the proven Target pipeline
i

Ownership model: mostly self-serve

The POC lets Target read whether any named ContextHub segment is satisfied — so no dev is needed as long as the segment exists and Jacqueline knows its name. She builds the audience and content swap in Target herself. Dev is only required to (a) build a new custom segment/audience, and (b) get the mechanism living in OD's codebase (see open items). Beyond that, this is ContextHub coaching for the team — not ongoing dev.

No-Dev — can start now; only needs final copy & assets from OD
ItemToolOwnerStatusNext step / needs from OD
Personal Wellness Program promo card
Default merchandising block shown to everyone — no targeting.
Authoring Jacqueline
(self-serve)
Ready to build Final card copy + image/CTA from Jane/OD. Confirm placement on the homepage.
General homepage content reorder
Fixed merchandising order of homepage sections — same for all visitors.
Authoring Jacqueline
(self-serve)
Scope pending Confirm with Jane the exact section order. (If it should reorder per user, it moves to the Build lane — see #6 below.)
Build — personalized; pipeline proven, needs audience + variant content built and QA'd
ItemToolOwnerStatusNext step / needs from OD
01New vs. returning welcome-back
Welcome-back cues / "pick up where you left off" for returning visitors.
Target Jacqueline (led POC)
dev to land in OD code
✓ POC proven Proven on labcorp.com; needs the mechanism moved into OD's codebase, then build welcome-back variants + QA. Needs: returning-visitor copy from Jane.
06Category-interest reorder (top row)
Reorder the top row of tests by the category type a visitor has shown interest in.
Target Jacqueline (self-serve)
dev only to build the segment
Ready to build One-time dev to build the category-affinity segment; then Jacqueline self-serves. Map each category → which tests surface. Needs: content/priority rules from Jane.
07Seasonal / campaign banner
Date-driven homepage banner — flu season, back-to-school, New Year wellness.
ContextHub Jacqueline
(self-serve, likely)
Ready to build Needs: seasonal calendar + banner creative from Jane/OD. Low lift, date-based.

Open items to confirm

Three things to nail down before the build lane is fully scoped — none are blockers, they just set ownership and expectations.

Recommended sequence

  1. Lock the list in writing. Confirm the exact homepage cards/sections changing, each tagged No-Dev or Build.
  2. Get Joe's ownership line. Self-serve vs. dev for the Build items — sets timeline and budget honestly.
  3. Collect content from OD/Jane. Copy, assets, and audience rules for every item. Start this early; it gates everything.
  4. Ship the No-Dev lane first. Wellness card + reorder go live quickly for a visible win while the Build items are authored.
  5. Build, QA, and roll out the Build lane on the proven pipeline, one experience at a time.