Products · Taxonomy Management
Plan, approve and distribute your taxonomy
Get control of your taxonomy as it scales across teams, brands, regions and agencies — with changes sandboxed before rollout, governed by approval, and pushed everywhere through the UI, the API and MCP-connected agents.
Trusted by
Where taxonomy governance breaks down at scale
- Every brand, region and agency keeps its own copy of the standard, and the copies drift apart.
- You change the taxonomy by email, and six months later the approval trail is the email thread.
- You cannot test a change before it reaches production reporting.
- The approved standard exists. Nothing carries it to the teams and systems that have to use it.
47%
of martech decision-makers cite stack complexity and integration challenges as key blockers.
Source: McKinsey, “Rewiring martech: From cost center to growth engine”
50%
adoption for data compliance and governance inside marketing, against 91% for AI content production — governance is the half that did not scale.
Source: State of Martech 2026, Brinker & Riemersma
Model a change before anyone lives with it
See what a change affects, which templates inherit it and what breaks, while it is still reversible. Enterprise taxonomies rarely come apart at the design stage. They come apart at the change, which is the stage most tools leave outside the system entirely.
Every change is proposed, reviewed and recorded
Approval workflows put a named person between a proposal and production. A user activity log records what changed and who changed it. Role-based access decides who can propose at all. This is what turns a taxonomy from a document into a governed asset.
The approved standard reaches every team and system
The approved standard reaches the people and systems that need it. Teams get it through the interface. Systems get it through 31 connectors and the API suite. AI tools get it through MCP-connected agents, working from the governed source rather than a copy.
What this is not
It helps to place this against categories that already have a name.
Not a data governance suite
Enterprise governance tools cover data across the business. This governs the marketing taxonomy specifically, at the depth marketing actually needs.
Not a master data management platform
MDM reconciles records after the fact. This distributes an approved structure before records are created.
Not a workflow or project management tool
It approves changes to the standard, not the campaigns that use it.
Not an integration platform
It uses connectors to distribute a governed taxonomy; moving arbitrary data between systems is not its job.
Works with the stack you already run
Native connectors across the ad platforms you buy on, the analytics and storage you report from, and the content systems your assets live in. An API suite and flat-file exchange cover whatever will never have a connector.
Frequently asked questions
Didn't find your answer? Bring your questions to a thirty-minute walkthrough with someone who has done this at enterprise scale — we'll show you, not tell you.
There are three taxonomy products. Which one do I need?
Choose this one if the standard already exists and the difficulty is keeping it consistent as more teams, brands and agencies depend on it. Choose Taxonomy & Governance if the naming itself is still the problem. Choose Content Taxonomy & Governance if the scaling problem is creative assets rather than campaign structure.
What is taxonomy management?
Taxonomy management is the practice of maintaining a shared classification structure as it changes and as more teams depend on it. It covers who may propose a change, who approves it, how it is tested before rollout, and how the approved version reaches every team and system that needs it. It is distinct from defining the taxonomy in the first place — that part is usually done once; this part never stops.
Who should own the taxonomy?
One team should own the structure and many teams should be able to propose changes to it. Ownership with no proposal route produces a bottleneck; proposal rights with no owner produce drift. The workable arrangement is a named owner, an approval step and an audit trail. That is what turns a taxonomy into a governed asset rather than a document.
How do we roll out a change without breaking reporting?
Model it in a sandbox first. See which templates inherit the change and what it affects downstream while it is still reversible, then approve and distribute. Enterprise taxonomies rarely fail at design; they fail at the change, and that stage usually happens outside any system that records it.
What are the advantages of using MCP?
The Model Context Protocol lets AI assistants reach a governed system directly rather than working from a pasted copy. For a taxonomy that means an agent can read the approved structure as it stands now, so what it produces conforms by construction. Buyers raise it often enough that it appeared in nine of twenty-one rows on our own purchase sheet.
How does this work across agencies?
Agencies receive the approved standard and work inside it, with their own access scope and isolation from other clients' data. The compliance view shows where an agency is drifting before the campaign runs. Finding it afterwards is a remediation project; finding it first is a conversation.
See it against your own taxonomy
Thirty minutes with someone who has implemented this at enterprise scale, not a generic product tour.
- Your naming conventions modeled as a working template
- Which of your current entries would pass validation, and which would not
- How governance holds without becoming a bottleneck
- What rollout looks like across teams and agencies
- Which of your platforms connect natively
- Pricing and packaging, discussed openly