Back to work
/ 03Cloud Modernization

Customer Data Platform & Event Tracking

Replaced vendor-driven pricing tables with a client-specific unit-economic model that anchored CDP contract negotiations in data — and cleared a migration path off the legacy platform without disrupting existing Adobe-based reporting.

01

20–30% platform-spend savings

Segment contracted against the client's own unit-economic model, not vendor list price.

02

One governed event standard

Three competing inventories consolidated across marketing, data science, and architecture.

03

Spend redirected to signal

Tracking budget shifted from unused events to high-value actions with proven impact.

04

Zero reporting downtime

Executive and merchandising dashboards stay live throughout the platform transition.

The Challenge

The client's existing Customer Data Platform (SAP CDP) had gaps the marketing organization had been working around for years: ambiguous event taxonomy, expensive scaling characteristics as the digital business grew, and a measurement stack split awkwardly between Adobe Analytics, FullStory, and downstream PowerBI dashboards.

Three new CDP vendors — Twilio Segment, Hightouch, and Rudderstack — were in active evaluation, but the client's procurement and architecture teams lacked an apples-to-apples economic model to compare them, and there was no shared definition of the events the next-generation pipeline needed to capture. The marketing organization also needed any migration path to preserve continuity for existing Adobe-based reporting so the business didn't lose visibility while the new platform stood up.

Our Approach

A senior data architect embedded into the data engineering and marketing architecture teams and led the evaluation, negotiation, and design work end-to-end.

We hosted demo cycles with each vendor, pulling SAINT classification rules and event-tracking transformations out of Adobe so the vendors could speak to the client's actual implementation context rather than deliver generic pitches. We built a unit-economic cost breakdown of Segment and Rudderstack against the client's actual MTU and event volumes — giving the procurement team negotiating leverage anchored in real economics rather than vendor list prices.

We then reconciled the marketer-stated priority events against actual consumption signal from Adobe and FullStory, surfacing the gap between what marketers said they needed and what the business actually used, and used that data to clean up a fragmented event inventory across multiple stakeholder groups.

Finally, we finalized fact and dimension tables for the next-generation clickstream pipeline with the data engineering team — designed to preserve compatibility with existing Adobe-based downstream reporting so the migration would not interrupt business visibility.

Engagement Model

One senior data architect, full-time, multi-quarter. Reports into the marketing architecture lead.

Technology
Adobe AnalyticsTwilio SegmentHightouchFullStoryPowerBIMiroGitHub Copilot

Ready to get back to building?

Tell us about the engagement. We typically respond within one business day with a named builder who can talk substance — not a generic sales pitch.

Prefer email? info@inthe.cloud