Foundry Academy · Marketing Operations · Lesson 4 of 6

Tracking plan and preflight QA

Define decision-oriented measurement and complete a documented preflight that verifies the whole customer and data path before launch.

Start the lesson

Your learning work, on this device

No signup, cloud storage, cross-device sync or verified completion. Saving is optional. This browser profile is shared with anyone who can use it; private mode, browser cleanup or storage limits may remove work. Use only fictional or non-sensitive material. Export a copy before relying on this device.

Not saved. Worksheets, answers and practice notes currently last only in this tab.

Practice markers are self-reported, never credentials.

01 · Explanation

Tracking plan and preflight QA

Objective: Define decision-oriented measurement and complete a documented preflight that verifies the whole customer and data path before launch.

A tracking plan starts with the campaign decision, then defines events and dimensions needed to support it. For each measure, specify the user action, trigger, property names, allowed values, source system, owner, consent dependency, test method, reporting delay, and known limitation. Use a governed naming convention for campaign parameters and avoid placing personal or sensitive information in URLs, event names, or free-text analytics fields. Reconcile key conversion events against a system of record where possible. Attribution shows how a platform assigns credit under a rule; it does not by itself prove that a campaign caused the result.

Preflight tests the experience end to end. Use approved test records to verify audience and suppression, sender identity, claims, disclosures, subject line, asset versions, links, redirects, page rendering, keyboard access, forms, validation, confirmation messages, lead routing, notifications, analytics events, error handling, and unsubscribe behavior. Capture evidence with date, environment, and reviewer. Define who can pause the campaign and how rollback works. A launch should not proceed because most checks passed if a critical control fails. Privacy, accessibility, payment, or security defects require the responsible specialist, not an informal workaround. For accessibility checks, record the applicable WCAG 2.2 criterion, method, environment, result, evidence, and unresolved limitation. A partial checklist must not be represented as a WCAG conformance determination.

Before you begin

  • Confirm F07, F08, and F11; record that event schema, parameter convention, accessibility/mobile results, privacy approval, signatures, and launch authorization are absent.
  • STOP. If the event schema, parameter convention, accessibility/mobile evidence, or privacy authorization is missing or conflicts with F07/F08/F11, route the preflight to authorized analytics, privacy, and accessibility owners; do not claim tracking approval or execute testing or launch.

Original overview module anchor →

02 · Compare the artifacts

Supported work. Visible uncertainty.

This fictional, sanitized training case contains fabricated campaign and audience data. It includes no real personal or confidential records and does not provide legal, privacy, advertising, or revenue guarantees.

JuniperWorks campaign launch gate

JuniperWorks is a fictional provider of workflow software for regional construction firms. The marketing team proposes a webinar campaign called Reduce Project Delays, with a $24,000 media and production budget. The draft objective is generate awareness, while finance expects 80 qualified registrations and sales can accept no more than 20 discovery handoffs during the campaign month. The proposed audience file has 9,400 business contacts. Of those, 1,100 are existing customers, 620 have opted out, 730 came from a trade-show scan without documented follow-up permission, 240 are duplicates, and 85 contain free-text personal observations. The landing page promises users can cut delays by 35 percent. That number comes from three selected customers; the full eight-customer review ranges from a 9 percent increase to a 31 percent decrease, with different definitions and periods. Design has approved version 7, but the live page is version 6 with an old price. The analytics plan uses five campaign parameters inconsistently and has no test for duplicate conversion events. The form routes every submission to sales, including students, vendors, existing customers, and incomplete records. Sales wants a one-hour response target, but coverage exists only during Mountain Time business hours. Legal and privacy review are still pending, the speaker release is unsigned, and one image license cannot be located. Leadership asks to launch Friday because ad inventory was reserved. Learners must convert the brief into a decision-ready objective, build an appropriate audience, control content and asset versions, preflight tracking and claims, design a two-way handoff, and report results with limitations. Reserved media and executive enthusiasm do not replace release evidence.

Supported example — reference only

Step or milestone
TRACK-01
Trigger or date
Before preflight execution
Evidence and source ID
F08: campaign parameters are inconsistent and duplicate conversion events are not tested.
Owner
Marketing operations/analytics owner
Gate or threshold
Learner proposal: one controlled parameter convention and a duplicate-event negative test.
Dependency or gap
Approved event schema and execution evidence not supplied.
Status
Draft — test pending

A well-handled evidence gap

Step or milestone
TRACK-02
Trigger or date
Before launch approval
Evidence and source ID
F07: live page is version six with an old price; F11: legal/privacy review incomplete.
Owner
Marketing and privacy reviewers
Gate or threshold
Gate: correct version and required approvals must be evidenced.
Dependency or gap
Approval, accessibility result, and signature not supplied.
Status
Blocked

Flawed approach — do not copy

Marking this campaign tracking plan “approved and complete” without the required evidence or reviewer is a flawed submission. Stop launch for duplicate conversion, privacy/accessibility failure, stale asset, unsupported claim, or missing approval.

Repair: Rework the campaign tracking plan as an evidence-backed draft, not an approved result. Inventory required events and parameters as proposed definitions. Use F08 to define one controlled campaign-parameter convention. Design success, duplicate, invalid, opt-out, and system-failure paths. Check the revision against this requirement: Event and parameter conventions and five path types are specified. If the required evidence is still absent, keep the decision blocked and identify the missing input or authorized reviewer.

Full case record, ambiguities and all assignments →

03 · Bounded practice

Build the campaign tracking plan.

Specify event, parameter, form, routing, accessibility, mobile, privacy, and failure tests.

Deliverable: A tracking plan and preflight evidence-capture checklist with execution, signature, and results fields explicitly pending.

Complete a bounded starter and gap analysis using only CB01, F07, F08, F11, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

Exact supplied inputs for this assignment
  • M04-I01 · F07 — The approved design is version seven and the live page is version six with an old price.
  • M04-I02 · F08 — Campaign parameters are inconsistent and duplicate conversion events are not tested.
  • M04-I03 · F11 — Legal and privacy reviews and the speaker release remain incomplete.
  • M04-B01 · CB01 — Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
  • M04-S01 · F07, F08, F11 — Build a starter version of “A tracking plan and preflight evidence-capture checklist with execution, signature, and results fields explicitly pending.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

Operating procedure

  1. Inventory required events and parameters as proposed definitions.
  2. Use F08 to define one controlled campaign-parameter convention.
  3. Design success, duplicate, invalid, opt-out, and system-failure paths.
  4. Specify event deduplication evidence and failure handling.
  5. Place privacy, accessibility, claim, and version failures behind a launch-blocking gate.
  6. Route execution evidence and approval to marketing operations, analytics, privacy, and accessibility reviewers.
Field-by-field guidance
Step or milestone
Name one ordered action or decision checkpoint. Module use: Use the plan to specify tracking behavior and launch gates before any test is run.
Trigger or date
Use a supplied trigger; write date not supplied when absent. Module use: Use the plan to specify tracking behavior and launch gates before any test is run.
Evidence and source ID
Pair the observation with its exact supplied source ID. Module use: Use the plan to specify tracking behavior and launch gates before any test is run.
Owner
Name the authorized operating or specialist role. Module use: Use the plan to specify tracking behavior and launch gates before any test is run.
Gate or threshold
State a measurable provisional gate and who must approve it. Module use: Use the plan to specify tracking behavior and launch gates before any test is run.
Dependency or gap
Name the evidence, owner, or prerequisite that blocks progression. Module use: Use the plan to specify tracking behavior and launch gates before any test is run.
Status
Use a truthful state such as draft, open—not supplied, review pending, or blocked. Module use: Use the plan to specify tracking behavior and launch gates before any test is run.
Campaign tracking plan · learning draft
Step or milestoneTrigger or dateEvidence and source IDOwnerGate or thresholdDependency or gapStatus

Start with 6 rows; the complete workbook specifies 8 stable rows for this artifact. Add rows here or use the full download. No action is saved until you explicitly choose saving above.

Download complete six-module workbook (.md) · Structured case packet (.json)

Keep private client data, unpublished inventions, personal identifiers and credentials out of these public learning tools.

Module 4 · 2-item formative check

Tracking plan and preflight QA

Choose an answer and request feedback. Read why each option does or does not fit the evidence. Answers stay in this tab unless you choose device-only saving; they are never submitted.

Question 1 of 2 · MODULE 4 · knowledgeA privacy-critical preflight test fails before launch. Which response follows a defensible release gate?
Question 2 of 2 · MODULE 4 · scenarioF07 confirms an approved-versus-live version mismatch, F08 confirms inconsistent parameters and untested duplicate conversions, and F11 confirms incomplete legal, privacy, and speaker review. Which preflight finding is actionable?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • Event and parameter conventions and five path types are specified.
  • Every test has expected evidence and pending result.
  • Launch-blocking gates and owners are explicit.

Stop: Stop launch for duplicate conversion, privacy/accessibility failure, stale asset, unsupported claim, or missing approval.

Go: Proceed to controlled test only when event/parameter definitions and evidence-capture method are approved.

Escalate: Escalate privacy, accessibility, claim, and version failures to their qualified owners.

04 · Evidence to keep

Leave with usable work.

Submit the tracking specification, test evidence, defect log, release decision, and rollback owner.

Download your artifact CSV and, if wanted, export the learning-work JSON above. Neither export is a reviewed submission or certificate. Device-only saving is optional; you must press Save my work now after edits.

When all six artifacts are ready, compare the full packet against the track rubric. Qualified human review is still required before real-world decisions.

Marketing operator coordinating campaign work on a laptop.
Learn the standard. Practice the work.
Marketing colleagues collaborating on digital campaign execution.
Leave with evidence you can inspect.

Sources, scope and review boundaries

Curriculum 2026.10.08-learning-paths-1. External source dates below are record checks, not continuing guarantees. Verify current requirements before consequential use.

ftc-can-spam · Official guidance

CAN-SPAM Act: A Compliance Guide for Business

FTC explanation of U.S. commercial-email requirements, opt-outs, sender information, and responsibility for vendors.

Open reviewed external source ↗

nist-privacy-framework · Official guidance

NIST Privacy Framework

A voluntary primary framework for identifying and managing privacy risk in products, services, and data processing.

Open reviewed external source ↗

w3c-wcag-22 · Standards-body recommendation

Web Content Accessibility Guidelines (WCAG) 2.2

Normative W3C Recommendation. Select and test the success criteria applicable to the content and target conformance level; a checklist or partial test is not a conformance claim.

Open reviewed external source ↗

ws-marketing-operating-control · Academy internal operating standard

Wealth Synergy marketing-operations internal operating standard

Academy-selected campaign, approval, suppression, asset, preflight, routing, reporting, and archive controls. This is an internal operating standard selected by Foundry Academy; it is not law, accreditation, licensure, or an external-standard requirement.

Version 1.0 · reviewed 2026-09-01 · owner: Foundry Academy curriculum owner

A future Wealth Synergy private professional-development certificate would be issued only after its assessment, capstone, identity, reviewer, retention, access, deletion, appeal, and issuance controls pass quality review. No credential is currently issued. Any future certificate would not be an accredited academic qualification, professional license, or government certification.