# Welcome

Personalization that feels 1:1, delivered at scale.

Welcome to Moonbrush. This documentation is your guide to integrating data, activating audience intelligence, and launching safe, high‑impact messaging—without exposing sensitive attributes or secrets.

***

### Who This Is For

* **Product & Growth** — launch playbooks, test ideas, read impact.
* **Marketing & CX** — craft copy, choose channels, respect fatigue & consent.
* **Data & ML** — ship events, manage features, monitor drift, and lift.
* **Engineering** — integrate SDKs/APIs, operate reliably.

***

### What Moonbrush Does (at a glance)

```
Sources  →  Ingest  →  Identity & Consent  →  Feature Store  →  Models  →  Decision API  →  Channels
(web, app,   (pixels, SDKs,             (durable+           (psychographics,     (ranked actions     (email, push,
commerce, ads) server)                    ephemeral)          personas, uplift)     & explanations)     in‑app, site)
```

* **Psychographics & Personas**: infer motivations, decision styles, and persona probabilities from behavior.
* **Intent Feed**: capture live actions and context; emit enriched, real‑time features.
* **Consumer Graph**: governed person record; safe views expose only approved fields for activation.
* **Audience Playbooks**: turn signals into exactly‑what‑to‑say/where/when—with caps and guardrails.

> Sensitive or protected attributes are **quarantined** and never used for activation without explicit communication, data usage agreement, and applicable SLA with end-user.

***

### Onboarding Checklist

* [ ] Establish data & privacy owner(s) and consent scopes.
* [ ] Send a minimal set of events (page view, search, add‑to‑cart, conversion).
* [ ] Data dumb and analysis for target audience understanding, micro-segmentation, and specific activation notes/quirks (relative to vertical, company, brand, etc)
* [ ] Custom psychographic model development
* [ ] Persona and playbook definition, guidelines, and activation
* [ ] Create holdouts and baseline metrics.
* [ ] Ship your first audience via Moonbrush platform, direct integration to preferred MarTech, or via API (coming soon)

***

### Safety & Governance

* **Consent**: purpose‑limited processing (analytics/personalization); revocation respected.
* **Sensitive fields**: quarantined; excluded from APIs, templates, and routing.
* **Guardrails**: frequency caps, fatigue, sensitive‑category blocklists, quiet hours.
* **Explainability**: decision reason codes per request.
* **Research-Driven:** in-depth research papers available upon request, justifying all standard models, personas, and playbooks available within the Moonbrush platform. 

***

### Document Map

#### Foundations

* Architecture Overview
* Data Governance & Consent
* Identity & Stitching

#### Data Plane

* **Intent Feed** — capture → enrich → segment
* **Consumer Graph** — person record & safe views

#### Modeling

* **Psychographic Modeling** — features, estimators, feedback loops
* **Standard Persona Models** — taxonomy, assignment, calibration

#### Activation

* **Audience Playbooks** — objectives, triggers, templates, measurement
* Decision API — ranking & reason codes

#### Build & Operate

* SDKs & Events Reference
* Observability & Testing
* Change Management & Versioning
* SLAs & Reliability

***

### Conventions Used in This Doc

* **Code** in monospace blocks; replace `<token>` and IDs with your own.
* **YAML/JSON** examples are **illustrative** and may omit optional fields. For security purposes, YAML/JSON examples may point to specific models, personas, playbooks, or columns that do not exist within the Moonbrush platform.&#x20;
* Times are **EST** on the intent feed and in **UTC** in all other instances, unless otherwise stated.

***

### Support & Feedback

* Use your workspace **support channel** or contact your account team in the console.
* Found an issue in the docs? Open a request with the page title and a brief description.

***

### Changelog (Docs)

* \*COMING SOON!\*

***

*© Moonbrush. All examples avoid sensitive categories and are for demonstration only.*

### Jump right in

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-people-group">:people-group:</i></h4></td><td><strong>Consumer Graph</strong></td><td>Core operational and reference database for persona analysis, micro-segmentation, and activation playbooks</td><td></td><td></td><td><a href="moonbrush-core-features/consumer-graph">consumer-graph</a></td></tr><tr><td><h4><i class="fa-chart-user">:chart-user:</i></h4></td><td><strong>Standard Psychographic Models</strong></td><td>Psychographic enrichments offered to all Moonbrush users (custom models always available)</td><td></td><td></td><td><a href="https://github.com/GitbookIO/gitbook-templates/blob/main/product-docs/broken-reference/README.md">https://github.com/GitbookIO/gitbook-templates/blob/main/product-docs/broken-reference/README.md</a></td></tr><tr><td><h4><i class="fa-globe-pointer">:globe-pointer:</i></h4></td><td><strong>Intent Feed</strong></td><td>Capture audiences as they're looking for <em>your</em> product collected from internet, social, purchase activity and more!</td><td></td><td></td><td><a href="broken-reference">Broken link</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.moonbrush.ai/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.