How to send a test email
In this article, you will learn how to configure your system testing destination addresses and execute test email broadcasts to verify your formatting, layouts, and links inside customer inboxes.
What you will need:
- A SystemeScale account
- A dedicated, active testing email address
- An unlaunched newsletter draft or active campaign sequence item
1. Configure your default testing inbox address
Before triggering verification previews, establish your global workspace verification targets inside your master account configurations:
1
Navigate to native Email configurations
Click on your profile picture icon in the upper-right utility panel bar, enter the master Settings dashboard, and select the Emails tab on the left navigation layer.
2
Log your testing address parameter
Scroll down to locate the card module titled Testing. Input your preferred preview destination address directly into the empty text block field.
π
Recipient Address Activation Gate
To maintain strict anti-spam protocols and secure outbound server arrays, any address submitted within this block layout must be verified manually before it can process incoming server previews. Learn more in our Sender Confirmation Tutorial.
2. Triggering tests for bulk Newsletters
To verify the appearance of standalone broadcasts or one-time promotional templates before push execution:
3
Open your newsletter editor view
Navigate to your active newsletter workspace section layer (How to send or schedule a newsletter).
4
Push test block to mail servers
Inside your newsletter workflow settings page, click the primary Save and test action button. The platform will immediately drop a compilation preview copy into your logged testing inbox.
3. Triggering tests for automated sequential Campaigns
To audit formatting rules for individual milestones nested deep within automatic sequential tracks:
5
Access your campaign sequence track
Open your target campaign sequence panel framework (How to set up an email campaign) and select the specific email milestone draft item you wish to inspect.
6
Execute testing delivery validation
Inside the campaign step editor or configuration screen view, click the Save and test button to force an instant trial delivery run.
Technical constraints & deliverability guardrails
β οΈ
Isolate Test and Sender Targets
To guarantee precise routing tracking across network loops and completely eliminate internal loop deliverability problems, never use your verified outbound business sender email address as your target preview recipient address. Use a separate personal or internal testing alias.
βΉοΈ
Variable Parsing Restraint Notice
Dynamic contact personalization shortcode tokens (such as
{contact_first_name} merge values) **do not parse or populate literal data strings within a preview test environment**. Because a test email is uncoupled from real customer profile sheets, the codes remain unparsed. To preview a fully compiled live token structure, execute a real live send test to your personal contact profile card.π
Automation Rule and Workflow Exemptions
Currently, standalone raw email messaging actions configured directly inside localized automation rule containers or graphic multi-step funnel workflows lack a native "Save and test" trigger interface. To audit those items safely, execute sandbox runs using our test checkout patterns.
β
How to confirm your email sender address
Is your test delivery execution failing to route out from the platform workspace? Confirm that your custom sender credentials are validated and authentic in the system.
Was this article helpful?