Skip to main content

Email Testing and Preview

Learn how to test and preview your email campaigns with real user data before sending.

Overview​

Joryio provides comprehensive email testing capabilities that allow you to preview emails with actual user data and send test emails to yourself or team members. This ensures your personalization works correctly and your emails look great before sending to your entire audience.

Features​

Email Preview​

Preview your email templates with real user data to see exactly how personalization will appear.

Three preview modes:

  1. Existing User - Preview with data from an actual user in your database
  2. Custom User - Preview with custom test data you define
  3. Customize User - Start with an existing user and override specific fields

Send Test Emails​

Send test emails to yourself or team members to verify deliverability, rendering, and functionality.

Supported scenarios:

  • Test with existing user data
  • Test with custom user data
  • Send to multiple recipients
  • Override user attributes for testing edge cases

How to Use​

Previewing Emails​

  1. Open your campaign in the email editor
  2. Click "Preview & Test" in the toolbar
  3. Choose your preview mode:

Existing User Mode​

  • Search for a user by email, name, or ID
  • Select the user from search results
  • The email preview updates automatically with their data
  • See all user attributes and how they render in the email

Custom User Mode​

  • Enter custom test data:
    • Email address
    • First name
    • Last name
    • Custom attributes (as JSON)
  • Preview updates in real-time

Customize User Mode​

  • Search and select an existing user
  • Override any fields you want to test
  • Useful for testing edge cases without modifying real user data

Sending Test Emails​

  1. Open your campaign in the email editor
  2. Click "Send Test" button in the toolbar
  3. Choose your test mode (same three modes as preview)
  4. Add test recipient emails:
    • Enter email addresses
    • Add multiple recipients
    • Remove recipients with the X button
  5. Click "Send Test Email"

The test email will be sent using your configured email provider with the user data you selected.

Sender, Reply-To & BCC in test sends

A test send uses the same sender, Reply-To and BCC as the real send - including the per-variant sender for A/B campaigns. A Custom From must be on a verified domain (SPF+DKIM), exactly like production; sends from an unverified domain are refused. Configure senders and the Reply-To / BCC lists under Email Configuration.

Test sends match live sends - and respect suppression

Test sends render through the same renderer as live sends, so personalization tokens, custom attributes, and content blocks resolve exactly as they will in production - a test never differs from the real result. Suppression is enforced on test sends too: a suppressed address is refused rather than emailed. Test sends are always free - they never count toward billable engaged profiles.

Test sending is also available for email nodes in journeys - each email message node has a Send test message button with the same user picker. See Canvas Nodes.

Template Variables​

All template variables are replaced during preview and test:

Hello {{ user.firstName }}!

Your email is: {{ user.email }}
Account type: {{ user.attributes.plan }}

Supported Variable Patterns​

  • {{ user.fieldName }} - Standard user fields
  • {{ fieldName }} - Fallback pattern
  • {{ user.attributes.customField }} - Custom attributes

Common Fields​

  • {{ user.firstName }} - User's first name
  • {{ user.lastName }} - User's last name
  • {{ user.email }} - User's email
  • {{ user.phone }} - User's phone number
  • Custom attributes from your user data

Search Functionality​

The user search supports:

  • Email addresses - Including special characters like + and .
  • Names - First name or last name
  • User IDs - 24-character hexadecimal IDs
  • External IDs - Your custom user identifiers

Search is case-insensitive and searches across all these fields simultaneously.

Best Practices​

Before Sending Campaigns​

  1. Test with real users - Use the existing user mode to verify personalization works with your actual data structure
  2. Test edge cases - Use custom user mode to test:
    • Missing fields (empty names, no attributes)
    • Long text values
    • Special characters
    • Different user segments
  3. Test across devices - Send test emails to different email clients:
    • Gmail
    • Outlook
    • Apple Mail
    • Mobile clients
  4. Verify links - Click all links in test emails to ensure tracking and destinations work

Testing Personalization​

  1. Test missing data - What happens if firstName is empty?
  2. Test special characters - Names with apostrophes, accents, etc.
  3. Test long content - Very long names or attribute values
  4. Test different segments - Free vs. paid users, different plans, etc.

Team Collaboration​

  • Add multiple test recipients - Include team members for review
  • Test different scenarios - Each team member can represent a different user type
  • Verify rendering - Different email clients render emails differently

Troubleshooting​

No Users Found​

If search returns no results:

  • Check your search query for typos
  • Verify the user exists in your database
  • Try searching by email instead of name
  • Make sure you're in the correct workspace

Template Variables Not Replacing​

If variables aren't being replaced:

  • Check the variable syntax: {{ user.fieldName }}
  • Verify the field exists in the user data
  • Check for typos in field names
  • Custom attributes must exist on the user

Test Email Not Received​

If test emails aren't arriving:

  • Check spam/junk folders
  • Verify email provider is configured correctly
  • Check provider dashboard for errors
  • Ensure test email addresses are valid

Technical Details​

Email Provider​

Test emails use the same email provider configuration as your campaigns:

  • SendGrid
  • AWS SES
  • SMTP
  • Mailgun
  • Bird

This ensures test emails behave exactly like production emails.

Authentication​

User search and test email endpoints are authenticated and workspace-scoped, ensuring:

  • You only see users from your organization
  • Tests use your workspace's provider configuration
  • All actions are audit-logged