Marketing technology stack

A marketing technology stack is the set of tools a marketing team actually runs, plus the connections between them: where each record is created, which system it flows to, and which one holds the version everyone trusts. It is an inventory, not a plan.

Martech is simply the short word for marketing technology, so this page and martech stack strategy name the same object from opposite ends. Read this one for what you have and how it fits together. Read that one for what to buy, keep or kill.

Keep the two apart in your own head as well. The moment a stack review turns into an argument about renewals, you have started doing strategy, and the inventory stops being accurate.

Key takeaways

• A stack is described by job and by data flow, not by vendor logos.
• Every object needs one nominated record of truth, written down.
• The connections are the stack; tools alone are just a shopping list.
• Removing a tool reveals what quietly depended on it.

How it works

A stack is best described in layers by job rather than by brand. Each layer captures or acts on data, hands it to the next, and one system in the chain is nominated as the record of truth for each object.

The record of truth is a choice — name one system per object and write it down. Without that line, two tools will hold two versions of the same contact and both will look authoritative on a report.

Connections do the real work. The handoffs between tools are where business process automation (BPA) shows up inside marketing, usually as a sync that nobody remembers building.

Add models to those handoffs and you have intelligent automation; extend the same approach across every process in the business and you have hyperautomation — both describe what a stack can do, not which tools you own.

Teams with an outbound calling motion also run computer-telephony integration (CTI), which ties the dialler to the contact record so a call lands in the same history as an email.

Briefing and approval traffic usually lives outside the marketing tools entirely, in chat and shared documents, which makes collaboration platform strategy part of the map even though no marketer bought it.

A stack is also a map of personal data. The Federal Trade Commission’s small business guide tells firms to inventory the information you have by type and location, including records held by contractors running a call centre.

Tools arrive one at a time — that is how overlap happens. Microsoft’s cloud adoption guidance treats the security and operational risks of ad-hoc adoption as a portfolio-level problem, which is precisely what an unmapped stack becomes.

Examples

Stacks differ by business model rather than by budget. Three shapes come up repeatedly, and in each one the interesting part is which system holds the record of truth and what passes between the layers.

A business software firm. Forms feed an automation tool, which scores contacts and pushes them to the CRM. The CRM owns the account record, analytics owns sessions, and a warehouse joins the two so one report can show spend against closed revenue.

An online retailer. The store platform owns the customer and the order, so marketing tools read from it rather than holding their own list. Email, advertising audiences and loyalty all sync outward from that single record.

A franchise network across several markets. A central content system publishes local pages, each market runs its own advertising accounts, and a shared data store reconciles currency, language and local lead definitions before anything is reported upward.

Removing a tool is the honest test of a stack — you find out what quietly depended on it. Pull the scheduler and three reports stop counting, which is one reason an incoming agency asks for a stack map before its first campaign.

Related terms

These terms describe parts of the same technical picture, or the places a stack touches the rest of the business. None of them replaces the inventory itself, and none of them makes the buying decisions.

• Automation center of excellence: the central team that sets standards for the automations connecting these tools.
• Digital marketing outsourcing: handing execution to a provider who will need this map on day one.
• Business process automation (BPA): the rule-based handoffs that move records between layers.
• Intelligent automation: the same handoffs with judgement added by a model.
• Computer-telephony integration (CTI): the link between voice channels and the contact record.

FAQ

What belongs in a marketing technology stack?

Anything that creates, stores or acts on marketing data, including tools nobody in marketing bought. A shared drive holding campaign assets counts if a report depends on it.

How many tools should a stack have?

There is no right number, and the count is a poor measure anyway. What matters is whether every tool has an owner, a job no other tool does, and a known place in the data flow.

What is the record of truth?

It is the single system nominated as authoritative for a given object, such as the contact or the account. Other systems may hold copies, but only one version is reportable.

Who maintains the stack?

Usually marketing operations, sometimes with a technical owner per tool. Shared ownership works when it is written down, and fails quietly when it is assumed.

How is a stack different from martech stack strategy?

This page describes the state: the tools, the connections and the data flow. A martech stack strategy decides what to buy, consolidate or retire, and who pays for each line.

Find agencies and providers that will work inside your existing stack in the Outsource Accelerator provider directory.