Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Technology › MarTech Tool Categories

MarTech Categories Explained

The marketing technology categories explained: advertising and media, content and experience, social and relationships, and commerce and sales.
Guidebeginner11 min readUpdated

How the landscape is organised

The most widely used map is the annual marketing technology landscape from chiefmartec.com, which groups thousands of products into six top-level categories: advertising and promotion, content and experience, social and relationships, commerce and sales, data, and management. Each top-level group holds dozens of sub-categories, and products are placed by their primary job even when they do several.

The map is a taxonomy of the market, not a design for a stack. Its value is vocabulary: when someone says a tool is a customer data platform, a demand-side platform or a digital asset manager, the map says what job that implies and which neighbours it has. Its limit is that the categories describe what vendors sell, not what a business needs, and the two are not the same. A stack is designed from use cases mapped to layers, which the designing a marketing stack guide covers; the landscape is consulted when a layer needs a tool and the team wants to know what kinds exist.

A second way to organise the same products is by the layer of the stack they serve: collection, data, decisioning, activation or measurement. The two views cross. Advertising tools are mostly activation with some measurement; data tools are mostly the data layer; management tools serve no layer directly but organise the work. This guide uses the market's categories as its headings and notes the layer each serves, so that the two views can be read together.

Categories

The table gives the major categories, the job each does, the layer it serves and the questions that decide whether a business needs one.

CategoryJob in the stackLayerNeeded when
Advertising platforms and buying toolsBuy and serve paid media across search, social, display, video and retail media; demand-side platforms (DSP) for programmaticActivationPaid acquisition is a channel
Ad serving, verification and measurementServe creative, verify delivery, measure reach, viewability and liftMeasurementSpend is large enough that verification pays
Search and content optimisationResearch keywords, audit sites, track rankings, optimise contentDecisioning, measurementOrganic search matters
Content management and experiencePublish and manage web content, digital assets, personalisation, experimentationActivation, decisioningAlways, in some form
Email, messaging and marketing automationSend messages and run sequences by behaviour and stageDecisioning, activationAlways, once there is a list
Social management and listeningSchedule, publish, engage and monitor across social networksActivation, measurementOrganic social is a channel
Customer relationship managementHold the record of people, accounts and deals; manage sales stagesData, activationAlways, as the record of people
Commerce platforms and marketplace toolingRun the store, catalogue, checkout and feedsData, activationSelling online
Tag management and collectionDeploy tags, expose the data layer, send events server-sideCollectionAlways
Analytics and attributionRecord behaviour, report, attribute, test incrementality; web analytics (GA4)MeasurementAlways
Data platformsWarehouse, customer data platform (CDP), data management platform (DMP), consent management, data qualityDataSeveral sources must be joined; several channels share segments
Business intelligence and reportingModel definitions, build dashboards, distribute reportsMeasurementReporting outgrows platform exports
Management and collaborationPlan work, manage projects, budgets, approvals and agile boardsNone directlyTeams coordinate across people and agencies

The explorer below is a different kind of list. It shows the tools this site documents, grouped by the discipline each serves, with the category each belongs to and the pages that refer to it. It is an inventory of what the site covers, filterable by discipline, and not a ranking or a recommendation; its purpose is to let you see which categories the site's guides touch and to find the pages that go deeper on a tool you already use.

Marketing tool ecosystem

Advertising and media

Advertising technology is the oldest and most structured part of the landscape, because paid media involves buyers, sellers and intermediaries who need to transact at scale. On the buy side are the advertising platforms themselves, each with its own interface for search, social, video or display inventory, and the demand-side platforms that buy programmatic inventory across many publishers through real-time auctions. On the sell side are supply-side platforms and exchanges that make publisher inventory available to buyers. Between them are ad servers that hold the creative and record delivery, verification tools that check ads were viewable and brand-safe, and measurement tools for reach, frequency and lift.

The programmatic ecosystem guide explains how the buy and sell sides fit, and the platform hubs on this site cover each buying platform's mechanics. From the stack's point of view, advertising tools are activation with a measurement loop: they consume audiences and conversions from the data layer and return delivery and performance data to it. The two integration questions are how audiences reach the platform (uploaded lists, server-side matching, platform pixels) and how conversions come back (browser tags, server-side conversion interfaces, offline imports). Both are covered in the data flow guide.

Adjacent to buying are the creative and promotion tools: creative management platforms that produce variations at scale, affiliate and partner platforms that track and pay for referred sales, and the public relations and influencer tools that manage earned and paid relationships. They are smaller categories with the same shape: activation tools that need audiences in and results out.

Content and experience

Content and experience tools build and serve what people see when they arrive. At the centre is the content management system, which publishes the site, and around it are the tools that extend it: digital asset management for images, video and brand files; experimentation platforms for testing variants; personalisation engines that choose content by segment or behaviour; search and content optimisation tools for organic visibility; video hosting and interactive content; and the forms, landing page builders and chat tools that capture and converse.

The category serves two layers. Publishing and serving are activation: the page is a channel. Experimentation and personalisation are decisioning: they choose what to show. The distinction matters for governance, because a personalisation rule is a decision that should be defined where the business can see and change it, not buried in one tool's interface. The conversion rate optimisation section of this site covers testing and landing pages as practice; this guide only places the tools.

The integration questions for content tools are the data they need to decide (segments and behaviour from the data layer) and the events they emit (views, interactions, variant exposures) so that the measurement layer can report on them. A personalisation engine that cannot read the stack's segments builds its own, and an experimentation tool that does not emit exposures to analytics produces results nobody can reconcile.

Social, relationships, commerce and sales

Three categories deal with people the business already knows or is in conversation with.

Social and relationships covers social media management (scheduling, publishing, community engagement), social listening and monitoring, influencer and advocacy platforms, and the customer relationship management system itself, which the landscape places here because its job is the relationship. In the stack, the customer relationship management system is the record of people: the place where a contact, an account, a deal and its stage are held, and the source of truth that marketing's view of a customer should reconcile to. Social tools are activation and measurement for the organic social channel. Email, messaging and marketing automation sit nearby: they send messages and run sequences driven by behaviour and stage, and they are the activation and decisioning tools most teams buy first after analytics. The marketing automation hub covers that category in depth.

Commerce and sales covers the commerce platform (store, catalogue, checkout), the feed and marketplace tools that syndicate products to shopping channels, sales enablement and engagement tools, and retail and point-of-sale systems. The commerce platform is both a data source (orders, products, customers) and an activation surface (the store itself), and for a retailer it is usually the system of record for revenue, which makes it the source every other number is reconciled against.

The relationship categories share one integration question above all: identity. A social tool knows a handle, the customer relationship management system knows an email address and an account, the commerce platform knows a customer id and an order. Joining them is the data layer's job, and the designing a marketing stack guide treats it as a design requirement rather than a feature.

Data and analytics

Data and analytics tools are the layer that makes the rest a system. Collection tools (tag managers, server-side tagging, software development kits) capture events. Data platforms store and govern them: the warehouse for history and joins, the customer data platform for profiles and activation, consent management for what may be used, data quality tooling for whether the feed can be trusted. Analytics tools record behaviour and report it; attribution and incrementality tools estimate what caused what; business intelligence tools model definitions and distribute dashboards.

The category has changed more than any other in recent years. The data management platform, built for cookie-based advertising audiences, has lost most of its role as third-party cookies have become unreliable; the customer data platform and the warehouse have taken on first-party audience work; server-side collection has grown as browser collection has become less complete; and consent management has become a standard component rather than an add-on. The direction is first-party, consented, governed data in a store the business controls, activated through server-side connections.

The distinction between analytics and business intelligence is worth knowing, because it decides which tool answers which question. Analytics reports what happened on the site and in campaigns in the vendor's model; business intelligence reports the business's own definitions across every source. The reporting versus business intelligence guide draws the line, and the reporting and business intelligence section covers the practice.

Illustrative example — not a real result

A regional bank maps its tools to categories

A regional bank's marketing team inventories 38 tools and places each in a category. Advertising and media holds 9 (four platform accounts, a demand-side platform, an ad server, a verification tool, a creative management platform and an affiliate network). Content and experience holds 8, including two experimentation tools bought by different teams. Social and relationships holds 7, with two social scheduling tools and the customer relationship management system. Commerce and sales holds 3. Data and analytics holds 9, including a data management platform with a contract of £3,100 a month that has not pushed an audience in 14 months since the bank moved to first-party lists. Management holds 2. The exercise surfaces five overlaps and one orphan, and the team retires the data management platform and one experimentation tool at their next renewal, saving about £4,700 a month, and consolidates social scheduling the following quarter.

Where categories overlap

Categories overlap because vendors expand into adjacent jobs, and the overlaps are where most stack confusion lives.

Marketing automation and the customer data platform both hold profiles and build segments. The useful division is that the data layer defines segments and the automation tool acts on them, but many automation vendors sell their profile store as a customer data platform and many customer data platforms add messaging. Choose one place for the definition and treat the other as a consumer.

Customer relationship management and marketing automation both track stages and score leads. The record of people holds the stage; scoring feeds it from the automation tool; neither duplicates the other's job. Where the same vendor sells both, the overlap is usually resolved by the vendor; where it does not, it is resolved by the stack design. Whether to take both jobs from one suite or a specialist tool for each is weighed criterion by criterion in the comparison of a marketing suite with best-of-breed tools.

Analytics and experimentation both report conversion by variant. The experimentation tool reports its tests with its own statistics; analytics reports the business with the vendor's model; business intelligence reconciles both to revenue. Each is right about its own question.

Advertising platforms and data platforms both build audiences. The platforms build them from their own signals and from what they are given; the data layer builds them from first-party data and sends them. The direction is that governed audiences come from the data layer and the platforms' own audiences are used alongside, not instead.

Tag management and platform tags both deploy pixels. All tags should go through the manager, with hard-coded tags as dated exceptions, which the tag governance guide covers. The tool categories hub has a table of the common overlaps with the resolution for each.

The two data platforms most often confused are set side by side in the CDP versus DMP comparison, which explains why the balance between them has shifted.

Common mistakes

  • Reading the landscape as a shopping list. It is vocabulary; the stack design says which categories the business needs.
  • Placing a tool by the vendor's label. A tool called a customer data platform may be an automation tool's profile store; place it by what it does in the stack.
  • Buying a category because competitors have one. The needed-when column in the table is the test; a tool without a use case is a cost.
  • Ignoring the overlaps. Two tools in one cell of the stack is a decision deferred, and it costs money and reconciliation time every month.
  • Treating adtech and martech as separate worlds. They share audiences and conversions through the data layer; the integration between them is where performance is won.
  • Confusing analytics with business intelligence. Each answers a different question; expecting one to do the other's job produces reports nobody trusts.

Frequently asked questions

What is the difference between adtech and martech?

Adtech is the technology for buying, selling and measuring paid media: demand-side and supply-side platforms, ad servers, exchanges and verification. Martech is the broader set that includes adtech alongside content, relationships, commerce, data and management tools. In practice the line is blurred, because advertising platforms now hold customer data and customer data platforms now push audiences to advertising; the useful distinction is whether a tool's job is reaching people you do not yet know or acting on people you do.

Is a customer data platform the same as a data management platform?

No, although they overlap in purpose. A data management platform was built for advertising audiences, historically on third-party cookies and anonymous segments, and shares them with buying platforms. A customer data platform holds first-party profiles of known people, resolves identity across sources and activates to any channel. As third-party cookies have become unreliable, the data management platform's role has shrunk and the customer data platform has taken on much of the audience work with consented first-party data.

Do suites or best-of-breed tools make a better stack?

Neither by default. A suite trades depth in each category for integration between its modules; best-of-breed trades integration work for depth. The right mix depends on which categories matter most to the business and how much integration capacity it has. Most stacks end up hybrid: a suite or platform at the centre where integration matters most, specialist tools where depth matters, all connected through a governed data layer.

Terms used on this page

Where this page is used

Part of these learning paths

Also related

Sources

  1. Marketing technology landscape — chiefmartec.com

Related