What’s the difference between preview and live testing?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

You've built your automation, the workflow looks right, and now you want to make sure it actually works before a real subscriber hits it. That's where preview mode and live testing come in. They sound like the same thing, but they catch completely different problems.

Preview mode is a visual sanity check. It shows you how your email will look, how merge fields will populate with real subscriber data, and whether your dynamic content blocks are rendering correctly. Think of it as flipping through a mockup. Nothing actually gets sent. No trigger fires. No system talks to another system.

That makes it fast and great for catching content mistakes. Wrong first name variable? Broken image? Off-brand headline? Preview finds those in seconds. But it has a hard limit: it can't tell you anything about what happens when the email actually travels through your sending infrastructure.

Live testing is the real thing. You fire the actual trigger, send a real email to a test address (or a small seed list, which is just a handful of addresses you control across different inbox providers), and watch what happens end to end. This is where you find out if the trigger is wired up correctly, whether your ESP is authenticating the send properly, whether timing delays are working as configured, and whether any conditional branches in your workflow behave the way you expect.

Live testing also surfaces deliverability issues that preview will never show you. If your sending domain has an authentication problem, or if a suppression list is accidentally catching your test contacts, you'd only know by sending a real email.

Here's the pattern that works well in practice: use preview mode for every round of content edits (it's fast and cheap), then do at least one live test before you activate the workflow. Check that the email lands, check the timing, check that the right version of dynamic content appeared for your test contact's profile, and check that nothing that should have been suppressed actually went out.

Neither one replaces the other. Preview tells you what the email should look like. Live testing tells you what the system actually does.

If you want to go deeper on validating your full workflow before launch, the question on how to test an automation before launch covers the full checklist. Or if something is breaking and you're not sure why, our SOS hotline is free.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Get help diagnosing your testing setup

Tell me which email testing issues you're dealing with. I'll help you figure out whether preview mode or live testing will catch the problem, and what to look for in each. Share: 1. Which ESP or automation platform you're using 2. What type of email you're testing (campaign, triggered automation, transactional) 3. What you're trying to verify (content, timing, trigger behavior, deliverability) 4. Any specific issue you've spotted or suspect

Edit the yellow boxes, then send to the AI of your choice.