Jomablue is designed to be run multiple events for an organisation. Therefore there are common settings and attributes that exist across multiple events. 

One of the main benefits of this is that a person record can be persistent across multiple events. This enables deeper insight and engagement a person engaging with your brand.  

The problem with Test events, is the "Test" will persist forever as production data. 

For example, if you created a Test Event, with some test categories and some test people records, they will forever be visible across the event reporting in your Jomablue instance.

In addition, the level of effort to get a Test Event running in order to test some functionality, it's generally not worth it.

What we suggest

You Jomablue instance will come with a default test event called "Christmas Party". This is a playground for you too add people records and content to get a feel of how it works. Although categories and email templates you create in here will be persistent across production events, it can be filtered out in post-event reporting.  

If you're simply wanting to test an email, there is nothing stopping you from adding yourself to the production event as a person record, in the correct "staff" (or crew) category. You can then use the test campaign functionality to send yourself emails from the event. Therefore you are able to test the experience, without creating additional workload or disrupting event data.

If you're unsure, get in contact and we can help you run the test cases you want without affecting production insights. 

Did this answer your question?