StartAbout Sigma

About billable usage events

View as Markdown

With Sigma’s usage-based pricing model, your organization incurs costs through credit usage when specific types of events (or user activity) occur, including data inputs, integration actions, and report exports. Administrators can monitor credit usage from these events in the Consumption usage dashboard.

This document explains categories of billable usage events, how specific event types use credits, and which account type permissions are required to trigger these events.

For information about credit pricing and billing, contact your Account Executive.

Billable usage event categories

Your organization can incur costs through credit usage when the following types of events occur.

InputCollaborative data entry (or input table data updates in the published version of a workbook)
Integration actionActions that call API endpoints or stored procedures
Report exportExports generated from reports

Summary of billable usage events

An individual usage event can consume a single credit, multiple credits, or no credits. The following table explains which types of events do and don’t use credits, and how Sigma tracks credit usage for qualified events.

Event categoryWhat does use creditsWhat doesn’t use creditsHow Sigma tracks credit usage
Input
  • Direct input table data updates in a workbook draft
  • Input table data updates via actions executed in a workbook draft
  • New input table creation2
  • Input table duplication or copy/paste2
  • CSV uploads to input tables2

1 input credit per row (up to 100 credits per action)

Each row created, updated, or deleted in an input table is tracked as an individual event that uses a credit. However, if a single user interaction (e.g., an update row(s) action) creates, updates, or deletes more than 100 rows, the event uses a maximum of 100 credits.

Integration action
  • Direct Sigma REST API calls that aren’t triggered by actions
  • Non-Sigma API calls (customer or third-party endpoints) outside of Sigma that aren’t triggered by actions
  • Stored procedure calls that aren’t triggered by actions (e.g., stored procedures called in table formulas)

1 integration credit per call

Each API endpoint or stored procedure call triggered by an action is tracked as an individual event that uses a credit.

Report export
  • Exports generated from workbooks
  • Reports downloaded directly from the Sigma UI

1 export credit per unique file

Each unique file generated is tracked as an individual event that uses a credit.

If a report is exported as an email burst, each unique file generated for an individual email is tracked as a separate event that incurs cost. Alternatively, if an export generates a single file such that multiple email recipients receive an identical report, the export is tracked as one event.

Usage event permissions

The following table lists the account type permissions required for a user to trigger specific types of billable usage events.

Event typeRequired account type permissions
InputEdit input tables: Enables a user who’s viewing the published version of a workbook to perform direct input table data entry and trigger actions that modify input table data. Notes:
  • The Edit input tables permission enables a user to enter data in an existing input table when the data entry permission is set to allow edits in the published version.
  • The Edit input tables permission does not enable a user to create new input tables. For information about account type permissions and workbook access required to create input tables, see Create new input tables.
Integration action
  • Call stored procedure actions: Enables a user to trigger an action that calls a stored procedure.
  • Trigger API actions: Enables a user to trigger an action that calls an external API endpoint.
Report export
  • Create, edit, and publish reports: Enables a user to access export features, including the ability to create export schedules, send scheduled exports on demand (“Send now”), and export via direct download.
  • Export to email: Enables a user to export reports to email recipients.
  • Export as email burst: Enables a user to export reports as email bursts.
  • Export to Google Sheets: Enables a user to export reports to Google Sheets spreadsheets.
  • Export to Google Drive: Enables a user to export reports to Google Drive folders.
  • Export to Slack: Enables a user to export reports to Slack channels.
  • Export to Microsoft Teams and SharePoint: Enables a user to export reports to Microsoft Teams channels and SharePoint folders.
  • Export to cloud: Enables a user to export reports to Google Cloud Storage (GCS) or Amazon S3.
  • Export to webhook: Enables a user to export reports to webhook endpoints.

Example usage event scenarios and billable outcomes

The following table summarizes common usage event scenarios and the total number of credits used.

Example scenarioCredit usage tracked
A user opens the published version of a workbook and updates input table data across 10 columns in a single row.1 credit (for the updated row)
A user opens the published version of a workbook and updates input table data in a single column across 10 rows.10 credits (1 for each updated row)
You configure a form to trigger a condition action sequence that updates rows in an input table only when they meet the specified criteria. A user submits the form in the published version of a workbook, resulting in value updates across 20 rows.20 credits (1 for each updated row)
While editing a workbook draft, a user uploads CSV data to an input table. The CSV file contains 1 million rows.No credits (Input table data entry performed in a workbook draft doesn’t use credits. Therefore, the number of rows uploaded from the CSV file and added to the input table is irrelevant.)
While viewing the published version of a workbook, a user submits a form. The interaction triggers an action sequence that adds a new row of data to an input table and calls a stored procedure.2 credits (1 for the added row + 1 for the called stored procedure)
You configure an automated action sequence that updates 1 row in an input table at the end of each week.1 credit per week (for the updated row)1
You schedule a report export that sends an email burst to 125 recipients on the first day of every month. Each recipient receives an individualized report.125 credits per month (1 for each unique file generated)
You initiate an on-demand report export that emails a report to 50 recipients. Each recipient receives the same file.1 credit (for the single file generated)
A scheduled workbook export sends a daily Slack notification with 4 unique attachments.No credits (Workbook exports don’t use credits.)

Footnotes

  1. Automated action sequences can only modify input tables with the data entry permission set to allow edits in the published version of a workbook. If an existing target input table is updated to only allow edits in the workbook draft, the automated action sequence cannot run successfully, and no credits are consumed. If the input table is updated to once again allow edits in the published version, the automated action sequence runs successfully and credit consumption resumes. For more information, see Run action sequences automatically. ↩ ↩2

  2. Functionality is supported in a workbook draft only. ↩ ↩2 ↩3