Skip to main content
Act-On Software

Data Studio FAQs

AUDIENCE: Administrators, Marketing Users
Requirements: Enterprise Account

If a set of lists are explicitly selected via inclusion filters (e.g. if you select messages that have been sent to specific lists), the unique set of referenced profile fields for those lists are made available for the export definition.

If no inclusion filters are specified in a dataset, only standard profile fields are made available.

However, an administrator can override the system and allow you to inject a custom profile field if needed.

For On Demand (or manual) exports, absolute date ranges, relative date ranges or all time can be selected as periods for the export data set. The date range selector pops up when an export (or package) is requested to be generated manually.

All time includes all data for the account for a specific dataset including partial data for today (i.e. the day on which the export is invoked).

An absolute date range must specify a start and end date wherein either date can’t exceed today. If today is included in the date range for which export data is being requested, partial data will be retrieved (up until the time at which the export was processed).

Relative periods of data do not include today. The term ‘Last’ suggests that data is retrieved until yesterday (for the account’s time zone). The allowed range is 1 to 365 days (both inclusive).

For Daily (or Weekly) exports (or packages), the period for which data is inferred by the export (or package) schedule. If specific days of the week are selected, the export (or package) runs on those days between 3am and 5am in the account’s timezone but retrieves data for the previous X days (via the Last X Days selector). This type of schedule can be contained within optional date bounds i.e. after Date X, before Date Y or between Dates X and Y (always inclusive of both X and Y).

As an example, if a daily export is scheduled with a time period of Last 1 Day, the export would run every day between 3am and 5am in the account’s timezone and the payload would contain data for the previous day. Similarly, if a weekly export (with a time period of Last 7 Days) is scheduled to run every Monday, this will run between 3am and 5am in the account’s timezone for a payload from the previous Monday starting at 12am midnight until the previous full day i.e. Sunday at 11:59:59pm. Daily (or Weekly) exports are always scheduled to run between 3am and 5am in the account’s timezone. This time cannot be changed.

If a package is schedule to run Daily or Weekly, it spawns off child exports and applies the date range for data retrieval to those child exports. The child exports referenced by a package could have their own schedule definition. However, the schedule of the package dictates the schedule (and date range) of the child export instance runs.

For Monthly exports (or packages), the period for which data is retrieved is always a full month. The instance when the export (or package) runs is exactly on the 1st day of the following month (between 1am and 3am in the account’s timezone). As with the daily/weekly schedule, if a date boundary is specified, the monthly scheduled exports (or packages) always run within those bounds. Note however that the date boundary for monthly schedules specify a month and year pair. As an example, if a monthly export is requested for July 2015 until November 2015, the first instance of this export (or package) will run on August 1st, 2015 between 1am and 3am in the account’s timezone (wherein data for the entire month of July 2015 will be generated). Similarly, the next run will execute on September 1st, 2015 between 1am and 3am and generate data for the month of August 2015. This will continue every month on the 1st day of every month between 1am and 3am until December 1st, 2015 where the last run will generate data for the period of November 2015.

If you have inclusive filters defined for your export that restrict the dataset to specific assets, you could pull data for all time.

However, if you want all data for a specific dataset (not limited to specifically selected elements), you must choose a limited time period.

For all datasets (except website visitor traffic), the unique context is recid (recipient id).

For website visitor traffic, the unique context is cookieid (because of the large number of anonymous visits; besides, known visitors can also be identified by cookie id) Unfortunately, Data Studio does not reconcile cookie id, email addresses and recipient ids to identify a true unique.

If this is required, we recommend downloading the detailed log and using an external ETL process or BI tool to compute true uniques.

Only CSV at this time.

Data Studio’s initial focus is to easily generate raw data.

For an on demand export or package, you request for a run by clicking the GENERATE link in the export (or package) list view. In the Run Logs view, you’ll see your queued / running / complete job with your name (or the name of the requester) on it.

For a scheduled job, the initiator of the run is the system Export Scheduler.

This specifies how you would like the output for the processed export or package be delivered. The output could either be preserved by Data Studio for a period of 7 days for a manual pull download OR it could be pushed to SFTP destinations defined in the Destinations section.


The CSV generated output (either as pure CSV or compressed as ZIP or GZIP) can be pushed to an SFTP destination or pulled from Act-On as a Downloadable File. CSV files can be quite large.

Yes - optionally - via email. The content of this email is very basic and there is no follow through link to get you to your completed export. You will need to navigate to the run log to find a specific export run.

Not at this time. The goal of Data Studio is to get you your data in raw form that you can then plug in to your favorite BI tool and generate polished visuals. Therefore, we haven’t focused on high fidelity output formats.

No you cannot but an Act-On Customer Success Manager could create one on your behalf. In a future version, creation of custom fields or aggregates will be supported natively as a self service option.

The schedule of the package overrides the schedule of the export and drives the export. The export (by itself) will run on its own defined schedule (or not at all if it is defined to be on demand).

The package will drive another instance of the export based on its schedule. It is quite possible that the export may run twice on the same day (once for its own schedule and once when invoked by a package).

No - all child exports contained in a package will be generated as CSV files (even if the export definition specifies its destination file as a ZIP or GZIP).

A run time error would occur while combining the two output files into the package archive. You will still be charged for the token cost of each of the successfully generated exports.

10 data studio exports is the standard limit. To increase this, contact your account manager.

Inserted is the field and it is a marketing action for forms and represents the count.

  • Was this article helpful?

Have a question about this topic?

Ask the community!