Parques Reunidos connects tickets and annual passes through a shared customer identity

Parques Reunidos linked ecommerce, annual passes and campaigns through a shared identity, according to the case study DruID published on July 24, 2026. The supplier reports more than 452,000 integrated accounts.

The project connects transactions with different customers, durations and purchasing arrangements. A ticket, an annual pass and a group booking represent different relationships with the same leisure business. If each system recognises the buyer differently, the company loses continuity when it tries to understand what that customer purchased, which channel brought them in or which communications they can receive.

DruID describes an architecture linking identification, customer data and commercial activity. It attributes more than 42 integrations and more than 250 automated journeys to the deployment. These are infrastructure figures: they show the breadth of the connections, but the case does not publish a sales increase attributable to that infrastructure or a comparison with customers who remained outside it.

The operator's own reporting helps explain the problem behind those connections. In its 2024 sustainability report , Parques Reunidos counted 8,228 responses from online purchasers at 19 parks. It also explained that it collects feedback after visits and measures the purchasing experience separately from the experience inside the park. Connecting those moments requires distinguishing buyers from the visitors they represent.

The report places the group's origin in Spain in 1967, under the name Parque de Atracciones Casa de Campo de Madrid. It also identifies EQT's control since 2019. Spanish origin and current ownership are different facts. The figures for that year provide historical business context; they do not describe the performance of the identity project presented by the supplier in 2026.

July 24 is the case study's original publication date. Its later modification in September does not establish another launch date. Nor does it date each integration or automation. The documented development is the public account of the deployment, with an identified client and specific commercial components.

Recognising buyers across tickets, passes and bookings

The starting point, according to DruID, was an organisation with information spread across platforms, differences between parks and sales and marketing processes without a common operating model. In the first phase described by the supplier, the group operated more than 60 parks. That reference belongs to the project's scope, rather than a confirmed count of the parks the group retains today.

The case lists ecommerce, annual passes, group sales and hotel management among the connected businesses. This combination matters because an account can participate in transactions with different durations and beneficiaries. A ticket purchase covers a particular visit; a pass introduces a relationship based on repeated use; a group transaction can represent several people through a single contact.

A persistent identity can preserve a link between those transactions when participating systems recognise it. Its commercial value depends on the information that actually moves through the connections. Knowing that two transactions belong to one account can help organise the relationship. Knowing who actually visited the park, or which part of a booking was used, requires additional data that the case summary does not detail.

An integrated account therefore does not equal a unique visitor. A purchaser can manage several tickets, while the same person can interact with the group through different channels. The project can resolve some fragmentation between records without automatically turning every attendee into an individually identified profile. That distinction affects both audience size and any subsequent calculation of repeat visits.

In the pass business, recognising an existing relationship also changes the starting point for interpreting another transaction. A standalone purchase and a purchase by someone with an active pass tell different commercial stories. This is an analytical consequence of the model described, rather than a claim that Parques Reunidos has published a particular algorithm for selecting promotions or discounts.

Group sales add another separation: the person organising a booking may be the commercial contact, while the attendees take part in the experience. Treating that entire transaction as one person would obscure some behaviour; allocating it to all visitors without valid identification would invent precision. The identity layer needs to preserve what each record actually represents.

Identity as a component independent of the CRM

DruID presents the project as a combination of CRM, CDP and CIAM. A customer relationship management system organises relationships and commercial activity; a customer data platform brings together information that can help understand and segment those relationships; customer identity and access management determines how users are recognised and authenticated. The functions complement each other, although the labels alone do not describe a complete implementation.

The lesson the case attributes to Sergio Vallejo, Parques Reunidos' global chief information officer, is that identification and the customer view can be considered separately from the choice of CRM. The practical interest of that separation is to examine user recognition as a shared dependency for several tools, rather than rebuilding it in each application.

DruID says the platform was designed for eleven distinct functional scenarios, connecting businesses such as ecommerce, annual passes, group sales and hotel management. That count describes uses of the architecture, rather than eleven independent financial results. The source lists integrated channels and business lines, but does not explain every scenario or attribute sales to each one. The scope helps explain why shared identification must recognise different kinds of commercial relationship.

This distinction avoids assigning technologies to the operator that the source does not identify. The account mentions comparing large platforms, open solutions and leisure-specific tools when defining the architecture. It does not publish the complete supplier selection for the CRM, hotel applications or campaign engine. A definitive list of those brands would create an appearance of precision that the documentation cannot support.

Independence between identity and CRM also has a consequence for technological change. If a company changes a commercial tool, preserving the relationship between accounts and channels can help prevent the new application from treating existing customers as strangers. That possibility explains the design; it is not a quantified saving from this project. The case supplies no migration costs, maintenance hours or financial comparison between architectures.

At Parques Reunidos, the relevance of the shared layer follows from the variety of relationships already documented. The purpose extends beyond adding another ecommerce record. The stated objective is for tickets, passes, forms and commercial contacts to have a reference through which they can be related, without confusing access to an application with a person's complete history.

What the 452,000 accounts and 250 journeys measure

The supplier reports more than 452,000 accounts, 23 applications, 22 organisational units and 65 access points. Each unit counts something different. Applications represent connected environments; organisational units describe an internal distribution; access points represent digital entrances to the system. None of those three counts should be substituted for the number of parks or the number of people.

The case's headline figures round accounts to more than 450,000, while its results section uses more than 452,000. The more precise figure remains a minimum declared by the supplier. The source does not specify the inventory's cut-off date, how many accounts were active in a month or how many completed a purchase during the period considered.

The project summary also mentions more than eight million customers. It provides no definition that would align that population with the account population. Dividing accounts by customers would produce an apparent identification rate without a comparable basis. The observation periods, included markets or meaning of customer could differ; the text does not resolve those differences.

The more than 42 integrations should not be interpreted as 42 different applications either. The supplier refers to systems and suppliers, while the application inventory provides another count. A technical connection and a business tool are not equivalent units. The figure indicates coordination complexity, but it offers neither a complete interface map nor a measure of the connections' stability.

More than 250 automated journeys describe orchestrated processes, rather than 250 campaigns with proven sales. The case does not enumerate every journey or provide its entry volumes, outcomes or financial contribution. Assessing performance would require knowing which event starts each process and which result is recorded. A recovery flow and an access-management flow can both be useful without pursuing the same commercial outcome.

Deployment was progressive, according to DruID's account. That detail is consistent with a project bringing together different applications and units, but it does not establish a rollout timetable. The figures describe the platform's reported scope. They cannot establish quarterly growth, show that every connection was activated simultaneously or compare performance before and after one common launch date.

Online purchasers and visitors leave different signals

Parques Reunidos' 2024 report documents a listening system that covers several stages of the relationship. Surveys after a website purchase ask about the buying process. Surveys inside the park collect opinions about particular aspects of the visit. Post-visit surveys are used to calculate the Net Promoter Score, or NPS, which the group uses as an experience indicator.

The 8,228 online purchasing questionnaires came from 19 parks. Alongside that figure, the report does not provide the total number of invited purchasers or eligible transactions. The responses therefore cannot establish a participation rate. Nor do they show how many purchasers abandoned the process before payment: a survey appearing after a completed transaction observes people who have successfully passed through the process.

For on-site feedback, the company described electronic devices and QR codes at the 23 parks with the most visitors. Questions covered shows, shops, food service, toilets and accommodation. Those 23 parks are not the 23 applications in the DruID case. A numerical coincidence does not make two different inventories the same set of operations.

The post-visit survey was sent the following day to customers with an email address on record and consent for its use. The report adds that the average online purchaser typically buys two tickets per transaction and that respondents answer on behalf of the purchasing group. This matters: a purchase record and a survey response can represent a shared experience without individually identifying every visitor.

The listening system operated at considerable scale: Parques Reunidos recorded 287,754 post-visit survey responses during 2024. That volume describes a different stage and population from the 8,228 purchasing-process responses. The company does not provide the total number of invitations sent alongside the count, so a response rate cannot be calculated here either. These are opinions from a sample eligible to receive the questionnaire, with an email address and consent, rather than a census of every attendee.

The group NPS reached 18 points in 2024, according to the same report. The indicator subtracts the proportion of detractors, who score their likelihood of recommending the park between zero and six, from the proportion of promoters, who answer nine or ten. For the group aggregate, the company weighted the result by visitor type, annual-pass holder or single-visit customer, and by park size measured in visitors. Those 18 points describe that recommendation indicator; they are neither a commercial growth percentage nor a result attributable to the identity platform.

The report says post-purchase measurement enables satisfaction to be analysed from the purchase through to the visit. That statement explains the usefulness of connecting stages, but does not detail which responses are individually matched, how buyers who do not answer afterwards are treated or what share of the two samples overlaps. A common customer view can help formulate those questions. The available documentation does not show that DruID's architecture resolved those comparison problems or increased NPS.

Connecting these signals can help separate a payment difficulty from dissatisfaction with the visit. It can also show whether people who rate purchasing positively ultimately rate the experience positively. An association between answers does not establish that automation caused another sale, however. That conclusion would require observing subsequent transactions and comparing groups or periods under equivalent commercial conditions.