On this page
In short. A marketing playbook is a named, versioned rule that watches one number in your advertising and raises a finding when it crosses a line declared in advance. Numeric conditions select playbooks, never a person browsing a list and never a language model.
How it works#
The catalogue ships with the product, and an organization can edit it or add rules. A threshold compares the latest value with a baseline: a trailing mean, the same period last year, the year-to-date mean or a percentile. The detection operators are the ones the morning brief uses (Signals and the morning brief).
Every rule measures itself in leads and raises an audit finding. None changes a budget or touches an ad platform. A rule below its evidence floor records "not enough data", never "fine". The horizon matches the problem: 7 days for an incident where money bought nothing, 14 days for the operating rhythm, 28 days for price and quality drift, where day-of-week effects would otherwise dominate.
The catalogue#
| Playbook | Fires when | Evidence floor | Horizon |
|---|---|---|---|
| Delivery cost spike | Cost per thousand impressions over 40% above the year-to-date mean | 500,000 VND spent | 14 days |
| Delivery cost in its worst quartile | Cost per thousand impressions above its own 75th percentile over 90 days | 500,000 VND spent | 14 days |
| Click-through collapse | Click-through rate over 30% below its 28-day mean | 500,000 VND spent | 14 days |
| Ad fatigue | Frequency at or above 3.0 and click-through 20% below its 28-day mean | 500,000 VND spent | 14 days |
| Impression saturation ceiling | Frequency at or above 4.5 on lead, traffic or content campaigns | 1,000,000 VND spent | 14 days |
| Landing page click loss | Over 30% of link clicks never became a page view | 1,000,000 VND spent | 14 days |
| Critical landing page loss | 60% or more of link clicks never arrived | 1,000,000 VND spent | 7 days |
| Cost per lead outside the target band | Lead cost outside the declared band, either direction | 90,000 VND spent, lead-objective campaigns | 14 days |
| Solution-tier cost per lead outside band | Lead cost above the higher declared band | 750,000 VND spent, lead-objective campaigns | 14 days |
| Lead cost drifting off baseline | Lead cost over 30% above its 28-day mean | 1,000,000 VND spent | 28 days |
| Result rate collapse | Result rate over 30% below its 28-day mean | 1,000,000 VND spent | 14 days |
| Spend with zero results | Material spend and results at or below zero | 1,000,000 VND spent, 2 days | 7 days |
| Efficient scale opportunity | Lead cost under the efficient ceiling, result rate at its 90-day median or above | 3,000,000 VND spent | 28 days |
| Spending ahead of plan | Over 20% above the pro-rated plan | 7 days, brand grain | 14 days |
| Spending behind plan | Over 20% below the pro-rated plan | 7 days, brand grain | 14 days |
| End-of-flight shortfall | Over 30% behind plan | 14 days, brand grain | 14 days |
Efficient scale is the one rule that reports good news: where more budget is likely to pay. The two delivery-cost rules are alternatives; run one per organization.
Counter-indications#
Suppression pairs are part of the rule set.
| This rule | Blocks | Because |
|---|---|---|
| Spend with zero results | Result rate collapse, same entity | A fall to exactly zero is an outage, not a decay |
| Either delivery-cost rule | The other one, and click-through collapse | They are alternatives; broader reach raises cost and lowers clicks |
| Cost-band rules | Lead cost drifting off baseline | An unacceptable price is the finding |
| Either fatigue rule | Efficient scale | More budget on a saturated audience re-buys the same people |
The frequency ceiling and the zero-result rule check the campaign objective, because high frequency and zero leads are normal for awareness campaigns. A campaign with no recorded objective is skipped.
How a playbook runs and is measured#
One evaluation serves four callers: the audit card on Marketing performance, the data assistant, the 07:00 brief and the rule editor's dry run. The scheduled scan runs Mondays at 06:30 Vietnam time over the closed Monday-to-Sunday week. It writes proposals with no approver; approving, rejecting and activating stay an owner or org admin step, logged in the audit log (Decision engine screens).
A finding becomes a proposal only if the organization declared a conversion metric and the guardrails passed. If the conversion feed returned no data for the window, the proposal is recorded as learning. With no CRM feed, leads resolve to nothing rather than zero, so a missing feed never scores a decision as a failure.
Adopting and tuning#
| Step | How |
|---|---|
| Read | Hệ vận hành Marketing > Thư viện playbook ngành (Marketing Systems OS > Industry playbook library) |
| Adopt the defaults | Seeding follows the organization's data: a marketing organization gets the marketing catalogue |
| Edit | The rule editor, with a dry run over the last 30 complete days; every threshold needs a written reason |
| Version | An edit writes a new version; evaluation reads the highest, and decisions keep the version they were made under |
| Turn off | Removes the playbook from evaluation, not only from the list |
The editor is in the platform console (Admin > organization > Playbook library), which a super admin opens; an owner or org admin can make the same edits through the server. Re-seeding never overwrites an edit.
Where it stops#
Where the library stands is on Project status. Nothing in a rule can move money or send anything outside the platform, and editing a threshold cannot change that. Operational chains with triggers are a separate screen, Automations (Decision engine screens). Rules on signals the platform does not store (site engagement, search visibility, email bounce) are held out: such a rule evaluates to unknown and never fires.