Counter Data Exporter

How the Counter Data Exporter Works

Save your counts and event logs as a file. CSV works with most spreadsheets. JSON works well with code, and XLSX is an Excel file.

1. Choose the data: Pick totals only, full event logs or both.
2. Choose the format: Select CSV for spreadsheets, JSON for code or XLSX for Excel.
3. Set the time format: Pick local time or Coordinated Universal Time (UTC) in ISO 8601 format.
4. Download: Save the file to the device or share it.

Counter Data Exporter Formula

A rough file size is the row count times the bytes per row. The format and fields can change the real size.

Rows

Events or totals exported

Bytes per row

About 40 to 80 bytes for a CSV event row

Example: An event log of 12,000 taps at 60 bytes per row gives a CSV of about 720,000 bytes (703 KB, or 0.69 MB).

Counter Data Exporter Reference Table

This table compares file types, where to open them and how much space they may take.

About the Counter Data Exporter

An export saves count data so you can use it outside the counter and keep it after the tab closes.

CSV stores one event or total in each row. Most spreadsheet apps can read it. Use ISO 8601 times in UTC to keep dates clear when you share a file across time zones.

Ways to Use the Counter Data Exporter

Save a file to check counts, share results or keep a backup. Here are five common uses.

• ✓Spreadsheet analysis: Analysts build pivot tables from event logs.
• ✓Record keeping: Teams archive counts for audits.
• ✓Research data: Researchers load logs into R or Python.
• ✓Sharing results: Users email a CSV to a manager.
• ✓Backups: Users save counts before clearing the browser.