- Template item
A marketing campaign checklist is the pre-launch QA list that proves every form, tag, CRM record, and email journey works before paid spend starts, plus the sign-off that makes someone accountable when something breaks. It is not a planning template or a creative brief. It is the launch-day gate. Most "marketing campaign checklist" results on Google are planning docs: audience, offer, channels, timeline. Useful earlier in the cycle. Useless at launch. By the time your campaign is 48 hours from going live, your questions are smaller and sharper.
Does the form fire the right event? Does the lead land in the right queue? Does the welcome email render on iOS Mail? And whose name is on the sign-off when it doesn't? This guide covers both: the six QA zones you must pass, and the sign-off model that keeps paid spend from flowing into a broken funnel.
What a marketing campaign checklist actually is (and what it is not)
A marketing campaign checklist is a pre-launch QA list and sign-off record that verifies every tracked touchpoint (forms, UTMs, CRM records, email journeys, paid platforms, and creative) behaves correctly before budget goes live. It is the gate between "creative is approved" and "we are spending money."
That distinction matters because the word "checklist" gets used two different ways in marketing. The first is a planning doc: audience, offer, channels, dates, budget. That lives at the start of a campaign cycle. The second, which is the one you are reading about here, is a QA doc: test cases, acceptance criteria, named approvers. That lives at the end.
The simplest boundary rule: if your checklist still has "write the subject line" on it, you are confusing a planning doc with a QA doc. Planning asks what to build. QA asks whether what you built actually works. The two deserve separate documents, separate owners, and separate review meetings.
Why the QA version is the one that saves money: a campaign brief that passes planning review and fails launch QA still costs you creative hours, agency fees, and brand airtime. A campaign that passes planning review, skips launch QA, and goes live with a broken form costs you paid spend plus the leads that spend was supposed to generate. HubSpot's CRM research and operator experience both land in the same place: launch defects compound faster than planning defects, because paid traffic doesn't pause while you fix the form.
The 6 pre-launch QA zones every campaign must pass
A complete pre-launch QA pass covers six zones: landing page and form, tracking and tags, CRM and lead routing, email journeys, paid platforms, and creative and copy. Each zone has its own test cases and its own owner. Missing a zone is how campaigns ship with silent failures that only surface three weeks in when the pipeline report looks wrong.
The six zones:
- Landing page and form. The page loads, the form submits, the thank-you fires, and the data lands in the destination you expect. Mobile and desktop both pass. Required fields match the data you actually need in CRM.
- Tracking and tags. UTMs are present on every ad destination URL and follow a convention your analytics platform can parse. Conversion events fire once (not zero times, not three times). Server-side and client-side agree.
- CRM and lead routing. New leads land on the right owner, with the right source, campaign, and stage. Dupes are handled. Enrichment runs. The sales handoff fires only when it should.
- Email journeys. The welcome fires. The nurture queues. Suppression lists apply. The unsubscribe works. Dynamic fields render, with no "Hi {{first_name}}" sends.
- Paid platforms. Pixels and conversion APIs are live. Audiences are built and scoped. Budget caps and bid caps are set. Account-level billing has runway.
- Creative and copy. Landing-page copy matches ad copy. Image aspect ratios match placement specs. Legal/compliance has approved the final version, not an earlier draft.
Operator pattern you will see repeatedly: zones 1, 2, and 3 fail at launch far more often than zones 4, 5, and 6. Why? Zones 4-6 are usually owned by one named person each (lifecycle marketer, paid media buyer, creative lead). Zones 1-3 cut across teams, so each team assumes someone else tested the handoff. The sign-off table in the next section fixes that.
Who signs off before launch (RACI table)
Pre-launch sign-off assigns a named owner and a named approver to every QA zone, then requires both signatures before paid spend goes live. No signature, no launch. The marketing ops lead typically owns the sign-off ritual: chases the signatures, logs the artifacts, and halts the launch if any zone is red.
| QA zone | Owner (runs the tests) | Final sign-off |
|---|---|---|
| Landing page + form, tracking + tags | Marketing ops | Head of marketing or growth lead |
| CRM + lead routing | RevOps or marketing ops | Head of sales |
| Email journeys | Lifecycle / email marketer | Marketing ops |
| Paid platforms, creative + copy | Paid media buyer + creative lead | Head of marketing |
Two patterns are worth calling out. First, marketing ops signs off on email journeys, not the lifecycle marketer. The lifecycle marketer built the journey; marketing ops verifies it against the CRM and the paid-source attribution. Separation of build and verification is the whole point of a QA checklist.
Second, head of sales signs off on CRM and lead routing because sales lives downstream of the breakage. If the lead-routing rule drops a Series B prospect into a self-serve queue, the pipeline consequence is sales's problem. Giving them the sign-off also gives them the mandate to halt a launch when routing is wrong.
Test cases: forms, tags, CRM records, email journeys
Test cases translate each QA zone into concrete pass/fail checks with named owners. Every test case needs three things: a specific action to perform, a definition of "what good looks like," and the role that runs the test. If any one of the three is missing, the test is theater. The checkbox gets ticked without the behavior ever being verified.
Form test cases
| Test | What good looks like | Who runs it |
|---|---|---|
| Submit with all fields filled | Thank-you page loads, record written to CRM | Marketing ops |
| Submit with required field missing | Inline validation blocks submit | Marketing ops |
| Submit on mobile Safari | Same thank-you + CRM write as desktop | Marketing ops |
| Submit from a known test email domain | Record is tagged test and excluded from reports | Marketing ops |
Beyond these four, run one real end-to-end submission from a personal device, not the office network. More than one launch has shipped with a form that works everywhere except through the corporate VPN.
Tag and UTM test cases
UTM naming conventions themselves are a separate topic; see the sibling article for depth.
| Test | What good looks like | Who runs it |
|---|---|---|
| Click each ad in preview mode | UTMs land on the destination URL unchanged | Paid media buyer |
| Open browser dev tools during submission | Conversion event fires exactly once | Marketing ops |
| Compare GA4 vs ad platform conversions | Counts within 5% of each other on test traffic | Marketing analyst |
| Validate server-side event via Meta/Google test tools | Deduped against client-side event | Marketing ops |
If server-side and client-side disagree by more than 5% on test traffic, pause the launch. The real-traffic disagreement will be larger, and attribution reports will mislead the next quarter's budget decisions. Google Analytics' Campaign URL guidance is the canonical reference for UTM structure.
CRM record test cases
| Test | What good looks like | Who runs it |
|---|---|---|
| New lead from this campaign | Owner assigned per routing rules; source populated | RevOps |
| Duplicate lead from a prior campaign | Merge rule fires; no double record | RevOps |
| Lead from an ICP-matched company | Enrichment runs; account auto-created or matched | RevOps |
| Lead from an excluded domain | Routed to disqualified queue, not sales | RevOps |
Routing bugs are the single most common silent failure at launch. Salesforce's own documentation describes lead-assignment rules as deterministic; in practice they are only deterministic when the data populating them is clean, which is why the sign-off is a RevOps signature, not an assumption.
Email journey test cases
| Test | What good looks like | Who runs it |
|---|---|---|
| Trigger welcome from a test contact | Email arrives within SLA; dynamic fields render | Lifecycle marketer |
| Render preview across major clients | iOS Mail, Gmail web, Outlook desktop all pass | Lifecycle marketer |
| Unsubscribe from the welcome | Contact added to suppression, no further sends | Lifecycle marketer |
| Simulate a known-bad address | Bounce handled, journey stops gracefully | Lifecycle marketer |
Rendering is the zone that catches teams off guard most often. A template that looks perfect in the sender tool can collapse in Outlook. Litmus is the industry standard for pre-send rendering checks across clients.
When to hire fractional marketing ops vs full-time
The right ops hire tracks to monthly paid spend and launch cadence. Below $25K/month in paid, a fractional marketing ops specialist covers the sign-off ritual, test cases, and quarterly tooling cleanup without the overhead of a full-time role. Between $25K and $150K/month, fractional ops still handles execution but you add a part-time ops lead to own strategy.
| Monthly paid spend | Right hire | Why |
|---|---|---|
| Under $25K | Fractional ops, 10-15 hrs/week | Volume supports senior part-time, not full-time |
| $25K-$150K | Fractional ops + fractional ops lead | Build the playbook now, hire FT when cadence stabilizes |
| $150K+ | Full-time marketing ops manager | Daily launches justify dedicated capacity |
Full-time hiring at the sub-$25K band is the common overhire. The ops person spends 60% of their week on dashboards that no one reads. Running fractional through MarketerHire's model matches capacity to actual launch cadence: a vetted ops specialist in 48 hours, month-to-month, with the option to scale up when launches become weekly. Pattern recognition from 30,000+ MarketerHire matches says sub-$25K is where fractional outperforms FTE on cost and quality.
Specialist brief: scope a marketing ops hire from this checklist
A specialist brief turns this QA checklist into a scope you can hand to a candidate on day one. The brief defines role, deliverables, acceptance criteria, timeline, and hire model, with enough detail that an experienced marketing ops specialist can quote you a fixed engagement without a second scoping call.
Role: Fractional marketing ops specialist, 10-15 hours/week, 90-day initial engagement.
Deliverables:
- Written launch QA checklist mapping every active campaign to the six zones in this guide.
- Named sign-off RACI covering landing pages, tags, CRM, email, paid, and creative.
- A documented test library with the test cases from the previous section codified in your actual tools (your CRM, your email platform, your ad accounts).
- Launch sign-off log for every campaign that goes live during the engagement, stored where sales and finance can audit it.
- A one-page escalation path for when a zone fails pre-launch and the launch has to slip.
Acceptance criteria:
- Zero launches during the engagement with a form, tag, or routing defect that reaches production for more than 24 hours.
- Sign-off log complete for every launched campaign, with no "we just shipped it" entries.
- RevOps and sales both acknowledge the lead-routing rules in writing before the second launch.
- Checklist is maintainable by the next ops hire without the author present (the Taco Bell test for ops documentation).
Timeline: First draft of the checklist and RACI within 2 weeks. Full test library inside your tools within 6 weeks. 90-day review against the acceptance criteria.
Model: Start fractional. Convert to full-time only after 90 days of weekly launches with a clean sign-off log. If you are not launching weekly, fractional stays the right answer. Fund a Marketing Automation specialist part-time and reinvest the saved headcount into a marketing analyst who covers measurement across the whole funnel.
FAQ
The minimum is one end-to-end test per QA zone: submit the form, click an ad to verify UTMs, write a lead to CRM, trigger the welcome email, check the paid pixel, and confirm creative matches the final approved copy. Six tests, one named owner each, and a sign-off log. Anything less is launching on hope.
Four signatures: head of marketing or growth lead on landing pages and tracking, head of sales on CRM and lead routing, marketing ops on email journeys, and head of marketing on paid platforms plus creative. Marketing ops typically chases the signatures and halts the launch if any zone is red. No signature, no launch.
A documented, repeatable QA pass takes 2-4 hours for a standard campaign across form, tags, CRM, email, paid, and creative. The first time you run it, expect a full day because you are discovering the gaps. Once the test library exists in your tools, each subsequent launch runs against the same checklist and compresses to a half-day.
Lead routing and conversion tracking break more often than any other zone. Routing fails when a new campaign's source value doesn't match the rules, so leads land unassigned. Tracking fails when a tag manager update ships without regression testing. Both are silent: the campaign looks live, the pipeline report lies, and the error surfaces weeks later.
Fractional below $25K/month in paid spend, hybrid between $25K and $150K, full-time above $150K. The decision is about launch cadence, not headcount preference. Monthly launches do not justify a full-time ops hire; weekly launches do. If a fractional specialist can hit the acceptance criteria in the specialist brief, you do not need full-time yet.
Scope the hire, then launch
A marketing campaign checklist is only useful when it has a signature on it. Build the six-zone QA ritual, assign the RACI, codify the test cases in your actual tools, and gate paid spend behind the sign-off log. If you do not have the ops capacity in-house to run the ritual, hire for it with the specialist brief above: fractional first, full-time when launch cadence justifies it. The pattern that keeps paid spend from flowing into a broken funnel is boring. That is the point.
About the author: Jenny Martin is a Growth Marketing Editor at MarketerHire. She's led growth across DTC and B2B SaaS, scaling revenue to $50M and cutting CAC by 40%. She now focuses on AI-driven marketing ops and writes about growth hiring, channel strategy, and what works at the $2-50M stage.

