Data requirements

Zilliant aggregates and analyzes multiple data streams to generate visualizations and insights.

When you upload a data file to Zilliant, the system validates the file against the expected schema. The application then guides you to map your data and resolve some common errors before import. For best results, however, you should start with well-formatted data files.

Use the following tools and resources to help ensure you can successfully upload data to Zilliant.

Guides and tools

Zilliant offers in-application assistance and reminders to help you successfully upload data:

Required / Optional column reference—During the file upload process, Zilliant cues you with a list of required and optional columns for each required and optional file.
Excel template—Download a pre-formatted Excel template that includes the correct column names and order for each required and optional file. Use this file to organize and upload your data.

Resources

Best practices—Offers general guidelines to help you correctly format data.
Data input specifications—Lists required and optional files and their data input specifications.

Best practices

Zilliant validates files for common file errors. To ensure a valid data upload, check your files against the following best formatting practices.

Files

Should	Should not	Notes
Files must be in CSV or Excel format. Files should tie out corresponding data sets with other files. CSV files should comply with RFC 4180. File names should include only lowercase letters, numbers, and underscores (no spaces).	Files should not contain duplicate data File names should not contain spaces	Learn about RFC 4180 There can be many causes of duplicative or near-duplicative data, including combining data from multiple sources. To avoid this, make sure to implement data quality processes, such as standardizing data collection and entry procedures. For consistent file names, use a `<dataname>` naming convention, where <dataname> is the file’s data category. (Examples: `products.csv` or `accounts.xlxs`)

Data columns

Should	Should not	Notes
Each column must have a header row. Each column header label must exactly match the column name. Data in each column must meet data input requirements		Refer to Data input specifications for column header labels.

Data rows

Should	Should not	Notes
Files must contain at least one data row. Data in each column must meet data input requirements. Dates must be in ISO 8601 date format Fields containing special characters must be enclosed with quotation marks. CSV files: Row data must be listed in the same order as column headers Fields must be separated by commas Lines must end with CRLF	Do not use ASCII characters in numerical data.	Refer to Data input specifications for data input requirements. If a file isn’t encoded with UTF-8, consider using byte order marks in the file to signal the endianness of the file’s encoding. For more details about UTF-8, read HTML Unicode (UTF-8) Reference. For more details about byte order marks, read Using Byte Order Marks (BOMs).