How do Clarisights Data Exporters work?

You would often need data to be exported from Clarisights for various reasons like top-management reporting, or build cost reporting for use by finance teams. We allow you to do just that through 2 functionalities on our platform: widget exports and data exports.

In data exports, all the data from a channel is exported in a partially de-normalized format and delivered to data warehouses maintained by customers. These exports are configured daily to the destination buckets specified by the customer. We recommend you to use data exports when the volume of data to be exported on your end is large, for other cases, we recommend using widget exports.

NOTE: Currently, we only offer Amazon S3 and Google Cloud Storage as destination data storage systems.

Recent Changes (February 2026)

• No more empty files: Conversion export files are no longer generated when there is no conversion data for a channel. This reduces noise in your destination buckets.

• Improved reliability: Data exports are now orchestrated through a new scheduling engine for more consistent delivery timing.

Granting Permissions

You will need to grant the required permissions to the Clarisights team for exporting data (the same set of permissions are required for our widget exporters as well).

For Google Cloud Storage:

Grant the following permissions to the service account "101712083634-compute@developer.gserviceaccount.com":

• storage.objects.create

• storage.objects.delete

• storage.objects.get

• storage.objects.list

For AWS S3:

Grant the following permissions to the role "arn:aws:iam::747179778889:role/ClarisightsExternalAccessRole":

• GetObject

• PutObject

• PutObjectAcl

• DeleteObject

• ListBucket

Please share the bucket name, the region of the bucket, and path with the Clarisights team after granting these permissions.

After completing the above steps, you can contact your Clarisights representative to set up these data exports for you.

The following part of the article explains the specifications of the data sent through these exports.

Channels

All native API-connection channels, POD channels, and Custom Advertising channels can be exported via this feature.

File Naming Structure

The file structure for the outgoing exports is as follows:

<company_name>/<data_channel>/<version>/core_<level>/<upload_date>_from_<start_date>_to_<end_date>.csv
<company_name>/<data_channel>/<version>/stats_<level>/<upload_date>_from_<start_date>_to_<end_date>.csv
<company_name>/<data_channel>/<version>/conversions_<level>/<upload_date>_from_<start_date>_to_<end_date>.csv
<company_name>/<data_channel>/<version>/breakdowns_<breakdown_type>/core_<level>/<upload_date>_from_<start_date>_to_<end_date>.csv
<company_name>/<data_channel>/<version>/breakdowns_<breakdown_type>/stats_<level>/<upload_date>_from_<start_date>_to_<end_date>.csv

These are the different types of files mentioned above:

• core_: these files contain the dimensions data for the channel

• stats_: these files contain the metrics data for the channel (except conversion metrics)

• conversions_: these files contain the conversion metrics data for the channel (Optional). Note: As of February 2026, empty conversion files are no longer generated.

• breakdowns_: these files are present in case any breakdown dimensions are being exported for the channel (Optional)

Description of the filename structure:

• company_name: the name of your company

• data_channel: the name of the channel for the data (like Facebook, Google Ads, or the name of the POD or Custom Advertising channel)

• version: the version of data export

• level: the level of the data. All dimensions in Clarisights are stored at "levels" (Account, Campaign, Ad Group/Ad Set, Ad)

• upload_date: the date of upload for the data

• start_date: the start date of upload for the data

• end_date: the end date of upload for the data

• breakdown_type: the specific breakdown dimension being exported

Upload Structure

Each CSV file will be split into smaller chunks (each chunk contains a maximum of 100k rows) and each split will be compressed into gzip archives.

File Format

• Each CSV file is RFC 4180 compatible format

• Each CSV file will have an identifying header

• There is a special field created_at that identifies the date of CSV export

• Each CSV file is comma-separated

• Every field is double-quoted

And that's it! We hope this information gives you an overview of how our data exports work. Please reach out to your Clarisights POC in case of any issues or questions. :)