Amir Mousavi

Glossary

MarTech Glossary

Updated · By Amir Mousavi

Marketing technology — MarTech — is the software a team uses to plan, run, measure, and optimize marketing, together with the practices that keep those tools connected and governed. The 2026 landscape counts 15,505 products and has stopped growing for the first time in fifteen years: the buying problem is no longer finding a tool, it is telling overlapping tools apart. That is what this glossary is for.

Each of the 48 entries below has two parts: what the term means, then what to watch for when a vendor uses it — the tell that separates the category from the rebrand. Terms are grouped by stack layer, and every entry has a stable anchor you can cite or share. External facts and dates were verified on August 20, 2026; sources are at the end of the page.

The stack and how it fits together

Marketing technology (MarTech)

The software a team uses to plan, run, measure, and optimize marketing, together with the operating practices — data flows, naming, ownership — that keep those tools working as one system.

The 2026 marketing technology landscape counts 15,505 products, and for the first time in fifteen years the number has essentially stopped growing. The practical consequence: almost every capability now exists in several tools you already pay for, so stack decisions are less about finding software and more about deciding which overlapping tool owns which job.

MarTech stack

The specific set of tools a company runs and the integrations between them, usually described in layers: collection, storage, decisioning, activation, and measurement.

A stack is defined by its data flows more than by its logos: two companies can own identical tools and have completely different stacks because the connections differ. Mapping capabilities and flows before buying anything is the argument of the stack planning guide.

Composable architecture

An approach that assembles interoperable best-of-breed components around shared data — usually a warehouse — instead of adopting one vendor’s integrated suite.

Composable trades licence cost for engineering ownership: every integration a suite would have shipped becomes something your team maintains. You need it when data volume and team maturity justify it; you do not when "composable" is a way to avoid choosing an owner for the glue.

iPaaS (integration platform as a service)

Middleware such as Zapier, Make, or Workato that moves data between tools through prebuilt connectors, without custom code.

Good for edge cases and internal workflows; risky as the core pipe between systems of record. Per-task pricing grows faster than volume, and retries and error handling are opaque exactly where reliability matters most.

API (application programming interface)

The documented surface through which one system reads or writes another’s data — the raw material of every integration.

"Has an API" is where vendor diligence starts, not where it ends. Check that the objects and fields you need are actually exposed, what the rate limits are, and whether the authentication model fits how you deploy — those three points are where martech integrations die.

Webhook

A push notification between systems: instead of being polled, a tool calls a URL you configure the moment an event happens — a form submit, an unsubscribe, a purchase.

Webhooks are usually delivered at-least-once, so the receiving side must handle duplicates, and a webhook that fails silently loses data with no one watching. If a workflow depends on one, monitor it.

Authoritative system (system of record)

The system agreed to win when two tools disagree about a field — the source of truth for that specific piece of data, such as consent, lifecycle stage, or email address.

Authority is per field, not per tool: the CRM can own lifecycle stage while the consent platform owns opt-in status. Most sync problems trace back to two systems that each believe they are authoritative for the same field — the ownership-table exercise in the CDP versus CRM comparison exists for exactly this.

Data collection and measurement

Web analytics

Software that records visitor behavior on sites and apps as events — page views, clicks, conversions — and aggregates them into reports; Google Analytics 4 is the dominant implementation.

Analytics describes behavior on properties you own. It is not a system of record for revenue, not a CDP, and its counts will never match the CRM exactly — reconciliation gaps within roughly five percent are normal attrition from blockers and consent, not bugs to fix.

Event (and event parameter)

The unit of measurement in modern analytics: a named action (the event) with attached details (parameters) — for example a sign_up event carrying a plan parameter.

Naming decides usability: GA4 treats form_submit and Form_Submit as two different events, and a property without a naming convention accumulates parallel events nobody can report on. The conventions that survive contact with real teams are in the GA4 and GTM notes.

Tag management system (TMS)

A tool such as Google Tag Manager that deploys and governs measurement and marketing tags through a managed container, without a code release for every change.

The value is governance, not convenience: versioned changes, preview before publish, and one place to answer what fires where. A TMS without a named owner and a review step drifts into tag soup nobody dares delete.

Data layer

A structured JavaScript object on a page that exposes agreed, named values — page type, user state, transaction data — for tag management and analytics to read.

It is a contract between the site and measurement. The alternative — scraping values out of the DOM — breaks silently on the next redesign. If a tracked value matters, it belongs in the data layer, put there deliberately by the site code.

Server-side tagging

Running tags in a server container you control: the browser sends one stream to your endpoint, and the server forwards events to analytics and advertising platforms.

It buys durability (fewer blocked requests), control over what leaves the browser, and faster pages. It does not create consent — forwarding data a user declined is the same violation with an extra hop — and it means owning infrastructure: a misconfigured server container fails invisibly.

Measurement plan

A document that maps business questions to the events, parameters, and reports that answer them — written before implementation, and used as the acceptance test after it.

The cheapest artifact in analytics and the most skipped. Without one, tracking accumulates by request until hundreds of events serve nobody. The analytics implementation checklist starts here for a reason.

Attribution

Assigning credit for a conversion across the touchpoints that preceded it — last click, first click, or model-based approaches such as GA4’s data-driven attribution.

Every model redistributes credit; none measures whether the marketing caused anything — that is incrementality testing, a different discipline. Attribution answers "compare channels under consistent rules", so read relative movement, not absolute numbers.

UTM parameters

Query parameters (utm_source, utm_medium, utm_campaign and companions) appended to inbound links so analytics can classify the traffic they bring.

They only work as a taxonomy: lowercase everything, document allowed values, and generate links from a shared sheet or tool. Two gotchas cost real data — UTMs on internal links restart sessions, and inconsistent casing splits one campaign into several reporting rows.

Measurement Protocol

GA4’s HTTP endpoint for sending events directly from a server — used for offline conversions, subscription renewals, and other events that never happen in a browser.

Its status is widely misreported. Google has placed the Measurement Protocol in maintenance mode with no plans for deprecation, while recommending the newer Data Manager API for new server-to-server integrations — so existing integrations are safe, and new builds should start on the newer path.

Conversions API (CAPI)

The generic name for advertising platforms’ server-side conversion endpoints — Meta’s CAPI is the best known — which receive conversion events from your server instead of the browser pixel.

Platforms promote CAPI as recovering signal lost to blockers and privacy features, and it does — but it also moves matching from an anonymous pixel to identifiers you send deliberately. Decide what you send with a privacy review, not from the ad platform’s setup wizard.

Customer data and identity

First-party data

Data a company collects directly from its own audience with consent — site behavior, purchases, form fills, email engagement. Second-party data is someone else’s first-party data shared under agreement; third-party data is aggregated and resold.

"Zero-party data" — information customers volunteer, such as stated preferences — is a Forrester coinage that is legally still first-party data. Treat the label as marketing; treat the consent under which it was collected as the thing that matters.

Third-party cookies

Cookies set by a domain other than the site being visited — historically the mechanism behind cross-site ad tracking and retargeting.

The category is a lesson in not building plans on announcements: Safari and Firefox have blocked them by default for years, Chrome spent six years announcing deprecation — and then kept them in April 2025, dropping even the planned choice prompt. Signal loss is real and growing anyway; the reversal changed the deadline, not the direction.

Customer Relationship Management (CRM)

The system of record for known contacts, accounts, and deals, usually owned by sales or service — HubSpot and Salesforce are the reference points.

A CRM tracks relationships, not behavioral event streams, and its data decays as fast as people change jobs. The distinction that matters in stack conversations: a CRM records what your team knows; a CDP assembles what your systems observed.

Customer Data Platform (CDP)

Packaged software that builds persistent, unified customer profiles from many sources and makes them available to other systems — the CDP Institute’s definition, and still the test worth applying.

The label is the most rebranded in martech. The tells that a “CDP” is something else wearing the badge: it cannot ingest raw behavioral events in near real time, marketers cannot build audiences without engineering tickets, or profiles cannot leave for other tools. Most teams asking about a CDP need ownership decisions first — the argument is in the CDP versus CRM comparison.

Composable CDP

CDP capabilities assembled from parts — event collection, warehouse storage, identity modeling in SQL, and reverse ETL activation — instead of bought as one packaged product.

Both camps argue with pricing decks: packaged vendors call composable a science project, warehouse vendors call packaged a data silo. The real fork is staffing — composable means your team owns identity logic in SQL. If nobody can name that owner, packaged is the honest choice.

Data Management Platform (DMP)

An advertising-era system for building anonymous, mostly third-party audience segments from cookies and device identifiers.

The category has effectively ended: Oracle shut down its advertising business — including the best-known DMP — in 2024, and the surviving functions moved into CDPs, retail media, and clean rooms. A vendor pitching a DMP in 2026 should be asked which identifiers it still has.

Data warehouse

A queryable analytical store — BigQuery, Snowflake, Databricks — where raw data from every system lands and where modeling happens in SQL.

In marketing architecture the warehouse is the candidate single source of truth and the foundation of composable stacks. The honest prerequisite is engineering capacity: a warehouse without owned, maintained models is a swamp with a monthly bill.

Reverse ETL

Tooling that syncs modeled data out of the warehouse into operational tools — CRM fields, advertising audiences, email lists; Hightouch and Census defined the category.

What it actually buys: audience logic lives in version-controlled SQL instead of a vendor interface, and every tool receives the same answer. What it does not buy: real time — most syncs are scheduled batches, and the interval belongs in the design conversation.

Identity resolution

Stitching events and records from different devices, browsers, and channels into one customer profile — deterministically (shared identifiers such as email or login) or probabilistically (inference from signals).

Deterministic matching is the only kind worth building decisions on; probabilistic fills reports, not audiences. Vendor match rates are measured on the vendor’s best data — ask for the rate on records that look like yours.

Data clean room

A controlled environment where two parties analyze overlapping customer data — brand and retailer, brand and platform — without either side seeing the other’s raw records.

Genuinely useful at scale for measurement partnerships; mostly irrelevant below it. The prerequisites are meaningful audience overlap, legal review on both sides, and analysts to do the work — a mid-market team is rarely missing insights a clean room would unlock.

Activation and orchestration

Marketing automation platform (MAP)

Software that executes multi-step programs across channels — email, SMS, push, in-product — from triggers, audience rules, and branching logic.

The distinction from an ESP is the trigger-and-branch engine, and it is exactly what most teams underuse: a MAP sending two undifferentiated newsletters a month is an expensive ESP. The automation planning template exists to force the design questions first.

Email service provider (ESP)

Software whose core job is sending email at scale: list management, templates, scheduled sends, and delivery infrastructure.

An ESP is enough when your programs are calendar-driven sends to segments. Upgrade when programs genuinely need behavior triggers and branching — not because a vendor tier renamed itself "automation".

Journey orchestration

Coordinating messages across programs and channels around one customer’s state, so the sequence behaves as one conversation rather than parallel campaigns.

The unglamorous parts are the product: cross-program frequency caps, quiet hours in the recipient’s timezone, and exit rules for people who convert. A journey map without those three is a wish, not orchestration.

Segmentation

Dividing an audience into groups by attributes or behavior — lifecycle stage, engagement, purchase history — so programs and messages can differ by group.

Segments rot: the rule that defined one two years ago rarely matches how the business talks today. Audit membership logic on a schedule, and delete segments nobody can explain — an audience no one understands is a targeting bug waiting to send.

Lead scoring

Ranking leads by fit and behavior — points for firmographics, engagement, and actions — to decide which ones sales touches first.

Scores inflate: every added rule adds points somewhere, and thresholds set once are rarely recalibrated. The only defensible calibration is backward-looking — check what scores the leads that actually closed had, then set thresholds from that.

MQL and SQL

Marketing qualified lead and sales qualified lead: the two stage labels marking marketing’s handoff to sales, defined by criteria both sides agree to.

The letters are trivial; the definition is the entire game. If marketing and sales have not written down the criteria and the exit rules — what returns a lead, and when — the MQL count is a vanity metric that funds arguments instead of pipeline.

Suppression list

The list of addresses a program must never contact: unsubscribes, hard bounces, complaints, and legally excluded contacts.

This list is legally load-bearing. Unsubscribes must survive every migration and reach every sending tool — consent does not transfer between channels, and a suppression dropped in an export is a compliance incident, not a data cleanup item.

Email deliverability

Whether sent email reaches inboxes: a function of authentication (SPF, DKIM, DMARC), sender reputation, complaint rates, and list quality.

Since February 2024, Gmail and Yahoo require bulk senders — 5,000 or more messages a day — to authenticate with SPF, DKIM, and DMARC, offer one-click unsubscribe, and keep user-reported spam under 0.3%. Those are floors, not targets; reputation damage starts well below the enforcement line.

Privacy and consent

Personally identifiable information (PII)

Data that identifies a person directly (name, email, phone) or in combination (an IP address plus context), with exact definitions varying by law.

The classic martech leak is the URL: form pages that put an email address in query parameters feed PII into every analytics and advertising tag on the page. Google Analytics prohibits collecting it, and the fix — checking what your forms append to URLs — takes an afternoon.

The tool that presents privacy choices, records them, and exposes the resulting consent state for other systems to enforce.

Buying a CMP is not compliance — wiring it is. The project is the enforcement path: tags that actually wait for consent, a documented denied state, and a mid-session change test. The banner is the visible tenth of the work.

Google’s API for passing consent state to its tags, which then adjust behavior — from full measurement down to cookieless pings that feed modeled conversions.

Version 2 — two added advertising signals — has been required for ad personalization features in the EEA since March 2024. Read modeled numbers as modeled: when consent rates drop, Consent Mode fills reports, not audiences, and the model’s input is the behavior of people who did consent.

IAB TCF (consent string)

The IAB Transparency and Consent Framework: the advertising industry’s standard for encoding consent choices in a machine-readable string that programmatic vendors read; version 2.2 is current.

It matters in proportion to your programmatic footprint in the EEA and UK. If you run no programmatic advertising, your CMP does not need TCF registration — and a simpler consent implementation is easier to make honest.

Data governance

The rules and ownership around data: who may create fields, events, and audiences; what names they use; which systems are authoritative; who reviews changes.

In martech, governance is mostly naming and permission discipline — an agreed event taxonomy, one owner per system, a review step before new tags ship. It sounds bureaucratic and costs hours a month; its absence is why analytics audits find hundreds of events serving six questions.

Law 25 and CASL (Canada)

Québec’s Law 25 modernized private-sector privacy law in phases from 2022 to 2024 — privacy officer, breach reporting, consent standards, impact assessments. CASL, Canada’s federal anti-spam law, has required consent for commercial electronic messages since 2014.

For Canadian teams these bind daily martech practice more than the GDPR does. The CASL detail programs forget: implied consent expires — roughly two years after a purchase, six months after an inquiry — so a database that never re-earns express consent is quietly shrinking its lawful audience.

AI crawler

A bot that fetches web content for AI systems. The name covers three different jobs: training crawlers building datasets, search indexers feeding AI answers, and user-triggered fetchers retrieving a page during a conversation.

The three deserve separate policy — OpenAI alone runs GPTBot (training), OAI-SearchBot (search), and ChatGPT-User (on-demand fetches). Blocking “AI” as one category usually means blocking the answers channel you wanted while the training you objected to happens elsewhere. Telling them apart in server logs is covered in the AI search traffic guide.

AI visibility

How often, and how favorably, a brand appears in AI-generated answers — the AI-era analogue of rankings, measured by querying assistants with prompt sets and scoring mentions and citations.

Treat any single score as one run of a probabilistic system: the same prompt re-run produces different answers, so a score without sample size and variance is a screenshot, not a measurement. The full argument is in the AI visibility scores analysis.

Answer engine optimization (AEO)

Optimizing content to be selected and cited by answer engines — AI assistants and AI-augmented search — typically through extractable structure: direct answers, question-form headings, and machine-readable metadata.

Most AEO work is SEO work under a new invoice line: crawlability, clarity, and authority still decide selection. The genuinely new part is answer extractability — the first paragraph under each heading has to survive being quoted alone.

Generative engine optimization (GEO)

The umbrella term for earning presence in generative AI results — content structure, entity clarity, citations, and the technical surface (feeds, markdown renditions, metadata) that makes content easy for AI systems to ground on.

GEO and AEO circulate as competing labels for overlapping work; no vendor taxonomy is standard, so judge deliverables, not vocabulary. Ask what would change on the site — if the answer is structure, metadata, and citations, the work is real; if it is a dashboard of unstable scores, see AI visibility.

llms.txt

A proposed convention (llmstxt.org, 2024): a Markdown file at /llms.txt giving language models a curated map of a site’s most useful content.

No major AI provider has committed to reading llms.txt, so treat it as a cheap map, not a lever. This site publishes one and serves every page as Markdown alongside it; the honest framing is hospitality for agents, with adoption as the open question.

Content Signals

A robots.txt extension (Cloudflare’s Content Signals Policy, 2025) declaring how fetched content may be used: search, ai-input — grounding AI answers — and ai-train, each set to yes or no. Cloudflare added a fourth field, use, on July 1, 2026: it takes a level rather than yes or no — immediate (interact, store and reuse nothing), reference (index, excerpt, and link back — the default), or full (summarize and reproduce).

Two honest caveats: compliance is voluntary — Google has said the directive does not change its crawlers’ behavior — and Cloudflare changes defaults for new ad-serving domains on September 15, 2026, which is worth a policy check if that is you. This site declares search=yes, ai-input=yes, ai-train=no, use=reference: being usable in AI answers — and linked back to — is the point of the exercise.

AI agent

Software that pursues a goal by taking actions — browsing, calling tools, editing systems — rather than returning one answer; in marketing operations, agents draft, verify, and operate under human review.

The delegation test that holds up: give agents work that is structured, reversible, and cheap to verify, and keep judgment and accountability human. The reasoning, and where the line sits in content work, is in the AI agents guide.

Sources

Definitions and judgments are the author’s own, drawn from audits and implementations of real stacks. External facts rest on the following sources, verified on August 20, 2026:

For how these layers fit together, the related guides below extend several of the entries. To find out which of these terms your own stack is currently weak on, the MarTech stack readiness assessment turns the same categories into nine questions.

Related reading