> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cliqo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Pre-send analysis and test email

> The automatic checks before the send, and how to test the email for real — interactive part included.

## What you will learn

What the pre-send analysis checks, how to send a real test, and which problems block the send until they're fixed.

## Run the pre-send analysis

On the **Review** tab, click **Run pre-send analysis**. It checks:

* **Sending domain** — whether the sender has an address with a domain filled in.
* **Blacklist (Spamhaus / SBL)** — this lookup isn't performed from there today, and the analysis says so ("Not checked here") instead of faking an "ok".
* **Subject content** — words associated with spam, whole words in ALL CAPS, too many exclamation marks.
* **Personalization tags** — broken or mistyped tags. The analysis even catches the classic `|` swapped for an `l` (`{{primeiro_nomelOlá}}`), which would make the email go out with the literal code in the text.
* **Unsubscribe link** — the one-click unsubscribe header (List-Unsubscribe, required by Gmail and Yahoo) is injected automatically into every send.
* **Sending authentication** — DKIM on the sender's domain (and the Return-Path, when configured).

## Send a test email

**Send test** sits at the top of campaign setup, on every tab (it needs a template chosen), and also on **Review** (which shows when the last test was sent). Pick a **Test list** and/or type several addresses separated by commas under **More emails**. The test sends the **real** email — with the interactive part and the fallback, and with the draft's subject, preheader, sender and UTMs —, arrives with `[Test]` at the start of the subject, and **does not count toward the campaign's metrics**.

Open the test in Gmail and in at least one other client (Outlook or Apple Mail) to see both versions. If the test arrives static in your Gmail, see [Why my email arrived static](https://docs.cliqo.io/en/email-interativo/por-que-chegou-estatico.md) — on an account without the sender registration propagated, that's expected.

## What blocks the send

Some problems prevent the send until they're fixed, with the reason on screen:

* **Empty required fields** — internal name, subject, sender (name and email), template, an audience with at least one recipient and, when scheduling, the date. They show under "Fill in before sending" and the send button stays disabled.
* **Brand details** — without the brand's **Physical address** (and **Legal name**) under **Settings › Sending**, the send is refused.
* **Unregistered products** — the template references SKUs that don't exist in the catalog ("Register the products before sending", with a **Register** button).
* **Tags from another platform** — the imported email still has variables from another ESP that would go out as literal text; the editor converts the ones it recognizes and points out the rest.
* **Permission** — sending a campaign requires the Editor role or above.

With **Send now**, these checks run when you click, and the reason shows right there in campaign setup. If something is only refused at dispatch time, the campaign goes back to draft and the report shows "Not sent: …" with the reason.

## Related articles

* [How to create and send a campaign](https://docs.cliqo.io/en/campanhas/criar-e-enviar.md)
* [Checklist before your first send](https://docs.cliqo.io/en/entregabilidade/checklist-primeiro-envio.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.