What's new in Elevent

Have you ever wanted an easy way to see all of your no-shows for one specific showtime? We've added a filter to the Showtime Entry Detail report to help you do just that.

First, head on over to and find the Showtime Entry report.

Next, choose any showtime to examine in greater details by clicking on that row in the list of showtimes.

This report is the comprehensive view of every bit of admission activity around this showtime. To also see who did not show up, flip the Include Unused filter to Yes.

The report will update. In the redemption list, you'll see red "x" marks next to every ticket that wasn't scanned in at the door.

This includes any ticket in a package or subscription; it will not include passholders since there's no firm indication they may show up.

This ability applies only to our cinema clients who use our SWIFT integration to auto-report weekly grosses.

In the occasional situation where SWIFT may ask you to resubmit the file, we've added the ability to download the SWIFT file from a prior submission in CSV format--the format SWIFT requires. That file can then be resubmitted directly.

For Comscore and Maccsbox, this was already possible but in the XML format they require.

Please see your agreement with these third-party companies to ensure you resubmit in a compliant manner.

Learn more about automated film box office reporting here.

This update relates to advanced, technical users; integrations to Elevent via the Elevent API.

We've made 2 helpful changes to the Elevent API used when integrating other systems to Elevent.

Reserved Seating Tickets are Grouped Together

Before, each individual reserved seat--its row and section--were broken out into individual items purchased in the responses from the Elevent API. This provided fine-tuned detail, but it meant the way ticket sales data on a customer was returned for reserved seats was structured differently from general admission shows.

For instance, before this change, when calling Get Customer by ID

api.goelevent.com/Customer

You'd get something like this, where each reserved seat ticket in an order stood alone.

"Tickets": [ { "TicketId": "vGaFF6JLfu", "TicketName": "Reserved Seat - Adult", "Row": "Z", "Seat": "107", ... }, { "TicketId": "vGaFF6JLfu", "TicketName": "Reserved Seat - Adult", "Row": "Z", "Seat": "104", ... },

Now, in a single chunk, all tickets of the same type in an order with reserved seats will display like this:

"Tickets": [ { "TicketId": "vGaFF6JLfu", "TicketName": "Reserved Seat - Adult", "Row": "Z", "Seat": "Z107,Z104,Z111,Z106,Z105,Z109,Z108,Z110,Z102,Z101,Z103", ... },

Making it consistent with general admission tickets makes it easier to integrate and accurately show ticket sales numbers for organizers who sell both general admission and reserved seating tickets. If you saw odd numbers in Salesforce while using the Elevent for Salesforce app, this change resolves that issue.

You might notice the row reappears with each seat. That's by design--since it's possible to sell tickets across multiple rows, this clarifies exactly where each seat truly is.

LastModifiedDateTime Now Reflects a More Useful Time Stamp

The LastModifiedDateTime on API responses is a useful timestamp for integrations to identify the most recent time period from previous requests--so changes could only be applied since the last request.

Before this change, the LastModifiedDateTime would show the most recent date and time the customer made any purchase or had customer activity--like updating their account, a refund, etc. In most cases, this is perfect.

However, there are times when we might force an update to a customer to trigger an update in a third-party system, like a CRM. The LastUpdatedDateTime stamps will now update when that activity occurs. In this way, any integrated systems will see they should examine and update any returned data since it might be newer.

Looking for API documentation? Check it out here.

As your staff and Elevent user list grows, you might start to pile up inactive users that clutter up your user list--former staff, seasonal staff, etc.

To help you manage your currently active users, we've added an Inactive user filter to the Staff Manager in your Account menu.

By default, we'll land you on this page with inactive users filtered out. To show all deactivated users, just flip this filter to Yes.

Enjoy your unlimited Elevent user abilities here.

People tend to spend a lot of time on the Showtime Details page for on scheduled showtime.

There's a lot going on with any showtime - the tickets available, allocations of inventory, sales, discounts, rules, on and off-sale times, and more. This busy page functions as a kind of dashboard in its own right, for one showtime at a time.

Customer Report

To help you quickly pull a list of customers or sales just for this one showtime, we've added a couple of quick buttons up near the top.

Press the Customer Report button and you'll see a list of all the tickets purchased and by whom. Nudge the purchase date a bit to make sure you get everyone over time.

This kind of customer list is most useful for general admissions tickets; if you are using reserved seating, the Seat Manifest will show you a customer list and all the visuals you need for seating.

Sales Report

Similarly, press the Sales Report button to view all sales just for that showtime--broken down by type of ticket, allocation, section, discounts, and sales channel. Handy info!

Bonus tip!

One of most overlooked features on the Showtime Details page lives towards the bottom of the page. Check it out in the Ticket Details section.

For the ultimate in x-ray vision, did you know you can switch the view of all tickets sold in a showtime to see the discounts or rules that are in effect?

Switch the view to Rules and you'll see which maxes apply across all the ticket rules.

Advanced topic--integration nerds only.

Webhooks are a handy, relatively easy way to trigger other systems you might use to automate or update when activity happens in Elevent. Running a membership welcome campaign or tracking each donation in a table somewhere? Webhooks can fire every time a certain item is purchased or event happens--and other systems can subscribe to these events fees, like Zapier, make.com, n8n, etc.

Are you using or planning to use Elevent's new Fan Out Audience Growth platform? Most of the solutions you have that use webhooks would likely be replaced by Fan Out. Webhooks are more for technical, solo builders.

Redesigned Webhooks for Gifting Scenarios

Head into the expansive Elevent page in the Back Office. Navigate to the Webhook Manager.

Before, it really wasn't doable to separate the events from when a giftable item was purchased vs. when it was claimed by the recipient. Now you can cleanly and clearly track both events.

When a giftable item is purchased as a gift, the new IsGift field will indicate the item was a gift.

A new webhook will fire now when any gift is claimed by the recipient--so any automated welcome routines you want to target these potentially new people can fire right then. And you can put the picture together between gift buyer and gift recipient.

Memberships

When someone buys a membership, we added the Membership code to the data returned.

It's been a treat seeing all the creative uses of custom order fields--those checkbox, dropdowns, and text fields you can present to customers when buying items or completing an order.

We've seen raffle entries, agreeing to terms & conditions, allergy notifications and meal choices, swag requests, and more.

The Custom Order Field report will spit out a live list of every reply. As usage has grown, flitting through this report needed a little love.

We've added some extra filters to help you make this report work for you.

Most notably, you can now filter to only responses made within a range of dates. These go by purchase date--so the date range still works by the time in which the order was made.

You can use these filters along with the others, so you can easily filter to a certain type of item and look at only a range of purchase dates.

Note that if you filter to only show responses for ticket purchases, you'll see additional filters--where you can filter responses for a specific showtime. So, for instance, if you ask patrons who might need listening-assistive devices, you can review responses show by show.

You can even elect to show empty responses--if you have some requirement to show when customers were presented with an option and didn't engage.

Review collecting additional info from customers during orders here.

Quicker Auto-sync intervals

Now you have an option to sync your Elevent events every 30 minutes instead of the default sync, hourly. To activate, simply select the 30 min option from the sync interval section when you enable Auto Sync.

If you have a deep schedule, tread carefully with this setting. You may get throttled or your website may time out.

Bug Fixes:

• Refactoring to use wp_remote for API calls instead of Httpful and cUrl combination
• Log cleanup, fewer warnings
• Refactoring of event sync

Unforeseen events happen. Whether it's a weather emergency, problem with the location, or whatever else might happen, sometimes you need to quickly and easily notify all ticket holders. Showtime Email Notifications make it easy.

Before, if you sent an Immediate email notification out, any scheduled email notifications would be canceled automatically.

Since that's not always what you might want, now you can send email notifications immediately and the scheduled reminders will still be sent out.

Note: if you do want to cancel those scheduled email reminders, now you'll need to manually do so--press the Delete All button for one or more showtimes.

Learn more about email notifications here.

We created the option in Event Calendars to easily hide sub-events from displaying. The default calendar behaviour now hides sub-events. No more workarounds needed.

Bug Fixes:

Moved acf-field-group call for blocks to correct position; resolved conflicts with standalone ACF installations

The Elevent Calendar block and shortcode have come a long way--revisit them here.