Quickly create, manage inventory, and publish events using TM1 Events. From real-time collaboration tools to drawing custom floors, TM1 Events allows you to build your event in a matter of minutes.
Check out our library of informative videos, reference guides and frequently asked questions.
Based on organization TCODEs you are granted the following permissions:
1. Full-Access: You are assigned a Host TCODE matching primary, secondary or tertiary permission slots of the event. If you have full-access you will also need the Manage Published Events permission for TM1 Events.
2. Request-Only Access: You are assigned a national TCODE matching slots 5-20 of the event. This also applies to Host TCODEs in any slot (1-3, 5-20) if you don’t have the Manage Published Events permission. Additionally, collaborators are granted request-only access.
3. No Access: If your TCODEs do not match any slots on the event, you cannot see the event. Event access is determined only by the TCODEs that all the users in your organization are assigned.
For instances where special TCODEs access is granted, please view the Inventory Status Report in TM1 Reports. Please reach out to TMPS for additional questions around permissions.
Yes, if a collaborator has been specifically invited to an event, they will show in the collaborator list. When hovering over the collaborator you will see a trash can icon to remove them from the event.
Requester/approval flow is available for changing price level value (dynamic pricing), moving seats to another price level (flexing), and changing seat status (reclassing).
Events using a master pricing event are fully supporting for all actions in Manage.
Events that are part of a series can be managed. Managing seats by changing the price level or seat status may make them unavailable for future management on the Series Master event. Series Master events cannotbe managed at this time.
GA seats can be changed by price level and moved to another price level and seat status. The price of GA sections can be changed, provided the sections do not contain multiple price levels. GA inventory from Archtics currently shows as “unknown”.
With CAS Static contract events, seat status can be changed, seats can be moved to another price level, and changed by price level. CAS client defined contracts are not supported. CAS client defined events will need to use Master pricing event to manage pricing changes.
Non-ISM inventory can be supported by Interactive Seat Grid (ISG). Seats on the ISG can be changed by price level and moved to another price level and seat status.
You can view distributed Host and in-house Archtics inventory. Archtics inventory is read only and cannot be changed or added to the cart. If you have used TM1 Events to change price levels of distributed inventory, the Archtics event will need to be manually updated to ensure the price levels match and the inventory is in sync.
In-house refers to Archtics inventory and populates inTM1 Events as read only on the map and cannot be changed.
Yes. Distributed commerce offers are available from the event list page by hovering the event and clicking the Create Partner Offers Link or by clicking Create Offer in the Offers section of the event.
Alerts are not currently available in TM1 Events. Please reach out to your Ticketmaster representative for more information on when additional functionality will become available in TM1 Events.
Scaling and Inventory can be exported to PDF. The ability to zoom PDF is available in TM1 Reports.
Comps are displayed on the interactive seat map, sales revenue dashboard, and the statistics report. Archtics comps are included as sold. Further comp breakdowns are available in TM1 Reports. Archtics comps will display as sold.
Platinum offers are maintained within the Platinum tool and not available for editing in TM1 Events.
Currently, any ticket type on the Standard table can be changed by price level (dynamic pricing). Any qualified offers using sold qualifiers associated with that ticket type will also be changed to reflect the new price.
Users with the Manage permission can manage:
1. Event Name.
2. Event Info, More info link and description, Online Please note.
3. Ticket Limit Text -this is just the online display text, not the actual ticket limit enforced.
There is currently no request flow for these fields.
Yes, only if you have been permissioned. To receive access to this beta functionality, please reach out to your Ticketmaster representative.
Events is an end to end event creation tool. It includes new functionality that has never been deployed in the legacy suite of products. These features include:
1. Ability to collaborate with others on an event build.
2. Ability to draw the floor for your event.
Events (beta) includes these features:
1. Self-service event creation workflow.
2. Interactive inventory seat map pricing and holds.
3. Live messaging and collaboration tools.
4. Streamlined offer creation.
5. Autosave and audit trail capabilities.
The legacy Scaling and Publish products will remain active during the roll out of Events as there are features in the current products that are not yet available in Events beta. Inventory has been deprecated in March of 2019.
The following features are not currently supported in Events (beta):
1. Display floor edits on Ticketmaster.com after published.
2. Runs longer than 10 events.
3. Create events on Archtics (Host only).
4. Enable edits to account settings.
5. Approve promotor bumps.
6. Create VIP offers.
7. Produce non-venue promoted events (promoter ID hardcoded to promoted by venue).
8. Create ADA seats when building a new floor.
EMT is an extremely powerful and flexible tool. Events beta does not yet include all the event functionality of EMT. EMT and Events beta can be used in a complimentary manner to ensure you have all the flexibility needed when creating live events.
Contact your organization’s Administrator to create your account. If you do not know who your Admin is, contact your CSS.
Yes. To provide you the best value and give the development team an opportunity to build new features based on your feedback, the Events product team is adding you to the beta in a deliberate manner. If you are interested in using TM1 Events, please contact your CSS. Please note that before you can use Events, you will be walked through a detailed onboarding process.
During the on-boarding process, your CSS or ESS will work with you to ensure that the appropriate ISMs are uploaded to your Events profile. If changes need to be made to the ISM’s associated with your profile, please contact your CSS. They can help with adding additional ISMs or removing ones you do not want to use anymore.
Settings are collected and configured during onboarding. To make a change to your settings, please contact your CSS. They will work with the Events team to have them updated.
Yes, when you create an event, an event code is automatically generated based on your event code prefix, the event month and date.
The attraction information and photo are pulled from the Ticketmaster Open Platform database. All attraction images in the Open Platform database have been reviewed and approved by the Ticketmaster team.
If you are unable to find the attraction you need in Events, reach out to tour ESS to have the attraction created.
Yes, you can manage and reprice your inventory after an event has been published along with select event fields listed above in the “manage” section. Any other edits to this event must occur on Host or EMT.
Yes, but just like the current ISM process, it won’t immediately update after an event is published. Once you publish an event, your CSS will receive an email to initiate the process for building the consumer facing ISM with your event’s floorlayout. Once they’ve completed the process, the Ticketmaster ISM team will run it through their quality checks. After the published event passes the quality checks, which usually occurs within a minimum of five (5) business days, the ISM will be published.
First, click the collaboration icon located on the Event dashboard page and a panel opens. Enter the email address associated with the collaborator’s Ticketmaster ONE (TM1) account. The collaborator must have a TM1 login to be able to see an event, so it’s important that you use the email address associated with that account.
Ticketmaster Product Support (TMPS) receives an email notification if the invited collaborator has TM1 access but does not have access to Events and will kick off the process for enabling access. Next, the collaborator receives an email giving access to view and edit (not publish) the event.
Important: Collaborators only see events to which they have been invited, and not all events inyour venue. They are only allowed to view and edit events; only you as the Box Office Managers can publish events.
If the collaborator’s organization is using TM1, their administrator will need to create an account for them. If their organization is new to TM1, please contact your CSS about getting their organization set up on TM1.
Yes, if a collaborator has been specifically invited to an event, they will show in the collaborator list. Hovering over the user will bring up a trash can icon and the user can be removed.
Yes, if the event is in draft status. The promoter will not be able to publish the event or view/edit the settlement code. The permission to create and/or publish an event and to select the settlement code belong solely to you as the Box Office Manager. Additionally, once an event is published, the invited promoter can request pricing and inventory changesand use the in-app messaging capabilities.
For all Events questions, please contact your Ticketmaster Representative or Ticketmaster Product Support (TMPS).