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

Glossary term

Change Control

The routine a proposed change to a live system follows: written down first, reviewed, tested, signed off and recorded before it reaches customers or data.
StrategyprocessUpdated

Definition

Change control is the routine that every proposed change to a live system goes through: tracking, automation workflows, tags, integrations and business listings. The tracking plan guide defines it as the process that moves a row of the plan between its states, from proposed to approved, implemented, verified and, eventually, deprecated. A new event or a renamed parameter is written into the plan first, reviewed by the analytics owner for consistency with the naming convention and the measurement plan, and only then handed over to be built.

The routine is the same wherever it appears, even when the names differ. What it is not is a ban on change. It lets change happen safely and keeps a trail of what happened.

The steps: write, review, test, sign off, record

  • Write it down first. The request says what will change, why, who owns it and what it touches. For a tag, the tag governance guide treats the request as the inventory row written in advance: the use case, pages and triggers, consent category, data sent and the condition for removing it.
  • Review by the owner. The person responsible for the system checks the change against its rules: the naming convention, the vendor review, the performance budget or the suppression and frequency rails.
  • Test where it cannot do harm. Seed contacts walk every branch of a workflow, a tag is checked in preview across consent combinations, a tracking change is verified on a Staging Environment before release.
  • Sign off. Someone other than the person who made the change confirms it works. For changes to shared assets, such as a global suppression list or scoring weights, that second review comes before activation.
  • Record it. The change goes into the system's change log with the date, the person, what changed and why, and with a way back if it fails.

How heavy each step is depends on the blast radius. An edit to one workflow's copy can proceed on the owner's authority with a log entry; a change to something every workflow depends on needs a second person.

In practice: tracking plans, workflows, tags, integrations and listings

The automation governance guide applies a lighter form of software change control to live workflows, because a change to a workflow is a change to what real people receive. The tag governance guide gives it two rules: only the governance owner and named deputies publish, and every tag outside the container is brought inside or removed, which is why Google Tag Manager (GTM) workspaces, versions and preview fit it so well. The guide to documenting marketing integrations makes the integration register part of it: a new connection is not live until its row is complete and its owner has signed off. For multi-location businesses, the guide to location pages and listings at scale says it matters most for openings, closures, relocations and holiday hours, each with an owner, an ordered list of systems to update and a later check that every copy agrees.

Illustrative example — not a real result

A physiotherapy chain stops its reports splitting in two

Plaxitor Physiotherapy, a chain of 9 clinics, tracks online bookings with a single event. During a site update a developer renames it to match a new booking widget, without telling anyone. For 3 weeks the analytics reports show bookings falling by about 40% at every clinic, while the clinic diaries are as full as ever: the bookings are arriving under the new name, which no report reads. The marketing manager reconciles the two series by hand and introduces change control for tracking. Every change is now written into the tracking plan as proposed, reviewed by the analytics owner, verified on staging by someone other than the developer, and recorded with its live date and the old name, so the next rename arrives with a cut-over date the reports can follow.

A Change Log is the dated record change control produces; keeping a log without the routine records surprises after the fact rather than preventing them. A Change Freeze suspends risky changes for a period, such as a trading peak, and tightens the routine rather than replacing it. A Staging Environment is where the test step happens for sites and tools. In GTM, workspaces, preview and version notes give tag changes the propose, test and record steps built in.

Common confusions

  • Change control is the change log. The log is one output. The routine is the request, review, test and sign-off that come before the entry is written.
  • Change control means a freeze. A freeze stops certain changes for a time; change control is how changes are made the rest of the year.
  • Small teams do not need it. The automation guide's answer is a lighter version: a log, a test with seed contacts and no edits to live workflows when nobody will be watching. The incidents it prevents are just as damaging for a small company.
  • The platform's edit history is enough. It records that something changed, rarely why, and never whether anyone checked it first.

More terms to look up

Where this term is used

Related