Buyer Attributes
For every Buyer migrated from uTour or created from the Buyer request form, the DMO team will populate the following information:
| Attribute | Definition | Notes |
|---|---|---|
| Name | Official business name of the Buyer | |
| Buyer Type | Designates whether the Buyer is an individual or an organization | |
| Role Subtype | Designates the system or business process which does business with this Buyer | “Touring” is the only subtype currently being used |
| Address | Business address for the Buyer | Addresses must be explicitly marked as “Main” for the Buyer’s primary address and “Regional Office” for other office addresses |
| Phone | Primary phone number for the Buyer | Note that most buyer phone numbers will actually be connected to the buyer contacts working in the Buyer org. Phone numbers belonging to contacts are not to be associated with the main Buyer party |
| General contact email for the Buyer | Note that most buyer emails will actually be connected to the buyer contacts working in the Buyer org. Email addresses belonging to contacts are not to be associated with the main Buyer party | |
| Online Addresses: Website | Buyer's primary website | The main websites associated with the Buyer |
| External Records: Social Accounts | Social accounts for the Buyer | Any social accounts referenced on the Buyer's website |
| External Records: UTour ID | ID for the Buyer in UTour | For other system id references (e.g., UTour ID), the platform ID is maintained |
| Business Relationships | Links the Buyer to Venues and Events that they book talent for | |
| Appointments | Connects Buyers to individuals that work for the buyer organization |
More information on the full data model used for buyers within Auth Data is located here.
Names
Buyers are listed in Auth Data based on their legal business names. Trade names are logged as DBA (“doing business as”) names. Variations on the legal business name or trade names are logged as alias names.
Most (but not all) business names will have a business entity designator (such as “LLC”, “Corp”, “Ltd”, “LP”, or “LLP”) at the end of the business name. This designator is a necessary part of the business name and is always entered into Auth Data. Punctation with designators can vary, such as using “LLC” instead of “L.L.C.” in a business name. While not crucial, the DMO will always use the business name with the punctuation used in the official business registration.
Note that having a business name with an entity designator does not necessarily signify an official business name. There are generally no restrictions to using designators are part of trade name. For example, “Premier Vacations and Events, Inc.” is a trade name for “Premier Christian Cruises, Inc.”
Buyer Type
Individuals
Buyers may be individuals acting as sole proprietors or as sole employees of a registered business. In sole proprietorships, the individual’s name is the legal business name, even if they do business under a trade name.
This is distinct from the case where an individual is the sole employee of a registered business such as a limited liability company (LLC). Because there is a legal business entity involved, the buying party is the LLC, not the individual. If available, the individual can be logged as a buyer contact with the title of “owner” or “CEO”.
Organizations
Organizations are any buyers registered as non-sole proprietor businesses. This could be as small as an LLC with one employee or a corporation such as Live Nation with 32K+ employees spread around the globe.
Addresses
The “main” address for a Buyer represents the primary business location for the Buyer, such as the address for the business headquarters. Additional address types exist, such as addresses used for billing, shipping, payment, or for regional offices. Addresses for legal subsidiaries are recorded with those buyer profiles and not with the parent buyer.
Note that addresses used in a Buyer organization’s documents of incorporation are not logged within Auth Data unless they represent one of the available address types.
Contact Info and Online Addresses
Contact information (phone number, website and email address) will be captured by the DMO only if provided within a buyer create request or if the information is readily available on the buyer’s website.
It is important to note that any contact information or websites recorded by the DMO must match to the organization. Contact info for individuals working at the Buyer organization are logged against that contact, not the organization. See “Appointments” section below for more information about how individuals working at a Buyer organization are linked to the Buyer.
Phone numbers, email addresses, websites and social media links for legal subsidiaries are recorded with those buyer profiles and not with the parent buyer.
External Records
External Records link an Auth Data Buyer to distinct instances of the Buyer on other platforms. In cases where there are multiple instances of a Buyer in one platform, a single record is chosen and set as the “primary” link to that platform.
The following are the most common types of records that will be attached to a Buyer by the DMO:
- uTourId – Links the Auth Data instance of a Buyer to its instance in uTour. Note that there may be multiple versions of the same Buyer within uTour, which means that there may be multiple ExternalRecords for each uTourId. The DMO sets one of these records as the “primary” record. Within Touring, this is typically the uTour instance with the highest number of events/shows associated with it.
- NetSuite – Links Auth Data instance of a Buyer to its corresponding instance in NetSuite
- Salesforce – Links Auth Data instance of a Buyer to its corresponding instance in Salesforce
- Social Media Platforms - Links to each of the social media platforms known of the Buyer will also be added as individual external records.
- Clean links must be used for external records such as "https://www.instagram.com/buyer" instead of "https://www.instagram.com/buyer?hl=en"
- The DMO team will only capture official links (i.e. exclude fan websites or social media).
When a new Buyer is created, the DMO application will validate external records against existing Buyers to detect overlap with an existing Buyers. A more robust duplicate check will soon be introduced which will also compare additional properties, such as names, to other parties.
The DMO will click on links to ensure they resolve, as accounts on external platforms may be incorrect from migration or data entry.
Business Relationships
Buyers may have specific relationships with a Venue or Event Series that may need to be tracked by UTA.
For example, Spybar Management LLC is the legal business name for the party that operates a venue in Chicago called Spybar. This is tracked within Auth Data by linking the LLC to the venue using the Venues (Operating) relationship.
Buyers that book talent for specific venues can also be tracked using the Venues (Buying) relationship. Spybar Management LLC books their own talent, so they would be listed as a buyer to this venue.
Similar operating and buying relationships can be added to an Event Series (buyer always buys for this event), Event Instance (buyer brought in to buy just for a specific instance of the event) or Stage Instance (buyer buys talent just for a specific stage at the event).
In all business relationship cases, the DMO will only create business relationship links when prompted by frontline teams to track that information. The DMO will not proactively search and link that information without having been prompted.
In addition, these business relationships are linked to verified Buyers parties not to contacts within the Buyer organizations.
Appointments
Employees and persons acting on behalf Buyer organizations are referred to as Buyer Contacts. Buyer Contacts differ from Buyers that are individuals. Individual Buyers operate as their own Buyer entity; they are the party taking on the legal obligation to follow the terms of any contract with UTA. Buyer Contacts are representatives for a Buyer and are ultimately not legally responsible for the contract. For example, if a Buyer Contact no longer works for a Buyer organization, it is the Buyer organization that must ultimately pay UTA and our clients for their services.
Auth Data uses the concept of an appointment to associate an industry contact with a Buyer for which they work and to articulate the function in which they operate. For example, a music Buyer employs Jane Doe in the role in charge of marketing for booked events. Jane (a party of type Contact) is the Buyer contact while their position as the contact in charge of marketing is called the Job Role.
Job role options are predefined within Auth Data. With Touring, for example, those roles include Promoter Contact, Promoter Contact, Contract Signatory, Marketing Contact, Ticketing Contact, Production Contact, and Box Office Contact. Each Buyer subtype will have its own set of defined job roles.
If prompted, the DMO can attach individuals to specific job roles (such as “Marketing Contact”) to a buyer organization. Touring has predefined roles, so the DMO will not create an appointment for an individual that does not fit into these roles.