The previous lesson mapped what a technical marketing department must be able to do. This one is about what it does that with.
One note before the diagram, because the vocabulary overlaps: the Pyramid and the stack both contain something called "activation," and they're not the same thing. The Pyramid describes competencies — activation as a skill. The stack describes infrastructure — activation as a set of running systems. The Pyramid told you what the department must know; this is the machinery it knows it on.
Here's how we draw the stack today. Explore it below — each of the three orbital regions opens up — and then read on.
Three regions, no center
The shape is simple: three regions, connected by data flowing between them — and, the part we'd have drawn differently a couple of years ago, no single platform sitting in the middle that everything else orbits.
For years we'd have put one box in the center and arranged everything around it. What moved us off that is largely the AI era: it didn't blow up the stack or hand us a new one — the core components are the same ones we'd have named a while ago — but it quietly rearranged which parts carry the weight. Today each region earns its place by being good at the one thing it exists for:
- Tracking feeds the other two regions clean, complete, compliant, human first-party data.
- Activation turns that data into personalized experiences, fast, across every channel.
- Storage holds everything cheaply — and has become the layer AI reasons over.
The flow between them is the whole point. Tracking feeds both. Storage and Activation then run a loop: the warehouse is the broad, cheap source of truth; the activation layer is the fast muscle; and data moves back and forth between them as needed.
Region 01 — Data Tracking Infrastructure
In eCommerce, tracking website behavior is essential — and keeping that data complete and clean is getting harder all the time. Tracking-prevention systems erode what would otherwise be captured. Privacy regulation and consent requirements keep tightening, and getting tracking wrong carries real legal and reputational risk. And the AI era brings a flood of bots that artificially inflate traffic; unhandled, analytics quickly become unreliable.
We find it clearer to think about this region as a set of functions rather than a set of logos — the specific tools are secondary; the functions are what has to be covered:
- Collection and routing. A single server-side collection point that captures behavioral data cleanly, owns the anonymous ID in your own infrastructure, and routes each event to the right downstream system.
- Bot prevention. Filtering non-human traffic out at the door, before it pollutes numbers, behavioral data, and lists.
- Identity resolution and list growth. Resolving anonymous visitors to known profiles and collecting as many real email addresses as possible — from actual people, not bots or fake sign-ups.
- Email verification. Keeping invalid and junk addresses out of sends so sender reputation holds up.
This is the least glamorous region on the diagram, and — in our view — the one that now quietly protects the value of everything else. When a human reads a slightly dirty dataset, they squint and adjust. When AI reads it, it produces a clean, fluent, wrong answer and hands it over with total confidence. Clean input is now the thing standing between a team and confidently wrong output. (This is the pyramid's base-tier logic, showing up in the infrastructure.)
Region 02 — Data Activation Infrastructure
This entire region can be covered by a single application: Bloomreach Engagement. It's built around an in-house CDP running on a fast, in-memory database — the kind of speed that's essential when personalization has to resolve within seconds across multiple channels. Website, mobile app, email, SMS, mobile push, and ad audiences are all integrated parts of one platform.
Having one tool instead of six is a major advantage: one data model to maintain rather than six, and none of the pipelines you'd otherwise have to build and keep in sync between separate systems.
What the AI era changed here isn't the platform — it's the cost of feeding it. Two fairly time-consuming asset types, email assets and weblayers, have compressed a lot for us because we've built workflows around Claude that generate them and import them directly into Bloomreach. That's the pattern we flagged at the end of the last lesson, now visible as an actual component: Claude sits on the ring around this region in the diagram.
Region 03 — Data Storage Infrastructure
Data activation needs a very fast database — but that speed costs money. So it isn't advisable to keep full data history in the activation layer; it would quickly become expensive. Instead, a dedicated storage layer — the data warehouse — holds large volumes of data cheaply.
The scope here is also much broader than the CDP. The activation layer is usually the single biggest feed into the warehouse — all the CDP-grade customer data, website behavior, campaign engagement — but inventory, ad spend, and other operational data land in the same place. That breadth is exactly what makes this region so valuable now.
Because this is the region the AI era changed the most. The warehouse used to be the quiet one — a cheaper place to park data that didn't fit in the CDP. It isn't quiet anymore. AI now connects to the warehouse easily, and once it does, producing quality analytical output gets dramatically easier: ad-hoc questions asked in natural language and answered across sources that never sat together before, and the permanent reports we described in the previous lesson — built with Claude Code as HTML, no traditional BI tool required.
We build this layer specifically so that AI can understand and work with the data exceptionally well — which in practice means documentation stops being hygiene and becomes the interface. The model navigates the warehouse the way a new analyst would: by reading what's there.
And the bonus: any of this data can be imported back into the activation layer whenever it's needed. That's the storage–activation loop closing.
Where this course goes next
The department has a skill map and now a machine. What's still missing is the brain that decides who gets which experience — the model of the customer that all this infrastructure serves. In the next lesson we'll introduce the Datacop Atlas, and make the case for why the classic customer journey isn't enough.
Datacop is a fractional, AI-enabled technical marketing department for $25M–$2B eCommerce brands. The Academy is where we write down how we work.