> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onchainsuite.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Launch and Monitor
> Launch a campaign and read the metrics — including exactly how each rate is calculated.
## Before launch
* Validation passes with no errors
* Preview reports no missing merge fields
* A test send rendered correctly in a real email client
* The audience estimate matches what you expect
* Sender identity is verified
## Launching
Launching re-runs validation and stops if anything is outstanding. It then checks your monthly allowance against the estimated recipients plus what you've already sent this calendar month, and blocks the send if it wouldn't fit.
Only draft and scheduled campaigns can be launched — one that's already sending or sent can't be launched again.
Scheduling does **not** send. There is no scheduler — a campaign left in `SCHEDULED` stays there indefinitely. Launch manually at the intended time.
Sending is asynchronous: the campaign moves to **Sending**, is delivered in batches, then moves to **Sent**.
## Metrics
Campaign analytics cover email and in-app separately, plus a combined total.
### Email
| Metric | Definition |
| ----------------------------------------------------- | ------------------------------------ |
| Sent | Queued plus sent |
| Delivered | Confirmed by the provider |
| Unique opens | Distinct recipients who opened |
| Total / unique clicks | All clicks, and distinct recipients |
| Bounces, complaints, unsubscribes, suppressed, failed | Negative outcomes |
| Delivery rate | Delivered ÷ sent |
| Open, click, unsubscribe rate | Over delivered, falling back to sent |
| Click-to-open rate | Unique clicks ÷ unique opens |
Rates are percentages rounded to two decimals, and zero when the denominator is zero.
Open and click rates use **delivered** as the denominator only when delivery confirmations are flowing. If they aren't, delivered is zero and the denominator silently falls back to **sent**. Compare the two before reading too much into a rate.
### In-app
Sent, delivered, viewed, clicked, and dismissed, plus delivery, view, click, and dismiss rates.
In-app has no open pixel — delivery is reported by the client when it receives the push, which makes it more reliable than an email open, not less.
## What to watch
A rising bounce rate damages sending reputation for every future campaign. Hard bounces are suppressed automatically, but the underlying list-quality problem is yours to fix.
Click-to-open is the honest engagement signal — open tracking is increasingly blocked by mail clients, so open rate alone reads low and noisy.
An unsubscribe sets a flag on the contact that every future campaign honors. Watch the rate per campaign, not just the total — a spike means targeting or frequency, not content.
The reason to send from a wallet-aware platform. Query [`contact_360`](/api/sql-schema) or `wallet_activity_summary` to see whether recipients actually transacted after the send.
## Audit trail
Every campaign keeps a history — drafted, audience updated, tracking updated, test sent, scheduled, launched, sent — in order. This is the fastest way to answer "who changed the audience before this went out".
## Workspace view
The analytics overview aggregates across campaigns for a window of 1–90 days and shows how much of your monthly message allowance is used and remaining. On Pay as you go it shows usage without a cap.
The workspace overview counts **total** clicks rather than distinct recipients. When that difference matters, read unique clicks from the individual campaign instead.