Marketing Operations: Does Any of It Connect?

On the Wednesday of week ten Dana Whitlock has two documents open and they do not agree with each other. One is Miriam’s conditional publication approval, which withdraws a generated image of an oven plant. The other is a landing-page mock-up, built in week eight, in which that image is still the hero. Nobody did anything wrong. Theo withdrew the asset the moment he decided against it, and withdrawing an asset means announcing that it should not be used — which is not the same as it ceasing to exist in the eleven places somebody had already put it.

That gap is Dana’s whole job in miniature. Everyone upstream of her has been deciding what the campaign will say. She decides whether any of it actually works: whether a click becomes a record, whether the record carries where it came from, whether consent travels with it, and whether the person who eventually picks up the phone can see why this human is on their screen. Four weeks of launch remain, and the instrumentation window Ryan drew on the plan is weeks ten to twelve.

What lands on Dana’s desk

From Miriam in module 9 comes publication approval that is explicitly conditional, plus the claims register. The conditions are not opinions Dana can agree to; they are things she has to build. Consent scope has to be enforced by the system rather than remembered by a person. Unsubscribes must propagate everywhere, not only in the tool that sent the message. The substituted Calder wording has to replace the general claim in every asset, including email sequences already loaded and scheduled.

From Theo in module 8 comes the creative package with its provenance log, forty placements deep, and the withdrawn image note. From Ryan in module 6 comes the channel plan with its dates and volumes, the five journey-stage definitions, and one rule stated as a hard condition: no paid spend begins before the instrumentation is live, because leads you cannot attribute are leads you cannot optimise, and by the time the reports look wrong the money has gone.

And underneath all of it sits Delia’s arithmetic from module 1, which nobody has revisited: 2,530 leads, 760 MQLs, 190 opportunities. Every one of those numbers is a count of records in a system Dana is about to build.

What a marketing operations manager actually does

Marketing operations is the plumbing trade of a marketing department, and like plumbing it is invisible when it works and catastrophic when it does not. The job is to connect the systems — the advertising platforms, the website, the forms, the marketing automation tool, the customer relationship management system, the sales queues — so that a stranger’s single click becomes a record that a named person can act on, with the source recorded and the consent captured.

It is also, quietly, the department’s memory. Definitions, field names, scoring rules and naming conventions all live here, and they are the reason two people can look at the same dashboard and see the same number.

The software on Dana’s desk

A tag manager and a generated link convention sound like housekeeping and decide whether module 12 can measure anything: two channels whose names disagree cannot be compared, and the error cannot be fixed retrospectively because the data was never captured. Marketing automation holds the rules — scoring, consent, routing — and the important discipline is that the MQL definition is encoded there rather than described in a document nobody opens.

The CRM sync is the join where campaigns most often lose people, and where a lead arrives stripped of the reason it came. The last screen is not really software at all: Dana fills in her own form as a real person and follows the record through all six systems. That hour finds the consent flag that does not propagate, the missing field that breaks a routing rule, and the withdrawn image still live on an indexed staging page — none of which any dashboard would have reported.

The four decisions

What “connected” actually means

Ask a marketing team whether their systems are connected and the answer is almost always yes, because each individual link exists. Dana asks a different question, which is whether a single human being can travel the whole distance without falling through a gap. So she walks one, out loud, in the week-ten meeting.

A plant operations director in Ohio is on LinkedIn at twenty to eight in the morning. She sees the advert with Theo’s gap in it and taps. Her phone opens the landing page, and the first join has already happened: the labels identifying which advert she saw have to survive that hop, or the rest of the journey is anonymous. She reads, and fills in the form — name, work email, company, job title, company size, and a consent box with wording Miriam approved rather than wording somebody found in a template.

The submission goes to the marketing automation platform, which creates a record, stores the consent with its date and its scope, writes down the source, and applies the scoring rules. The record then syncs to the CRM, where it either becomes a new contact or is matched to an account that already exists. A routing rule reads the territory and the company size and drops it into a named SDR’s queue. And Curtis’s rep opens their morning list and sees a person, a company, a source, and a reason.

Six joins between an advert and a phone call, and every one of them is a place a human being can vanish. The tracking labels are stripped by a redirect through a link shortener, so the lead exists but arrives from nowhere. The form collects company size but no field mapping exists for it, so the value is dropped without complaint and the routing rule that keys on it fails. The sync runs every fifteen minutes and the routing rule fires before the score is written, so a genuinely hot lead is assigned as though it were cold. The email already exists in the CRM under a slightly different company name and the record duplicates. The territory field is empty, so the rule matches nothing and the lead lands in an unassigned queue that nobody has ever opened.

Here is the part worth carrying away. Most campaigns lose more people in the plumbing than in the messaging, and the loss is invisible, because a lead that vanishes at a join does not appear anywhere as a loss. It appears as a channel that underperformed. Somebody then rewrites the advert.

The tracking taxonomy

This is the most boring decision in the entire course and the highest-leverage thing on Dana’s desk, and it is worth being blunt about why.

When a link is used in an advert or an email, small labels are appended to it — conventionally called UTM parameters — that tell the receiving system where the click came from. There are five in common use: the source (which platform), the medium (which kind of marketing), the campaign, the specific piece of content, and, for paid search, the term someone typed. They look like technical infrastructure. They are not. They are free text that a human types, and nothing anywhere validates them.

Which means that linkedin, LinkedIn, LI, linked-in and LinkedIn Ads are five different channels as far as every report downstream is concerned. Nobody made a mistake big enough to notice. An agency built one set of links, a contractor building the webinar pages built another, somebody hand-typed a third at half past six on a Friday, and the campaign now has a real channel spending $330,000 and four phantom channels spending nothing and producing leads.

So Dana writes a taxonomy before a single link is built, and it is deliberately rigid: lowercase only, hyphens rather than spaces, a fixed and closed vocabulary for source and medium so nobody may invent a new one without asking her, a campaign name that follows one pattern for every placement in the launch, and a content label that identifies the specific asset and journey stage. Then she does the thing that actually makes it work, which is not the document: she builds a link generator, and rules that no link enters a live placement unless it came out of that generator. Conventions people are asked to remember decay in about three weeks. Conventions embedded in the only tool that produces the artefact do not.

The reason this matters is two modules away. Lena’s job in module 12 is to say which channels earned their money, and you cannot compare channels whose names disagree. Worse, it cannot be repaired afterwards. You can rename rows in a spreadsheet, but you cannot recover which advert a lead saw if the label was never carried in the first place — the information was not lost, it was never collected. And it bites earlier than that, too: Ryan’s reserve of about $174,000 is allocated at the end of week six to whichever channel has the lowest cost per MQL. If the taxonomy is inconsistent, that decision is made on noise, with real money.

The definition that has to be agreed before launch, not after

Delia’s arithmetic assumes 760 MQLs, and the phrase sits in the plan as though it referred to something that exists in the world. It does not. An MQL is not a fact about a person; it is a rule in a system, and somebody has to write it.

Dana’s version has two halves, and she insists they stay separate. Fit is about the company: a discrete manufacturer, in North America, between $50m and $500m of revenue, with a job title in operations, supply chain, procurement or plant management. Behaviour is about what the person did: which pages, how many visits, whether they came back, whether they attended a webinar rather than merely registering, whether they downloaded the supplier-risk guide or looked at pricing. A lead becomes an MQL when it clears the fit bar and crosses a behaviour threshold.

Then she makes Curtis and Ryan write down what does not count, which is the half most teams skip. A competitor. A student. A consultant. An existing customer. A forty-person machine shop that is nowhere near the segment. Somebody who downloaded one white paper and never returned. Exclusions are where a scoring model earns its keep, because without them the number goes up and the quality goes down and both movements are reported as success.

She forces the agreement into writing, signed by both of them, before launch. The alternative is not a mild inconvenience; it is two teams reporting different numbers from the same database for a quarter. Marketing’s dashboard says 610 MQLs. Sales says it received 380 worth calling. Both figures are correct inside their own definition, and the argument cannot be settled, because there is no shared object anyone can point at. Meanwhile the reserve gets allocated on the disputed number, the week-six optimisation is made on it, and by the time anyone notices, a quarter of spend has been steered by a metric two departments define differently.

One more detail, small and load-bearing: every record that crosses the threshold stores which rule fired. Not just the score — the reason. That single field is what makes Curtis’s feedback loop in module 11 possible at all.

The test nobody budgets for

In week twelve Dana books a day that appears on no plan and has no budget line, and runs the whole path with real submissions. Real email addresses she controls, on a real phone and a real laptop, through every landing page, from every channel, including the trade-show badge-scan import that will land three hundred records in one lump on the Thursday of week fourteen.

She finds five things.

The consent flag is not propagating to the email tool. It is captured correctly on the form and stored correctly in the automation platform, and the field simply does not exist on the other side of the join — so people who consented arrive looking like people who did not. That is Miriam’s condition failing silently, and it would have taken weeks to notice, because nothing about it looks broken.

One landing-page variant is missing the company-size field. The routing rule keys on company size, so every lead from that page fails the rule and drops into an unassigned queue. Not a small share of leads. All of them, from one of the campaign’s four pages.

The withdrawn Calder image is still live on a staging page, which has been indexed by search engines and is linked from a webinar registration confirmation. Theo withdrew it in week nine and Miriam blocked it in week ten, and here it is in week twelve, publicly reachable. This is the moment Dana stops treating the asset problem as a communications failure and builds the fix: one library of approved assets, versioned, with every placement pointing at it rather than holding a copy, and a rule that anything outside the library is by definition not approved. Withdrawing only works when there is one place to withdraw something from.

The paid-search landing page redirects through a shortener that strips the tracking parameters, so the most expensive leads in the campaign would have arrived unattributed. And the webinar thank-you page is missing its conversion tag entirely, so registrations would have been counted and attendances would not.

None of these are exotic. Every one of them is the ordinary consequence of six systems being configured by four people over three weeks. And the point Dana makes to Ryan afterwards is the one worth keeping: this rehearsal is the cheapest hour in the campaign. An afternoon in week twelve costs an afternoon. The same discoveries in week two of a live campaign cost every lead that arrived in between — and those leads are not recoverable, because nobody knows they existed. There is no queue of missing people to go back to. There is only a channel that looked disappointing.

Where this goes wrong

The classic failure is not that operations is done badly. It is that operations is done last, in the compressed fortnight after everything else has slipped, by someone who was handed the requirements a week ago. The campaign launches on the fixed date because the trade show does not move, the tracking is ninety per cent right, and the missing ten per cent is discovered in week three when a sales rep mentions in passing that they have not received a lead from the webinar programme. Three weeks of a fourteen-week campaign, and the money is spent.

The second failure is treating this desk as a ticket queue. If Dana first sees the campaign in week ten, she is configuring somebody else’s decisions rather than shaping them — and the decisions that most needed her, like whether every journey stage Ryan defined can actually be observed in a field, were made in week six by people who assumed it was possible. Ryan’s note in module 6 that a stage only exists if you can see it is the whole argument for having this desk in the room early.

The third is a taxonomy that exists as a document and not as a tool. Everyone agrees to it, everyone means it, and within a month there are four spellings of LinkedIn in the reporting, because agreement is not a mechanism.

Designing this desk’s agent: the pipeline monitor

Dana’s failures are silent by nature: a lead that never arrives generates no error and no complaint. It looks exactly like a channel that underperformed.

One concrete design choice. Reconcile at every join rather than at the ends. Submissions counted at the form, at the automation platform and at the CRM should agree; the join where they stop agreeing is the leak, and knowing which join is the entire diagnostic value.

{
  "check": "form_to_crm_reconciliation",
  "window": "2026-06-28",
  "expected": 138,
  "actual": 121,
  "gap_pct": 12.3,
  "suspected_join": "automation_to_crm_sync",
  "severity": "high",
  "owner": "dana.whitlock"
}

The metric to track. Leakage rate — leads submitted against leads arriving in a human being’s queue. It should be nearly zero, and the only way to know is to count both ends independently rather than trusting either system’s own dashboard.

What Dana hands on

Curtis Nwosu in module 11 receives leads that arrive in a named queue with a source, a score, and the rule that fired — which is what lets him reject an MQL with a reason rather than with an opinion. He also receives the signed MQL definition he helped write, which means the argument he would otherwise have had in week six has already happened, in week eleven, on paper.

Lena Park in module 12 receives a taxonomy consistent enough to compare channels against each other, a set of journey stages that exist as fields rather than as concepts, and a database in which the word MQL means one thing for the whole quarter. Without those, her analysis in the final module would be an exercise in reconciling spellings.

And the whole team receives the asset library, with the withdrawn Calder image now genuinely gone rather than merely disapproved of. The constraint everyone downstream now inherits is the one Ryan wrote and Dana enforced: the instrumentation is live before the spend starts. Nothing goes out on a link that did not come from the generator, and nothing appears in an advert that is not in the library.

Would it survive the test?

Read each one and decide what Dana finds, then tap a card to check.