Data Studio Overview
Please note: Additional fees apply for the Data Studio add-on module. Please contact your Account Manager to learn more.
Data is unformatted and does not include charts or other visualizations by default. If you want pre-packaged reporting templates with visualizations, consider the Engagement Insights feature.
- Export CSV data to manipulate in Excel or any business intelligence tool
- User friendly interface to export raw data
- Automate/schedule recurring data pulls/pushes
- Stitch data easily
- Data can be extracted for any custom time period
Any data points tracked in Act-On are available for export and analysis, including from these data sets:
- Landing Pages
- Email Messages
- Website Traffic
See our guide to exporting a copy of your Act-On data for a detailed walkthrough.
An export is a list of predefined data sets that you want to take out of Act-On to analyze. You can create export definitions from scratch or using existing templates.
A package is combined set of two or more exports. You can generate these on demand or on an automated schedule to create a single folder with all relevant reports.
You can define the location where Data Studio reports should be stored. You can choose between a custom FTP destination or a number of cloud storage services.
The Run Logs section is where you can view exports that are running, completed, or failed. You can also view details such as token usage. You can download output data or view it in your browser from this area.
There is a daily limit of 100,000 tokens per day for Data Studio exports. Generally, exports that take more time and processing power use more tokens. If your export will exceed your token limit, it will still be allowed to run – but all other exports will fail for the rest of the day. The token limit resets daily at 12 AM in the time zone of your account.
You can request a one-off override to the daily limit from our support team. This override will last for one day, then go back to the normal limit the following day.
Formula for token calculation
((Source Rows * Source Columns) + (Results Rows * Results Columns)) / 1000
Token consumption depends on both the source data and the results. This means that it is a best practice to limit (filter out) data that you do not need in your export and not include it in your source data. This often allows you to significantly reduce your token consumption.
Access and Pricing
Contact your Account Manager for information about purchasing Data Studio.