Skip to main content
Act-On Software

Data Studio overview

AUDIENCE: Administrators, Marketing Users

REQUIREMENTS: Enterprise Account

Data Studio is an advanced data transport tool that allows you to configure and move any data from Act-On to another tool.

AOmegaphonesmall.pngPlease note:
Additional fees apply for access to Data Studio. Please contact your CSM to learn more.

Pick your choice of data from preconfigured data sets and aggregations or dive right into the raw data facts. You can then decide on filters, scheduling of the exports, and the destination in order to accommodate any data needs.

Using Data Studio you are able to easily export marketing data using predefined export templates, allowing access to valuable data sets from your:

  • Media
  • Forms
  • Landing Pages
  • Email Messages
  • Webinars
  • Website Traffic
  • BYOBI (Bring Your Own Business Intelligence) - export CSV data (either as a pull or a push) to integrate with any BI tool (including Excel) to analyze further.
  • Extensible - initially 6 data sets - in the future, new data set and fields for existing data sets can be quickly added
  • Deprecate use of API for pulling data from Act-On
  • User friendly interface to export data
  • Automate / schedule recurring data generation
  • Stitch fact and dimension data easily
  • Data can be extracted for any custom period
  • Support for data push or data pull

An export is a list of predefined export (or tabular unformatted report) definitions. An export definition can be created from scratch or by starting off with a best practice template. An export definition contains a name, description, a source dataset, inclusive filters and specific actions, specification of data granularity (detailed or grouped), fields to be projected, sort criteria, filters, a schedule and a destination where the export output is to be delivered.

A package is a convenient mechanism to combine two or more exports. When requested to be generated (on demand or via a schedule), a package would spawn off child exports and the output of each export CSV would be combined into a ZIP archive delivered to the package definition’s destination. A package definition contains a name, description, references to two or more exports, a schedule (which dictates when its child exports get spawned off) and a destination where the package output is to be delivered.

A destination is a user defined list of locations where exported data can be pushed. At this time, the only destinations supported are SFTP, Azure File Storage, and Amazon S3 Destinations.

An SFTP destination only needs to be defined if an export or package data needs to be pushed to your location OR to your BI tool’s account. However, if the intent is to manually download export data once generated, a default ‘Downloadable File’ pull destination is provided out of the box as a target destination (without the need to explicitly configure any destinations). Note that only raw CSV data is transmitted to ‘push’ destinations defined in the Destinations section. Charts and heatmap visuals aren’t included in this push.

When an export (or package) is submitted for processing (for an on demand export, via the Generate link and for a scheduled export, automatically per the schedule definition), a runtime instance of that export (or package) appears in the run logs. The Run Logs view lets you track all instances of packages and exports that are running or have completed with details about the run. In addition, it lets you download or view output data corresponding to previously run instances of Exports (or Packages).

  • Was this article helpful?