Knowledge base
What is MarTech? A map of the customer-engagement stack
Marketing technology is just the set of software a company uses to find, understand, and talk to its customers. The jargon hides a simple shape: collect data, unify it, decide what to say, and deliver it. This is the map.
6 min read · Updated June 28, 2026
The problem MarTech solves
Every team that touches the customer collects its own data and sends its own messages. The website, the mobile app, the email tool, the support desk, and the ad platforms each hold a partial, slightly different view of the same person. The result is the familiar mess: the same customer gets a "welcome" email the week after they bought, a push notification for an item they already returned, and a discount for a plan they already pay for.
MarTech is the stack of tools that fixes that by doing four things in order: collect customer data from everywhere, unify it into one view per person, decide what each person should receive, and deliver it on the right channel at the right time. Most products you hear named (CDP, ESP, iPaaS, journey builder) are specialists in one of those four jobs.
The four layers
It helps to read any martech stack as four stacked layers, with data flowing up from the bottom.
- Data layer (collect and unify). Where customer data lands and becomes one profile per person. Home of the Customer Data Platform (CDP) and the data warehouse.
- Activation layer (move and decide). The plumbing that pushes unified data out to the tools that act on it, plus the logic that picks an audience. This is where ETL, reverse ETL, and iPaaS live.
- Engagement layer (orchestrate and send). Where a marketer builds the campaign or the multi-step journey and the message goes out over email, SMS, push, or in-app. This is the category Iterable is in.
- Measurement layer (learn). Analytics and experimentation that report what worked and feed the next decision.
The one distinction worth memorizing
The data layer is "data in" (it assembles the truth about a customer). The engagement layer is "data out" (it acts on that truth by sending messages). Tools that blur the two are the source of most stack pain.
Where the platforms fit
A short translation of the names you will hear, mapped to the layer they serve:
| Tool | Layer | One-line job |
|---|---|---|
| CDP | Data | Unify scattered customer data into one persistent profile |
| Data warehouse | Data | Store all company data for analysis (Snowflake, BigQuery) |
| ETL / reverse ETL | Activation | Move data into, and back out of, the warehouse |
| iPaaS | Activation | Wire apps together with real-time workflows |
| Engagement platform | Engagement | Build journeys and send cross-channel messages (Iterable) |
| Analytics | Measurement | Report results and run experiments |
No single vendor owns all four layers well, which is why companies assemble a stack. A modern best practice is to keep a strong data layer and pair it with a best-in-class engagement platform rather than asking one tool to do everything.
Frequently asked questions
Is MarTech the same as a CRM?
No. A CRM (customer relationship management) tool is one part of the stack, usually focused on sales contacts and deal pipelines. MarTech is the broader set of tools across data, activation, engagement, and measurement.
Does one platform do all of this?
Some suites claim to, but in practice companies assemble a stack of specialists. The strongest setups keep the data layer (CDP or warehouse) separate from the engagement layer (the sending platform) so each can be best in class.
Where does AI fit in the stack?
Mostly in the decisioning and engagement layers: predicting the best send time or channel for each person, and generating message copy. It depends on a clean data layer underneath to work.
Keep reading
Sources
Part of the MarTech and customer engagement field notes on this site. Written by Antoni K Pestka.