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

Marketing Technology

MarTech Tool Categories

The marketing technology landscape is large, but it is organised into a handful of categories that each do a recognisable job. This hub explains why the landscape has grown, introduces the core guides on categories and evaluation, adds further guides on tool requests, renewals, licences, retiring a tool, tool outages, hiring a technology partner and the choice between a suite and best-of-breed tools, maps where categories overlap and sets out the procurement basics that keep a purchase from becoming a regret.
SectionbeginnerUpdated

Learn this as a path

Prefer a guided order? This learning path reads pages from this section in sequence, with exercises and checkpoints.

In this section

The landscape and why it is large

The annual marketing technology landscape compiled by chiefmartec.com has grown for over a decade and now groups thousands of products into a small number of top-level categories: advertising and promotion, content and experience, social and relationships, commerce and sales, data, and management. The growth has several causes, and understanding them helps when reading any vendor map.

Marketing touches every channel, and each channel spawns its own tools as it matures. Software is cheap to build and distribute, so a narrow problem attracts a specialist product rather than waiting for a suite to add a feature. Large platforms expose programming interfaces that make it easy to build a tool on top of them, and each platform's ecosystem grows its own category of helpers. And marketing budgets are large and distributed across many teams, so there are many buyers for many narrow tools.

The practical consequence is that a category can hold hundreds of products that overlap heavily, and that the differences between them matter less than whether any of them fits the stack it would join. Reading the landscape is useful for learning what categories exist and what each does; it is not a selection method. The marketing technology hub sets out the stack as a system, and the stack design is what turns a category into a requirement.

Categories, evaluation: the core guides

The core guides are the map and the method.

MarTech categories explained is the map. It walks through the major groups, explains what each category does in the stack and which layer it serves, and shows where categories overlap and merge. It includes the tool ecosystem explorer, which lists the tools this site documents by discipline, as an inventory rather than a ranking. Read it to learn the vocabulary and to place a product someone has mentioned.

Choosing and evaluating tools is the method. It starts from requirements written as use cases, builds a scoring table from criteria the stack design supplies, runs a proof of concept with the business's own data, checks integration and data handling before features, and ends with a decision record that explains the choice to whoever inherits it. Read it before any selection, and before any renewal that is more than a formality.

The marketing stack section is the other half of the picture: it decides which layers need a tool, and this section explains how to fill them. The marketing automation hub covers in depth the category that most teams buy first, and the marketing tools resource lists the tools the site documents across all of them.

Further guides

Further guides follow a tool through its life in the stack, from the request that brings it in to the reviews that keep it, the partner who helps run it, the day it stops working and the retirement that takes it out, with a comparison for the choice between one suite and specialist tools:

Overlaps and consolidation

Categories overlap because vendors grow into adjacent ones. An email platform adds automation and becomes a marketing automation platform; a marketing automation platform adds a customer database and starts calling itself a customer data platform (CDP); an analytics tool adds experimentation; a customer relationship management system adds email. The result is that most stacks hold several tools that can do the same job, and the question is which should.

OverlapWhere it showsHow to resolve it
Email platform and marketing automationBoth send campaigns and run sequencesPick one as the system of action for messaging; the other sends nothing
Marketing automation and customer data platformBoth hold profiles and build segmentsDefine segments in the data layer; automation consumes them
Customer relationship management and automationBoth score leads and track stagesStages live in the record of people; scoring feeds it, never duplicates it
Analytics and experimentationBoth report conversion by variantExperimentation reports its tests; analytics reports the business
Tag manager (GTM) and platform tagsBoth can deploy the same pixelAll tags through the manager; hard-coded tags are exceptions with dates
Business intelligence and platform reportingBoth produce dashboardsDefinitions in the metrics layer; platform reports for operations only
Survey, chat and review widgetsEach wants a tag and a customer listOne per job, each reviewed, each scoped to the pages that need it

Consolidation is the deliberate removal of the overlap, and it is a project rather than a decision. For each overlap, pick the tool that keeps the job, move its integrations and data to the governed flow, migrate what the other tool held, and retire it with its tags and its contract. Consolidation works best when it follows the stack design rather than the renewal calendar, because the design says which tool should keep the job and the calendar only says which contract is up next.

Whether one broad tool or several specialists should keep the jobs is the question the suite versus best-of-breed comparison works through, layer by layer. The retirement tutorial covers the last step of consolidation: finding every dependency, exporting what must be kept, switching off, removing access and giving notice with a deletion request.

Procurement basics

Most tool regrets are procurement failures rather than product failures. A few basics prevent most of them.

Buy against written requirements, and keep them with the contract; a renewal conversation a year later should start from whether the requirements were met, not from the vendor's roadmap. Know the total cost: the licence, the implementation, the integration work, the training, the data costs it adds and the time of the owner who will run it. Negotiate the terms that matter later: data export on exit, deletion on termination, who owns the configuration, notice periods and the price at renewal rather than only the price at signing. Confirm the security and privacy position before the trial, not after, because a tool that fails the review after the team has built on it is a sunk cost argument waiting to happen.

Name the owner before signing, with administrative access in the organisation's hands rather than an agency's or an individual's personal account. And record the decision: what was chosen, against which alternatives, for which reasons, with which known gaps. The choosing and evaluating tools guide covers the decision record, and the KPI the tool is expected to move should be in it, so that the renewal can be judged.

The further guides turn these basics into routines. The intake guide gives every tool request one route in and triages it against the tools already owned, the licence review compares what each tool bills for with what is used, and the renewal tutorial turns a renewal into a decision made before the notice date.

Illustrative example — not a real result

A charity consolidates its messaging tools

A fundraising charity with a marketing team of four finds it is paying for three tools that send email: a newsletter platform used by communications, a marketing automation platform used by fundraising and the email module of its donor database used by the supporter care team. Together they cost about £1,900 a month, hold three different lists of the same 86,000 supporters and send a combined average of 5.3 messages per supporter per month with no shared suppression. The team writes the messaging use cases, finds that the automation platform meets 19 of 21, and keeps it. The newsletter list is migrated with its consent records, the database's email module is switched off and its contract reduced, and a single suppression rule caps messages at one per supporter per week. Monthly cost falls to around £1,100 and unsubscribes fall by about a third in the following quarter.

Common tool problems

Tool problems usually present as something else: a campaign that cannot be built, a report that does not match, a bill nobody can explain. The table maps the common ones to the guide that helps.

SymptomUsual causeGuide
Nobody can explain what a tool is forBought without a written use caseChoosing and evaluating tools, Handling requests for new tools
Two tools do the same job for different teamsOverlap never resolved; stack grown by purchaseMarTech categories explained
A tool cannot get the data it needsIntegration checked after purchase, not beforeChoosing and evaluating tools
A category someone mentioned is unfamiliarVocabulary, not a gapMarTech categories explained
A renewal arrives and nobody knows whether to signNo decision record and no success measureChoosing and evaluating tools, Reviewing a tool before renewal
The stack design says a layer needs a toolSelection within a categoryThe marketing stack, then Choosing and evaluating tools
A supplier's tool goes down and forms, sends or campaigns stop with no planNo fallback for the jobs the tool does; nobody named to confirm the cause and tell peoplePreparing for a marketing tool outage
An agency or consultant configures tools and the business cannot check or reverse what was doneAccounts, credentials and records left in the partner's hands; no way to test the workHiring and evaluating a marketing technology partner

The marketing technology hub is the starting point for the stack as a whole; this section is where the individual choices are made.

Terms used on this page

Sources

  1. Marketing technology landscape — chiefmartec.com

Related