Send a test email

Send a reviewed email sample to your own inbox before launching the campaign. A test lets you inspect the sender, layout, links and wording in an actual email client. It sends to the address you type, using the sample you rendered in the composer.

What a test send is

Send test uses the existing rendered preview. It prefers the generated personalized sample when one is available; otherwise it uses the Base sample. It does not generate new Adaptyle content as part of the test action.

The same control appears in broadcast, template and workflow email composers. A test is a real transactional send through your selected verified sender and consumes email allowance. It has no production contact association and the action does not start your workspace’s email-event workflows or webhooks.

Before you can send a test

Render a preview first; until one is available, the toolbar control is disabled. Select From on a verified domain. Sending also requires Write permission, available allowance, enabled workspace sending and an address that passes transactional suppression checks.

For example, preview an announcement using a customer with a first name, then use a sparse sample to check that “Hi there” replaces the missing name. Regenerate the personalized sample for the customer you want to review before sending the test. Switching the on-screen preview to Base does not make Send test ignore an available personalized sample.

Send a test email

1. Open the email’s Composer and select its sender.
2. In Data → Sample, choose the customer and any other inputs. Edit as JSON changes the sample without changing the customer record.
3. Open Preview. Check Base for Liquid and fixed content. If the message has Adaptyle, configure Model and Thinking under Personalize → Runs with, then return to Preview → Personalized → Generate preview. Generate again after changing the sample.
4. Choose Send test, enter your own address and confirm.
5. Inspect the received subject, preview text where supported, body, image fallback, links and footer. Check the clients and screen sizes your audience uses.

The image shows a rendered sample; it does not demonstrate inbox delivery. Generating a personalized preview uses credits, while sending the resulting test uses email allowance. Check usage before repeated tests.

How a test send differs from a real send

A test checks one rendered sample in one inbox. It does not verify the production recipient mapping, audience, marketing subscription, topic eligibility or campaign quality release. The test action also does not apply the template’s Cc and Bcc copies.

It sends the rendered body you reviewed. Do not treat a link visible in sample content as proof that production unsubscribe handling has been exercised. Review marketing eligibility on the actual contact and campaign separately.

If the test is refused, read the message: repair the sender/domain, check allowance or investigate the address’s bounce suppression. If acceptance is uncertain, inspect the email history before another attempt. If accepted but absent from your inbox, check the receiving account’s folders and delivery activity.

Once the sample is right, return to the broadcast review or template handoff.