What Experiences Are in Nevent

What we mean when we say experience

In Nevent, an experience is the central unit of work for the promoter. It’s the event they organize: a concert, a multi-day festival, a play, a fair, or any celebration that has a date, a venue, and tickets.

The term experience isn’t just an alternative name for event. Nevent uses it to remind you that what the promoter sells doesn’t end with the ticket. They sell the whole thing the attendee is going to live: access to the venue, the artists they’re going to hear, the accommodation they might book, the transport they might arrange, the T-shirt they might take home. That complete view is what the Experiences, Sales, and Add-ons block covers from the admin panel.

How the block is organized

Inside the Nevent menu there’s a block of three sections that work together:

Experiences is the list of every event the promoter has created in the tenant. From there you can see each event’s status, tickets sold against total capacity, location, and date. It’s also the entry point for accessing each event’s detail.

Sales is the full history of purchases made in the tenant. Every time an attendee buys tickets or add-ons, that transaction is logged here with the date, the buyer, the operation reference, and the amount. The section is read-only: you can view and filter, but not edit sales.

Add-ons is the catalog of extra products the promoter can offer alongside the ticket. They aren’t tickets, they’re products that expand the experience: merchandise, accommodation, transport, food, drinks, and activities.

The three sections are related. An experience generates sales. Sales can include add-ons. The add-ons catalog is available for every event in the tenant.

What an experience is in the list

When the promoter opens the Experiences section, they see a table with all their events. Each row contains the sales channel, the event name, the location, the start date, tickets sold against total capacity, the event’s status, and the promoting organization’s name.

The tickets column is especially useful at a glance: it shows the number sold and the available capacity. For example, an event with 727 of 5,086 tickets sold indicates that a little over fourteen percent of capacity has been covered and there’s still runway ahead. That same information, seen on an event with 0 of 4,284, signals that sales haven’t started yet or that something needs checking.

The promoter can filter the list by date (current, past, or all events) and search by event name. The actions available per row are viewing the event’s attendees, copying the event link, and cloning the experience to reuse as the basis for a new event.

What sales are and why they’re here

The Sales section isn’t an analytics report. It’s the transactional record: a chronological list of every purchase made in the tenant.

Each sales row has a unique reference (a transaction identifier), the exact date and time of the purchase, the buyer’s name and email, the amount in euros, and the sale’s status. The only status visible in the demo tenant is Completed, indicating a transaction closed successfully.

The promoter can filter sales by event, by date range, by minimum or maximum amount, and search by buyer name or code. This lets them locate a specific transaction or review sales for a given period without needing to export anything.

The Sales section exists inside the Experiences block because sales are the direct consequence of having active events. It wouldn’t make sense to separate the purchase history from the catalog of events that generate it.

What add-ons are

An add-on is any product the promoter can sell to an attendee in addition to the ticket. The ticket grants access to the event. The add-on expands that experience with something more.

Nevent organizes add-ons into six categories: merch, food, drinks, transport, accommodation, and activities. A promoter might offer, for example, a hotel room alongside the festival ticket, a private ride to the venue, an artist T-shirt, or access to an exclusive activity during the event.

Each add-on has a name, a price, a counter of units sold, and a status. The status can be Available (the product is active and for sale) or Out of stock (no units left). The price can be zero, which allows for including free or informational add-ons in the catalog.

The promoter manages the add-ons catalog from the Add-ons section, with the same creation and sync controls available in the Experiences section.

Why the block is called Experiences and not Events

The choice of name isn’t accidental. An event is something that happens. An experience is something that’s lived. Nevent bets on that second framing because the promoter’s goal isn’t to sell a ticket, but for the attendee to have a good memory from start to finish.

That philosophy has practical consequences in the platform: Nevent’s analytics, segmentation, and communication tools are designed to work with the event’s audience before, during, and after the date it takes place. The experience doesn’t end when the attendee walks through the door.

Relationship with the rest of the platform

Experiences are the starting point for almost everything that happens in Nevent. An event’s attendees feed the audience base from which the promoter can segment and launch campaigns. Add-ons sold appear in the sales history alongside tickets. Each event’s analytics are consulted from the experience’s detail view.

When the promoter opens an event from the Experiences list, they access every section specific to that event: Analytics, Description, Celebration, Tickets, Supplements, Sponsors, Attendees, Add-ons, Campaigns, Reassignment, and Music profile. Each of those sections adds a layer to the experience the attendee is going to have.