SlicingDice Documentation

SlicingDice - The All-in-One Solution Documentation

Welcome to the SlicingDice documentation. You'll find comprehensive guides and documentation to help you start working with SlicingDice as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Guides


First time checking our docs? You might want to start with the right foot by reading our Documentation Guide first.

SlicingDice columns are exactly like regular columns in a database or on a spreadsheet. Every column on SlicingDice is always associated to a dimension.

SlicingDice supports two main types of columns, attribute and event columns. The following is a summary of the differences between them:

Attribute Column

This column type is used to store any data not associated to a date/time. An attribute describes the facts, details or characteristics of an entity. You can use them to store: the name, age, and gender of users; the region or type of your server or IOT device, and more.

Check some examples of how to create columns and how to insert data into attribute columns.

Event Column

This column type is used to store event data that is associated to a date/time. For instance, you can track a click on a button in your Click event column by storing the value Add to Cart and the date/time of the event {% convert_date 'YYYY-MM-DDT10:35:23Z' '-1d' %}.

Check some examples of how to create columns and how to insert data into event columns. Further, you can also check an in-depth review of the differences between attribute and event columns.

One of the main advantages of the SlicingDice's columns is that you can add or remove new columns at any time, without any performance penalty, so you don't need to think or plan in advance how to model your database schema, as this can be executed and easily changed on the fly.

Column usage in practice

Below is an example of a SlicingDice database with three columns, which two of them are attribute columns (Name and Age) and one is an event column (Clicks), in which all the data stored is associated to one entity (UUID-01).





Add to Cart - {% convert_date 'YYYY-MM-DDT12:54:12Z' '-10d' %}
Pay Now - {% convert_date 'YYYY-MM-DDT10:22:10Z' '-5d' %}
Support - {% convert_date 'YYYY-MM-DDT17:05:25Z' '-2d' %}

As you can notice above, the columns Name and Age are storing information that doesn't need to be associated to a date/time, because it's a fact, not an event/transaction. On the other hand, the column Clicks is precisely storing clicks on buttons, so the data must have an association to a date/time, in order to know when the event happened.

Check the pages below to learn more about columns and how to create, edit or delete them:

How to create columns

How to list, edit or delete columns

Differences on Attribute and Event Columns

Supported data types