Case Study · Customer Data Platform

Replacing inflated visitor counts and third-party scripts with one server-side profile.

Optum's web data collection ran through Adobe Launch and dozens of third-party scripts, inflating visitor counts, hurting SEO, and leaving online and offline data unable to meet.

Role Led the migration — data modeling, XDM schema design, and server-side go-live on Adobe Experience Platform

2018-2020 XDM schemas for page views & interactions Server-side event processing Adobe Launch → AEP FB & Google server-side conversions

A unified customer profile across online, offline, and third-party data

Optum needed a single customer profile that could be targeted across CRM, campaign, DMP, and optimization tools — something the existing client-side setup couldn't support.

CAPABILITY

One profile, every source

Build a unified customer profile combining traits from online, offline, and third-party sources into a single addressable record.

3 sources = currently 3 disconnected views of the same person
VENDOR LIMITS

Client-side tools hit a wall

Browser privacy measures increasingly blocked third-party scripts, breaking the data collection that vendor tag managers relied on.

Browser privacy = vendor tags stop firing
WHY IT MATTERS

Journeys stayed fragmented

Without a unified profile, online and offline behavior couldn't be analyzed together to optimize the customer journey.

Online ≠ offline = journey can't be optimized end to end

Third-party scripts were quietly costing reach and rank

Three separate symptoms — duplicated visitors, slower pages, and siloed data — all traced back to the same client-side scripts.

MEASUREMENT

Inflated unique visitors

The same visitor was counted across multiple data sources for different products, distorting reach and audience numbers.

Multiple sources = reach numbers overstated
SEO

Third-party scripts hurt page rank

Dozens of third-party scripts loading client-side slowed pages and dragged down SEO rank, search impressions, and click-throughs.

N+ scripts = slower pages, fewer search clicks
JOURNEY

Online and offline data couldn't meet

There was no way to analyze online and offline behavior together, blocking journey-level optimization.

Online ≠ offline = no combined journey view

Model the data, stand up the CDP, migrate server-side

The team modeled current data as contracts, stood up Adobe Experience Platform with XDM schemas, then moved collection from client-side scripts to server-side processing.

1
Data model & contracts current state → schema

Created a data model and contracts for current data as the foundation for the new platform.Data modeling · contracts

2
CDP with XDM schemas

Set up the CDP on Adobe Experience Platform with XDM schemas covering page views and all interaction events.AEP · XDM schemas

3
Specs & application changes

Wrote specs and worked with developers to update application code for server-side data collection.Server-side collection

4
Migrate & go live

Migrated data collection from Adobe Launch to server-side and went live, removing third-party scripts from the client.Adobe Launch → AEP · go-live

Cleaner pages, a unified profile, server-side ad signal

0
Third-party scripts
Client-side processing eliminated
↑
Page rank & impressions
SEO and click-throughs improved
FB+G
Server-side ad events
Facebook & Google conversions
1
Targetable profile
CRM · Campaign · DMP · Optimization

From three disconnected sources to one targetable profile

⚡

A single addressable customer profile

Optum gained a unified profile built on AEP with XDM schemas that can be targeted across CRM, campaign, DMP, and optimization tools — combining online and offline signals for the first time.

✕

Third-party scripts removed

Eliminating client-side third-party processing improved page rank, search impressions, and click-throughs.

⤳

Server-side ad measurement

Events now process server-side for Facebook and Google, restoring signal lost to browser privacy controls.

Let's talk

Tackling something like this?

Tell me your biggest data or AI bottleneck and I'll send you how I'd approach it — the same way I worked this problem. No résumé dump, no pitch. Just a useful conversation.

Start the conversation →