Terms you will meet in the data and in this documentation, in plain language.

Term	What it means
Article	What is sold or issued: a day ticket, a pass, an exhibitor badge, a parking ticket. Carries price, validity and rules. Prefix `Article*`.
Assortment	A grouping of articles offered together in a shop context.
Buyer	The person or account that paid for a sale. Not necessarily the person who attends. Prefix `Buyer*`.
Cross-selling	An additional article sold alongside the main one. The data records both the source article and the uplift. Prefix `CrossSelling*`.
Distribution chain	The channel a sale came through — internet, on site, exhibitor service centre, internal. Column `SaleDistributionChainType`.
Entrance	The physical door or gate where a ticket was scanned.
Fair brand	The recurring event series that individual editions belong to. What you compare year over year. Prefix `FairBrand*`.
Fair event (Fairevent)	One edition of an event — a name plus a year, with dates. Prefix `Fairevent*`.
FKM	The voluntary audit scheme for trade-fair and exhibition statistics used by German organisers. The `IsFkm*` flags on statistics groups mark what feeds those audited figures.
Legitimation	The proof someone presented to qualify for a restricted article — press card, student ID, trade-visitor credential. Prefix `Legitimation*`.
Mandator	The tenant — the organisation whose data this is. Constant for your feed; you cannot query outside it.
mTicket	The mobile ticket form, as opposed to a printed or wallet ticket.
Promotion code	A discount or access code applied to a sale. Prefix `PromotionCode*`.
Quicode	An ADITUS barcode format used on tickets and badges.
Regcode	A one-to-one registration code, used to redeem an invitation into a personalised ticket.
Sale	One purchase transaction. Can produce many tickets. Prefix `Sale*`.
Statistics group	A reporting bucket that articles belong to, carrying the FKM flags. An article can be in several at once, which is why they live in their own dataset.
Ticket	One admission entitlement belonging to one person. The centre of the data model. Prefix `Ticket*`.
Ticket owner	The person who attends and whose name is on the badge. Prefix `TicketOwner*`.
Terminal	The device that performed a scan — a turnstile, a handheld reader, a gate.
Token	The UPPER_SNAKE_CASE values the status columns carry, for example `PAID` or `ASSIGNED`. See Datasets → Column values.
Upselling	An upgrade from one article to a higher-value one. The data records the source article and the uplift. Prefix `Upselling*`.
Usage	One scan of a ticket at an entrance. Entry or exit. Zero to many per ticket.
UTM parameters	Campaign tracking parameters carried on a sale (`SaleUtmSource`, `SaleUtmMedium`, `SaleUtmCampaign`, `SaleUtmTerm`, `SaleUtmContent`). What makes marketing attribution possible.

Naming conventions in the data

Once you see the pattern, most of the 342 ticket columns explain themselves:

Suffix	Means
`*InternalId`	the numeric primary key of that thing in the operational system. Stable, use it for joins.
`*UniqueId`	a GUID. Stable across systems, use it when you need a globally unique reference.
`*Name`	the human-readable label. What belongs on a chart axis.
`No` / `Number`	a business number, such as a ticket number or an event number.
`Is*`	a boolean flag.
`At` / `On` / `*Timestamp`	a point in time.
`Status` / `Type` / `*State`	a token column — see Column values.

So FaireventInternalId, FaireventUniqueId and FaireventName are the same event seen three ways: join on the first, reference with the second, display the third.

Glossary

Naming conventions in the data