Activation Playbook
Make data actionable
Purpose
Audience Playbooks translate Moonbrush’s psychographic models, persona probabilities, and intent feed into concrete actions and words: who to target, when to speak, what to say, how to say it, and on which channel—under guardrails that protect users and comply with policy. This section defines the playbook object model, governance, and ready‑to‑ship examples.
Scope & Safety: Playbooks may not target or tailor creative using sensitive/protected attributes or their close proxies. Sensitive fields are quarantined and never exposed to decisioning. Use only approved signals (see SAFE_PERSON_VIEW).
What is a Playbook?
A Playbook is an executable strategy that combines:
Objective (e.g., trial start, first purchase, reorder, feature adoption)
Eligibility & Triggers (persona codes, intent patterns, thresholds)
Channel Plan (email, push, in‑app, SMS, on‑site, ads)
Message Templates (microcopy with variables and tone rules)
Frequency & Fatigue Controls
Measurement (primary KPI, guardrail KPIs, holdouts)
Fallbacks (low‑data and safety fallbacks)
Playbook Object (YAML)
The templating grammar supports persona‑aware branches (
persona switch), variables, CTA components, and safety notes (unsubscribe/consent reminders where applicable).
Tone & Microcopy Matrix (by Persona)
Deal‑First Explorer (PER-EXP-dealfirst-1.0)
energetic, concise, value‑forward
quick comparison, savings
"Start free", "See it now"
“Try it now—see what you unlock.”
Quality‑Focused Crafter (PER-QLT-craft-1.0)
confident, craft‑oriented
specs, guarantees, expert takes
“Explore”, “See quality”
“Experience the finish and feel.”
Skeptic Seeking Proof (PER-SKP-proof-1.0)
calm, precise, transparent
benchmarks, case studies, side‑by‑side
“See the proof”, “Compare”
“Here’s how we perform, in numbers.”
Habitual Loyalist (PER-LOY-habit-1.0)
warm, reliable, helpful
continuity, convenience
“Set it up”, “Keep it going”
“Fits right into your routine.”
Do: plain language, benefit first, respectful opt‑outs. Don’t: exploit fear, imply sensitive traits, or gate core info behind clicks.
Channel‑specific Guidance
Email
Subject: ≤ 50 chars; avoid spammy terms; one clear benefit.
Preheader: clarify value or safety (cancel anytime, privacy‑first).
Body:
First paragraph = benefit + outcome.
Middle = evidence (1–2 bullets).
End = single primary CTA.
Push
Title ≤ 45 chars, body ≤ 120 chars. Direct verb + benefit. Respect device quiet hours.
SMS
≤ 160 chars. Always include brand, value, STOP to opt out.
In‑App/On‑site
Minimalist banner + one CTA. Show reasons on hover/expand.
Segmentation Recipes
Trial Nudge: persona in {EXP, QLT, SKP, LOY} ∧
convert_7d ≥ 0.15∧fatigue ≤ 0.8∧ consent includes personalization.Compare Grid:
persona_any:{SKP, QLT}∧ recentpricing_page_viewwithin 24h.Loyalty Perk:
persona_any:{LOY}∧order_frequency ≥ cohort_p75∧ not exposed in last 30 days.
Implement via
POST /v1/segments/queryor decision policy with persona mixture routing.
Microcopy Blocks (Reusable)
Ready‑to‑Use Playbooks
PB-TRIAL-NUDGE (Conversion)
Trigger: pricing page → add to cart abandoned within 72h.
Primary KPI: trial starts (7d).
Sample SMS: “{{product_name}} free for {{trial_length_days}} days. Explore {{key_benefit}}—no commitment. Reply STOP to opt out.”
PB-COMPARE-GRID (Consideration → Conversion)
Trigger: competitor page visits or frequent spec lookups.
Creative: side‑by‑side grid; neutral tone; link to independent review.
Example CTA: “See the proof.”
PB-LOYALTY-PERK (Retention)
Trigger: high loyalty score + nearing reorder window.
Offer: early access/bundle convenience; avoid deep discounts.
Example Push: “Early access unlocked—your favorites, one tap.”
PB-REORDER (Replenishment)
Trigger: expected depletion window ±3d.
Tone: helpful reminder.
Example In‑App: “Running low? Reorder in 2 taps.”
Guardrails & Ethics
Blocklists: Sensitive categories and attributes; ideology/religion/ethnicity not available to templates or routing.
Caps: per‑channel and cross‑channel fatigue; quiet hours; novelty limits.
Safety language: include consent/unsubscribe where required; no dark patterns.
Research-Driven: In-depth research papers available upon request, justifying all standard playbooks available within the Moonbrush platform.
Measurement & Feedback Loops
Holdouts per playbook (min 5–10%).
Attribution: time‑decay plus uplift estimates.
Diagnostics: failure reasons (fatigue, policy block, low confidence).
Auto‑tuning: contextual bandits swap copy variants within caps.
API Quickstart
Decide:
POST /v1/decidewith persona probs, session context → ranked playbooks + templates.Render: client fills variables (
product_name,key_benefit, etc.) and respects caps.Log: exposure → outcome with
trace_idfor learning.
Request (abridged)
Response (abridged)
Compliance Checklist (per playbook)
Limitations & Assumptions
Cold‑start fallback uses contextual and content‑based templates.
Persona probabilities are estimates; prefer mixture routing when confidence is moderate.
Results depend on event fidelity and consented coverage.
Last updated

