Dimensions is a powerful concept in NEON, which has the following main purposes:

  1. To decorate transactional data with attributes which can later be used for querying, reporting and data analysis
  2. To enable querying and filtering based on those attributes
  3. To control platform behaviour. Scripts can make conditions based on dimensions, and Triggers can be defined to only fire for certain dimension values.
  4. To select, localise and personalise content served back from NEON. The CMS functionality in NEON can override and replace content based on the client’s dimensions.
  5. To assign Entities to specific circumstances, such as markets, promotions etc so that only the relevant Entities are applicable to each situation, and that accidental execution is prevented.

One or more Dimensions are passed in with every API call to the Loyalty API. And each passed in Dimension is given a value. For example the following call submits a survey entry, and uses dimensions to say that it came from a UK based website:

POST .../surveys/mySurvey/members/myMember?dim=country:UK;channel=web

NEON allows you to define any number of Dimensions and Dimension Values. What Dimensions you define depends on the type, size and needs of your business.

Typical examples of Dimensions you may want to consider are:

  • Country
  • Market
  • Brand
  • Language
  • Business Unit
  • Campaign / Promotion
  • Channel
  • A/B Test
  • Partner



Which Dimensions to set up requires careful planning, and Dimensions can't easily be removed once created. And changing the meaning of Dimensions in the middle may skew data insight. The SPIKA team will plan this with you during your onboarding to make sure you get it right.

Dimensions are or can be saved for most Loyalty related data. This includes Activities, Members, Orders, Surveys, Competitions, Games, Wallet transactions to mention a few.