Skip to main content
Campaigns depend on dynamic wallet traits and merge variables, so most send failures are personalization failures. A preview cycle catches them while they’re still cheap.

​
Preview

Preview renders the campaign exactly as the send pipeline would, the HTML, the plain-text version, any unresolved merge fields, and any warnings. Preview as a specific contact to check how personalization resolves for a real recipient. You can also override individual fields, which lets you test edge cases, a contact with no first name, or no ENS, without creating test data. The missing fields list is what will block your launch. Treat a non-empty list as a failing check even when the preview looks fine.

​
Test send

Send the rendered campaign to a single address for review. The same content overrides available in preview work here too.
Test sends are invisible to analytics. They carry no tracking pixel and no click wrapping, and record no delivery event. Opening or clicking a test email will never appear in campaign results, and can’t be used to verify that tracking works.
Test sends also skip the plan allowance check, so they won’t consume your monthly messages.

​
Why a test send fails

​
What to verify

Preview as a contact missing the optional fields. Every variable should degrade to something readable, Hey there, not Hey ,.
The sender is resolved from verified identities at render time. If the test arrives from an unexpected address, your intended sender isn’t verified, check the render warnings and Sender Verification.
Test emails are real emails, check them in an actual client, not just the preview pane.
Re-check the estimate. A segment whose criteria changed since you built the campaign will quietly change your recipient count.

​
Ready to launch

A campaign is ready when validation passes with no errors, missingFields is empty in preview, a test send renders correctly in a real client, and the audience estimate matches expectation. Continue to Launch and Monitor.