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

Glossary term

Stack Record

The live register of every marketing tool: owner, deputy, cost, notice date, users, use cases and status, kept current by onboarding, reviews and retirement.
StrategyconceptUpdated

Definition

A stack record is the live register of a business's marketing tools, including any that are still running unused. Each tool has one row, and each row carries the same short set of facts: who owns the tool and who deputises, what it costs, the last date for giving notice, who uses it, which use cases it serves and where it stands in its life, from onboarding through live to retired.

It begins as an audit's inventory. The step-by-step stack audit tutorial hunts for tools through spending records, sign-ins and whatever loads on the website, and the table it fills in turns into the stack record when the audit closes. The difference between the two is time. The inventory is a snapshot taken to support keep, fix, consolidate and retire decisions; the record is the same table kept true between audits, so that the next one starts from it.

What each row holds and who keeps it

The fields are few on purpose, so that keeping the record current stays cheap. Owner and deputy say who can administer the tool and who answers for it. Cost and notice date tie it to the budget and the renewal calendar. Users and use cases say what would be lost if it went. Status says whether it is arriving, live or leaving.

The marketing stack management playbook gives the record to a single stack owner, marketing operations in the playbook's version, and makes it the one register that every phase of the programme reads and writes. Two of its rules define the term as much as the fields do: a change to a tool counts as finished only once the record shows it, and the record is kept where the team already works, linked from the onboarding pack, rather than in one person's files.

In practice: onboarding, access reviews, renewals and retirement

Onboarding. The marketing tool onboarding SOP enters a new tool with the status "onboarding" as soon as its purchase or trial is approved, so colleagues know it is on the way, and moves it to "live" only after the adoption review.

Access reviews. The tutorial on reviewing who can sign in to marketing tools starts from the record's list of tools and owners, then builds its own register beside it with one row per account rather than per tool.

Renewals. The playbook builds its renewal calendar from the notice dates in the record and reads it every month, so that each renewal review begins while renewing, renegotiating, replacing and retiring are all still possible.

Retirement. The tutorial on retiring a marketing tool begins from the tool's entry in the record and ends by marking the row retired, noting when, where its jobs went and where the exported data now lives.

Illustrative example — not a real result

A scooter hire firm finds tools its record never listed

Fostuane Scooters, an invented electric scooter hire firm operating in 3 cities, kept a stack record of 17 marketing tools. Its yearly audit read the company card statements alongside the record and found 4 subscriptions the record had never listed: a landing page builder, a survey tool and 2 design apps, all bought for a launch campaign 14 months earlier and all still renewing monthly at £96 a month between them. The stack owner added each to the record with a named owner and a notice date, and the owners decided within the week. The landing page builder stayed, because it still hosted the referral page; the other 3 were retired in order, with notice given before their next renewals. The audit closed with 18 live tools in the record and 3 rows marked retired, each with an owner and a status.

The Notice Date is the date column a renewal turns on, because it comes before the renewal and the playbook's calendar is built from it. An Integration Register covers what the stack record leaves out on purpose: each connection between tools, with what moves, how and under whose credentials. An Access Review takes the record's tools and owners as its starting list and checks every account against them. Why a tool was chosen, renewed or retired is kept apart from its row, in the decision records the playbook lists or in the team's Decision Log. A Consent Map is arranged by purpose rather than by tool, and the playbook updates it when a newly onboarded tool reads or holds consent state.

Common confusions

  • The stack record is the audit. The audit is a periodic exercise that ends in a decision on every tool; the record is what it leaves behind and what keeps changing between audits.
  • It is a record in the CRM. It lists tools, not contacts or accounts held inside any one tool.
  • It holds every connection and every login. Connections belong in the integration register and accounts in the access register; the stack record sits beside both.
  • Each tool owner keeps their own row. Tool owners answer for their tools, but the record has one keeper, and every phase of the programme writes to it.
  • The renewal date is the date to record. The row needs the notice date, which falls first and is the one that can be missed.

More terms to look up

Where this term is used

Related