Search glossary

Marketing Operations Glossary

Browse the glossary

Every term, two ways.

By topic

Start with the part of MarOps you work in

Testing and release25 terms Funnel, lifecycle, and revenue25 terms CRM, data, and database38 terms Lead management and automation43 terms Campaign operations and execution23 terms Measurement, analytics, and attribution46 terms Web, tracking, and consent31 terms ABM and go-to-market24 terms Platform, architecture, and operational maturity39 terms AI and modern automation26 terms

A–Z index

Find a term alphabetically

A

A/B test Acceptance criteria Account engagement Account scoring Account tiering Account-based marketing / ABM Action Activation Agent Alerting API Architecture Assignment rule Attribution Attribution window Audience Audit trail Automation bias Availability / uptime

B

Backlog Baseline Batch processing Behavioral score Benchmark Best of breed Bounce rate Business requirements Business rule Buyer persona Buying committee / buying group

E

Edge case ELT Email authentication Embedding End-to-end test / E2E Engagement rate Error handling ETL Evaluation / eval Event Event parameter / property Exclusion rule

F

Fallback Feature flag Field Field mapping Firmographic score First-party cookie First-party data First-party intent First-touch attribution Foreign key Form shortening Frequency cap Functional requirements Funnel Funnel analysis

G

Generative AI Golden dataset / test set Golden record Grounding GTM / go-to-market Guardrail

H

Hallucination Happy path Holdout group Human in the loop / HITL

I

ICP Idempotency Identity resolution Inbound Incremental testing Incrementality Influenced pipeline Inquiry Intake process Integration Integration test Intent data

K

M

Marketing automation platform / MAP Marketing-led growth MarTech stack Master data management / MDM MCP Metric Middleware / iPaaS Minimum viable process Minimum viable product / MVP Model drift Monitoring MQA MQL Multi-touch attribution / MTA Multivariate test

N

Naming convention Native integration Negative test Normalization North Star metric Null Nurture Nurture stream

O

Object Observability One-to-few ABM One-to-many ABM One-to-one ABM Open rate Operationalize Opportunity Opportunity-creation touch Opt-in Opt-out Orchestration Original source Outbound

Q

QA checklist Quality assurance / QA Queue

U

U-shaped attribution Unit test Upstream / downstream User acceptance testing / UAT UTM parameters

V

Validation rule Variance Vector database Version control

W

W-shaped attribution Waterfall enrichment Webhook Workflow

Z

Zero-party data

Quick answers

Browsing the glossary

How can I browse the marketing operations glossary?

You can browse the glossary by topic when you want to understand a body of related work, or use the A–Z index when you already know the term or its first letter. Both paths lead to the same complete term pages and practical explanations.

For example, a marketer working on database cleanup can open the CRM, data, and database topic to find normalization, standardization, deduplication, identity resolution, and data hygiene together instead of searching for each term separately.

What is covered by the glossary topics?

The glossary topic coverage is a practical map of marketing operations: testing and releases, funnels and revenue, CRM and data, lead management, campaigns, measurement, web tracking and consent, ABM, platform architecture, and AI automation. The categories group concepts that are commonly used together in operational work.

For example, the measurement topic places attribution, incrementality, KPIs, dashboards, and pipeline reporting near one another, which helps a team compare related concepts before agreeing on a reporting method.

Does every term include a practical example?

Yes. Every term includes a short plain-English definition and a marketing operations example, while its dedicated page adds a fuller explanation, workplace language, common mistakes, related concepts, and an external reference when one has been approved.

For example, the regression testing page does not stop at defining the term. It describes checking existing forms, routing, emails, analytics, and mobile behavior after a change so the reader can recognize the practice in a real release.