Data Studio Overview

  • Updated

Data Studio is Act-On's raw-data export tool. It lets you pull the behavioural and profile data Act-On already collects, on your own schedule, and deliver it to a spreadsheet or to a storage location your team already uses. If you've ever wanted to mix Act-On data with data from another system, or build a custom dashboard, Data Studio is the way to get the data out cleanly.

Why this matters: Act-On's built-in reports answer the common questions well, but they don't cover every scenario. Data Studio fills the gap. It gives your analytics, RevOps, or BI team access to the underlying data so they can answer questions Act-On's standard reports cannot, without the team having to request exports from marketing every time.
Quick Reference (Advanced Users) - Click to Expand
  • Open Data Studio at Reports > Data Studio.
  • Available data sets: Email Messages, Forms, Landing Pages, List or Segment Profile Data, Media, SMS Messages, Webinars, Webpages.
  • Exports are single data pulls. Packages combine two or more exports into one delivery. Destinations control where the file lands.
  • Formats: CSV, CSV ZIP, CSV GZ, XLSX.
  • Token formula: ((Source Rows × Source Columns) + (Results Rows × Results Columns)) / 1000. Daily limit is 100,000 tokens per account, reset at midnight in your account's time zone.
  • Data Studio is a paid add-on. Contact your Account Manager for access.
Note: Data Studio is a paid add-on module. If you don't see Data Studio under the Reports menu, contact your Account Manager to add it to your account.

Data sets you can export

Any data point tracked in Act-On is available for export. Out of the box the following data sets are supported:

  • Email Messages
  • Forms
  • Landing Pages
  • List or Segment Profile Data
  • Media
  • SMS Messages
  • Webinars
  • Webpages

Each data set exposes its own set of trackable actions (sent, opened, clicked, submitted, downloaded, and so on). See Choosing Actions for Data Studio Exports for the full list per data set.

Common uses

  • Export CSVs to analyse in Excel or a BI tool.
  • Automate recurring data pulls on a daily, weekly, or monthly schedule.
  • Combine several exports into a single delivery using packages.
  • Pull data for any custom time range, not just the periods offered by built-in reports.

Exports

An export is a definition of one data pull: which data set, which actions, what fields, what filters, and when to deliver it. You build exports from scratch or from a template. Each account starts with a set number of available export slots (Enterprise and Data Studio add-on accounts typically start with five). For a walkthrough, see Creating Exports in Data Studio or, for the faster path, Export from a Template.

Packages

A package is two or more exports bundled into a single delivery. You can choose a ZIP of separate CSVs, or a single merged CSV where the exports are joined on shared fields. Packages are useful when a recipient needs one file rather than several, or when you want Act-On to produce a consolidated view on a schedule. For the how-to, see Merging Data and Exports in Data Studio.

Destinations

A destination is where a finished export is delivered. The default is a downloadable file you retrieve from Data Studio. You can also connect an SFTP location or a Cloud Storage provider (Amazon S3, Dropbox, Google Drive, Microsoft OneDrive personal). Connected destinations appear as options whenever you set up an export or package. See Configuring Destinations for Data Studio Exports for setup details and IP requirements.

Run Logs

The Run Logs area is where you track what Data Studio has been doing. It shows exports that are currently running, completed successfully, or failed, along with token usage for each. From here you can download a finished file or view it directly in your browser.

Tokens and daily limits

Data Studio uses a token system to manage processing load. Each account has a daily limit of 100,000 tokens, which resets at midnight in your account's time zone. Exports that take more time and processing power consume more tokens. If a single export exceeds your daily limit, it will still be allowed to run, but any other exports queued for the rest of the day will fail.

Token formula:
((Source Rows × Source Columns) + (Results Rows × Results Columns)) / 1000

Because both the source data and the output affect the total, the best way to keep consumption low is to filter out data you don't need at the source, rather than pulling everything and filtering later. Narrower data sets cost fewer tokens and run faster. If you need a one-off override on the daily limit, contact Support. The override lasts one day and the limit returns to normal the next.

Access and pricing

Data Studio is an add-on module. Contact your Account Manager for pricing and to enable it on your account. Once enabled, it appears under Reports > Data Studio.

Was this article helpful?

Have more questions? Submit a request