Export Scheduling & Timing Guide

Widget Exports are deprecated. Existing widget exports keep running for now, but don't set up new ones: use Export Pipelines instead. To move an existing widget export, see Migrating from Legacy Exports to Export Pipelines.

This guide explains when each type of Clarisights export runs, how timezones apply, and how to choose a schedule that delivers complete data.

Export Pipelines

Each schedule of an export pipeline runs on its own cron expression, for example 0 6 * * * for every day at 6:00 AM. The minimum interval between two runs is 1 hour.

• Timezone: The cron and the date range are both read in the schedule's timezone. If no timezone is set, your company timezone is used.

• Delivery: The export starts at the scheduled time. Files appear in your bucket once the run has finished, which takes longer for large extracts and long date ranges.

• Several runs: A pipeline can have several schedules, for example a daily export of yesterday and a weekly export of the last 30 days.

See Managing Export Schedules & Manifests for cron examples and date range presets.

Widget Exports (Legacy)

Each widget export runs at a chosen hour, in your company's timezone, and then repeats every few hours:

Setting	Default	Description
Export hour	0 (midnight)	The hour of the day (0 to 23) to run, in your company's timezone
Interval	24 hours	The number of hours between runs (1 to 24)

A file usually arrives within a couple of hours of the scheduled hour, depending on the size of the widget.

Data Exporters (Legacy)

Data Exporters run once a day at a fixed time set by Clarisights. They can include a second daily run that re-exports only the last 3 days, which is useful when your systems need fresher data without waiting for the next full export. Contact us if you need to know or change when your Data Exporters run.

Choosing the Right Time

• Let the data arrive first. Clarisights imports data from your channels several times a day, and channels keep updating recent days (for example late conversions). To export a complete previous day, schedule the export later in the morning rather than right after midnight.

• Re-export recent days. If your numbers for recent days change after the first export, use a date range that covers the last few days (such as last_3d for Export Pipelines) and let each export replace those days in your warehouse.

• Match timezones. Dates in the export follow the schedule's timezone (Export Pipelines) or your company's timezone (legacy exports). Use the same timezone in your warehouse to avoid off-by-one-day differences.

Common Questions

Can I change when my export runs?

Yes. For Export Pipelines, the schedule's cron expression and timezone can be updated at any time. For widget exports, the export hour and interval can be changed. For Data Exporters, contact us. Reach out through the messenger support on the platform with the new time you need.

My export didn't arrive today. What should I check?

1. Check the schedule's time and timezone, and allow time for the export to finish.

2. Check that you are looking at the right folder in your bucket (path prefix, pipeline name, version, and extract).

3. Check that the bucket permissions have not changed. See Configuring Export Pipeline Destinations & Permissions.

4. If the file is still missing, contact us with the pipeline or widget name and the expected time, and we will check the run for you.