Once you’ve created your first email you’ll want to be sure to test before setting your campaign to active. To do this, it will depend on the type of campaign you’re sending.
With triggered campaigns, we recommend a 2-prong testing approach. First, you’ll want to send yourselves test messages from the specific emails by entering your email addresses separated by commas in the field before “Send test” and then pressing the button. A “Test sent!” message will be displayed if the test is sent correctly. You can also choose whether or not to add “[TEST]” to the subject line:
If your email contains any customer attributes you can choose the user whose details you want to merge in for the test from the left-side “Sample data” tab.
For event triggered campaigns, you will only be able to test with users who already performed the event. If they haven’t you’ll see an error that “event” or “event.DATA_NAME” is missing in the “Preview” tab.
Don’t worry, the email will only send to the address you’ve specified, the customer’s attributes you’re merging in are just for testing purposes.
The second of your testing approach, should be to either trigger the campaign for a test user so that you can see the full series play out, or leave your emails as “Queue Drafts” while actual users match the campaign. From there you’d want to check several times a day to send drafts and make sure all is well.
For anonymous events (events not tied to a user inside your Customer.io), you will not be able to see any “Sample data” users. The only way to test campaigns based on such events is by setting the emails to “Queue Draft”.
For newsletters, we recommend sending a test email, just like in the triggered email suggestions above.
For all types of email, once you’ve finished testing, either click send (for newsletters) or set your emails to “Send automatically”. Then sit back and watch your reports begin to fill in.