Skip to main content
Productions

This article explains how you create a production and use it to analyze and communicate with your audience.

Zaklina Udovicic avatar
Written by Zaklina Udovicic
Updated over 10 months ago

Productions are a collection of events of your choosing. It can be a production based on the same kind of event but with different start dates, but it could also be all events within the same genre - only your imagination sets the limit.

This feature allows you to analyze sales and customers' demography for all events together. You can also trigger event automations based on productions.

ℹ️ Events are updated with data up until the start time. That means that productions will be updated up until the last event has taken place.

Create your production


Go to Sales → Productions in the main menu and click on Add production to get started. In the next step, you name your production and select those events you want to include. When finished, press Save.

As soon as you've started to create productions, each one will have a production card that will be visible when entering Sales → Productions. Each production card shows the name and date range based on the events, the total number of events included, and the status. The productions are always sorted according to the start date by default. This can be changed to the right where you see the Start date⬆ sign.

Upcoming and passed productions are separated. To look at passed ones, click on Passed next to Upcoming.

Analyze your production


When entering a production, you will have five main categories - Sales, Customers, Segments, Events, and Calendar.

The Filter button at the top-right corner allows you to exclude season tickets and free tickets.

ℹ️ Productions are updated with information about the involving events and customers on a daily basis, up until the last event has taken place.

Sales

This is where you get an overall sales view for the events in the production. Find out the total number of tickets sold and your top sales channels, or let the activity heatmap tell you what days of the week and hours of the day your customers are the most active buying tickets, etc.

In the sales chart, you can toggle between tickets and revenue. The blue bars show the number of season tickets sold or revenue per day, while the green line shows accumulated tickets or revenue (up until and including each day).

Tickets and the last 30 days are set by default, but you can change this at the top left corner of the chart. The timespan can be modified to the previous 30 days, the last 90 days, the last 180 days, and from when the sale started.

You can modify the shown timespan underneath the chart. Move the circles towards each other to narrow the dates further and get a better look.

Customers

This is where you get to know the customers of the production and their demography. How many, where are they from, gender, returning customers, age, etc.?

ℹ️ The location map shows you where your customers come from, not where they were based when making the purchase.

Segments

Here you find which segments all the events customers fit into. These are based on the segments you've created under Audience → Segments. Note that one customer can be part of several segments or not even one. Therefore, they don't have to add up to 100%, but they can also add up to more than that altogether.

As we mentioned earlier in this article - events are updated up until the start date, and productions up until the last event have taken place. This means that some segments you create might not be part of all events in your production, even if it is the same kind of event but with different dates.

For example: Let's say you create a segment on December 2nd based on an event tag that 10 of your events have. This segment should match all ten events, but 4 of those events took place before December 2nd, which means that your new segment won't be part of those four events and, therefore, will not add up to 100% among the segments of the production.

ℹ️ Not working with Segments yet? Read this article to get started.

Events

All events included in the productions will be found here.

To Add a new event to the production, head out from the production and go to Sales → Events. Find the specific event and click in the top left corner of that particular event card. Three icons will appear at the bottom of the screen, whereas the third one is Add to production.

If you want to Remove an event, go to the Events category for the production and click in the top left corner of that specific event card. Three icons will appear at the bottom of the screen, whereas the third one ( 🗑️ ) is Remove from production.

Calendar

A general calendar for all events in the production.

Use a production when communicating with your customers


You might want to communicate with your event customers for many reasons. Maybe to welcome them before the event through an Automation, or perhaps the event got canceled or rescheduled.

Directly from the Production view

When entering a Production, you find a Message button at the top right corner. Click on it to choose whether to send an email or SMS to all event customers involved in the production.

Through Automations

You can trigger an automation based on a production and communicate with those customers involved.

You can learn more about automations here.

Through regular emails

Thanks to the audience filter, you can communicate with the customers through regular email dispatches. If you wish to send a message to all customers in a production, you do this by using the Should Include block in the filter:

Should include → Orders → Add condition → Order item: ticket → Describe item → Production.

ℹ️ The filter will not pick up customers who bought season tickets. They are only included in automations. To read more about season tickets, click here.

Selected recipients in email dispatches

Automations will only pick up the email address used when making the order. While in regular email dispatches, all email addresses on the customer's contact card in MarketHype will be picked up as a recipient. Therefore, the recipients for an email dispatch might have more recipients than actual event customers.

Did this answer your question?