The CRM centralizes data related to an organization's clients (in this case, a visitor, spectator, or user). It is used to study the relationship - in other words, the journey - of individuals in connection with your cultural venue.
This is the key distinction from ticketing software: ticketing systems are not designed to aggregate external data¹, but rather to operate and record booking and payment transactions efficiently. That's why a CRM and a ticketing system should not be confused: a tool that does not aggregate data from different sources is not a CRM.
The client database within ticketing software, though sometimes detailed, does not illuminate user journeys in the way a CRM does. Beyond the descriptive or consumption data recorded by a ticketing system (which shows what shows someone booked, at what price, for which date, and when), the CRM also leverages data about how the transaction occurred (when and how people buy, how regularly, etc.). This allows the CRM to identify behavioral groups, and it can further incorporate broader information about what may have triggered the purchase - such as an email campaign, a text message, a call from a group, participation in an outreach activity, or concurrent exposure to signage or digital marketing.
This enables one to identify and characterize a spectator's level of loyalty and understand how consumption evolves within a venue. The CRM's ability to cross-reference this variety of data types is what defines it and gives it purpose: to map purchase or booking journeys and analyze behaviors for deeper insight. A CRM can reveal so-called conversion funnels - the path an online visitor took to make a reservation (e.g., did they come via a web search, a digital ad, a newsletter, etc.). A dedicated sheet explores these different conversion funnels (see link).