ZenotiHelp

S3 folder structure and file format

ZTZenoti Docs Team Updated April 10, 2026 2 min readGuide

Navigate and understand the hierarchical folder structure and CSV file format used in your Amazon S3 bucket for Analytics β€” Amazon S3 data delivery.

Before you begin

  • Your organization must have Analytics β€” Amazon S3 enabled and configured.
  • You need access credentials to your organization's S3 bucket.
  • At least one full data load must be completed before folders and files appear in your bucket.

Steps

  1. Connect to your S3 bucket using your provided access credentials.
  2. Navigate to your organization's root directory folder.
  3. Look for one or more PODName folders within the root directory.

Note: If your business operates across multiple geographies, you may see multiple PODName folders. Each PODName represents a different geographic region or data pod.

Understand the folder hierarchy

The S3 bucket follows this hierarchical structure:

Root Directory/
  PODName/
    GroupID/
      table_name/
        logid/
          filename.csv

Each level serves a specific purpose:

  • Root Directory β€” Your organization's topmost folder.
  • PODName β€” Geographic region or data pod identifier.
  • GroupID β€” Sequential number indicating the data load cycle.
  • table_name β€” Individual table folder (e.g., Bi_FactInvoiceItem).
  • logid β€” Sequential processing identifier for the data load.
  • filename.csv β€” The actual CSV data file.
  1. Within your PODName folder, look for numbered GroupID folders.
  2. Start with GroupID 1 for your initial full data load.
  3. Access higher-numbered GroupIDs (2, 3, 4, etc.) for incremental data updates.
  4. Avoid any folders named with a _processing suffix β€” these indicate data loads in progress.

Important: Only query completed GroupID folders. Folders with _processing suffixes are temporary and are renamed when the data load completes.

Access table data within GroupID folders

  1. Navigate into a GroupID folder to see all available table folders.
  2. Open the specific table folder you need (e.g., Bi_DimUser for guest data).
  3. Navigate into the logid subfolder within the table folder.
  4. Download the CSV files from the logid folder.

Note: In typical operation, there is one logid folder per table per GroupID. Multiple logid folders may exist after manual re-runs or data corrections.

Work with CSV files

  1. Download CSV files. File names follow the format <logidnumber-fivedigitserialnumber>.csv.
  2. For large data volumes, look for multiple files named Data0.csv, Data1.csv, Data2.csv, etc.
  3. Process files knowing they are UTF-8 encoded and comma-delimited.
  4. Reference the SchemaFull folder in your bucket root for column definitions β€” CSV files do not contain headers.

Important: CSV files do not include column headers. The column order is defined by the schema files in the SchemaFull folder at your bucket root.

Tips

  • Start with the smallest GroupID β€” GroupID 1 contains your complete historical data set. Higher GroupIDs contain only changes since the previous load.
  • Check multiple PODName folders β€” If your business spans multiple regions, ensure you access data from all relevant PODName folders.
  • Monitor for new GroupIDs β€” New GroupID folders appear every 1–2 hours as incremental data refreshes complete.
  • Use schema files for reference β€” The SchemaFull folder contains .txt files defining the structure and column order for each table.
Was this article helpful?
Your feedback helps us improve our documentation.