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

Marketing Operations

Marketing Operations Systems

Operations systems are the places where marketing work, assets and data live, and the routines that keep them accurate. This hub separates systems of work from systems of record, describes what each must hold, routes you to the core work management and data operations guides and to further guides on setting up an asset library, withdrawing an asset from every channel and an onboarding pack for new marketers, and explains where operations hands over to the marketing stack.
SectionintermediateUpdated

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

Systems of work versus systems of record

It helps to sort every system a marketing team uses into one of two kinds. Systems of work are where work is planned, assigned and moved forward: the work management tool, the marketing calendar, intake forms and the review queue. They change many times a day and their value is in being current. Systems of record are where outcomes and approved artefacts are kept: the asset library, the CRM, the analytics property, the ad platforms' account structures and the consent records. They change less often and their value is in being accurate and trusted.

The distinction matters because the two kinds fail differently. A system of work fails by being ignored: work happens in chat and email, the board goes stale, and the calendar stops being believed. A system of record fails by being polluted: duplicate contacts, assets with no version or rights information, campaigns named three different ways. Fixing the first is about adoption and design; fixing the second is about rules and routines. Operations owns both, but it should not treat them the same way. A rule that every board card must carry a dozen fields will kill adoption; a rule that every campaign name must follow the taxonomy is exactly what a system of record needs.

Work management, assets, data

The operational systems in the table cover most of what a marketing team needs. Each has a job, a minimum it must hold and a typical failure.

SystemIts jobWhat it must holdTypical failureCovered in
Work management and calendarShow every piece of work, its owner, stage and date; give one view of what goes out whenWork items by type, stages, owners, due dates, links to briefs and approvalsHalf the work lives elsewhere, so the calendar is wrongWork management guide
Asset libraryHold approved creative, copy and brand files with versions and usage rightsFinal files, version, approval status, rights and expiry, channel sizesOld or unlicensed assets reused because the current ones cannot be foundWork management guide, Setting up an asset library
Data operationsKeep names, tracking and audience data consistent across platformsCampaign taxonomy, naming rules, hygiene routines, ownershipThe same campaign has different names in each platform and reports disagreeData operations guide

Data operations is the least visible of the three and often the most valuable. Every UTM parameter, every audience list and every campaign name is data that someone has to keep consistent, and consistency does not survive without an owner and a routine.

The core guides

  • Work management and marketing calendars covers how to run marketing work in one system: choosing an approach, designing boards, stages and work types, using the calendar as the single view, managing assets with versions and rights, building templates and intake forms, and reporting directly from the work system.
  • Marketing data operations and taxonomies covers the routines that keep marketing data usable: a campaign taxonomy across platforms, who enforces naming and how, CRM and audience hygiene, ownership and audit cadence, and the hand-off to analytics.

Read the work management guide first if work is scattered across inboxes and spreadsheets; read the data operations guide first if the work is organised but the reports disagree with each other.

Further guides

Further guides cover the asset library in practice, from setting it up to taking an asset down everywhere it runs, and the material that helps people joining the team find their way around the systems:

Connecting operations systems to the stack

The systems on this page run on tools, and choosing those tools is a stack decision. The marketing stack hub covers stack design, tool evaluation and integration. Operations contributes the requirements and the discipline: what the work system must record, what the asset library must hold, which fields must pass between platforms, and who keeps each system clean. To see which tools the operation already runs and whether each still earns its place, the tutorial on running a marketing stack audit finds every tool, maps it to the use cases it serves and ends with a decision for each.

Three connections deserve attention. The work system should link to the systems of record rather than copy them: a work item points to the asset in the library and to the campaign in the ad platform, so that there is one source for each. The taxonomy should be applied at the point of creation, in intake forms and templates, so that names arrive in the analytics property (GA4), the ad platforms and the CRM already consistent. And the technical layer, including the tag container (GTM) and any customer data platform (CDP), should be governed by the same change rules as the rest of the operation, even when a different team administers it. The marketing operations hub explains how systems sit alongside process and governance.

Illustrative example — not a real result

A travel company maps its systems

Saltmarsh Holidays, a specialist travel operator with a marketing team of nine, listed every place where marketing work or data lived. The list ran to 14 entries, including three spreadsheets that each claimed to be the campaign calendar and a shared drive with 2,300 image files and no version information. The team consolidated work into one work management tool with four work types, made the calendar a view of that tool rather than a separate file, moved approved assets into a library with an expiry field for licensed images, and adopted one campaign taxonomy enforced on the intake form. Within two quarters the list of places had fallen to five, and the monthly report no longer needed a day of manual name matching.

Common systems problems

SymptomUsual causeGuide
Nobody trusts the calendarWork lives outside the work system; calendar maintained by handWork management
Out-of-date or unlicensed assets go liveNo asset library with versions, approval status and rightsWork management, Setting up an asset library, Withdrawing an asset from every channel
An asset that had to come down is still running somewhereUses never recorded; automated journeys and partners' copies missed; the file not marked withdrawnWithdrawing an asset from every channel
New joiners wait for access and learn the rules by breaking themNo onboarding pack; access requested after the starter arrivesBuilding an onboarding pack
Every request arrives in a different formatNo templates or intake forms per work typeWork management
Reports from different platforms disagreeNo shared campaign taxonomyData operations
Naming rules exist but are ignoredNo enforcement at the point of creationData operations
Audience lists are stale or duplicatedNo hygiene routine or ownerData operations
Tools overlap and nobody knows which to useStack chosen without requirementsMarketing stack
The same campaign appears under several names across platformsNo shared taxonomy, hand-typed links or no naming ownerCampaign names and UTMs inconsistent
The monthly report takes days to assembleManual exports, unwritten definitions and unowned dashboardsMonthly marketing report takes days

The marketing operations troubleshooting section takes symptoms like these one at a time, with a diagnosis table and a fix, verification step and prevention habit for each cause.

Terms used on this page

Related