Skip to main content
Act-On Software

Data Studio FAQs

AUDIENCE: Administrators, Marketing Users
Requirements: Enterprise Account

  • Clicked is when a Media Link is followed. If you add a link as a media item, clicking it will increase the Clicked count by one.
  • Downloaded is any form of downloading your content. If you upload a file (eg., PDF), either clicking a link to download it or loading a web page where it is embedded will increase the Downloaded count by one.
  • If you select a set of lists for an Export using inclusion filters (i.e., if you select multiple messages that have been sent to different lists), all profile fields for those lists are made available for the Export definition.
  • If you do not specify inclusion filters in your dataset, only standard profile fields will be 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, you can choose:
    • Specific date ranges
    • Relative date ranges ('Last X days')
      or
    • All time
  • The date range selector appears when you are generating an Export (or Package) manually.

Notes:

  • 'All time' includes all data available on your account for this dataset. It includes any available data for today (the day when you run the export).
  • An absolute date range must specify both start and end dates. If today (the day when you run the report) is included in the date range, the report will include any available data.
  • Relative periods of data do not include the current day. The most recent time available is the previous day (1 day ago in your account’s time zone. The maximum time available is 365 days.

For Daily or Weekly Exports (or Packages), the Export (or Package) schedule determines the schedule:

  • If specific days of the week are selected, the export/Package runs on those days between 3am and 5am in the account’s time zone and retrieves data for the previous X days (based on the range you selected).
  • You can set additional date limits of 'After Date X,' 'Before Date Y,' or 'Between Dates X and Y' (this last option includes both days X and Y).

Examples:

  • If a daily Export is scheduled with a time period of 'Last 1 Day,' it will run every day between 3am and 5am in your account’s time zone. The Export will contain data for the previous day.
  • If a weekly Export (time period of 'Last 7 Days') is scheduled to run every Monday, it will run between 3am and 5am in your account’s time zone. The Export will contain data from the previous Monday starting at 12am midnight until the previous full day (Sunday) at 11:59:59pm.
  • If a Package is schedule to run Daily, its child Exports will use this date range for data. Any different time ranges made on the individual child Exports will not be used.

For Monthly Exports (or Packages), data is always retrieved for a full month. The Export (or Package) will always run on the 1st day of each month (between 1am and 3am in your account’s time zone).

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 time zone (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.

CSV, CSV ZIP, CSV GZ, or XLSX. We recommend using the Zip or GZ options for more exports, since they will process and download faster.

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.

Not inside Data Studio.

The generated output can be pushed to an SFTP or cloud destination or downloaded to your computer. Generated 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?
Support

Have a question about this topic?

Ask the community!