Configuring Destinations for Data Studio Exports

  • Updated

A destination is where Data Studio delivers a finished export. By default, exports are available as a downloadable file in Act-On. If you want the data to land in a team storage location without anyone having to log in and fetch it, you need to add that location as a destination first. Once added, destinations appear as options whenever you set up an export or package.

Who does this: Act-On administrator, usually with help from IT or the team that owns the storage location
Time needed: 5 to 20 minutes depending on the destination type
Why this matters: Downloadable files expire after a short retention period and live only inside Act-On. For any recurring export that a team needs to act on, a proper destination (SFTP or cloud storage) removes the manual step of logging in to fetch the file and keeps the data wherever the consuming team already works.
Quick Reference (Advanced Users) - Click to Expand
  • Configure at Reports > Data Studio > Destinations.
  • Supported: Downloadable File (default), SFTP, Amazon S3, Dropbox, Google Drive, Microsoft OneDrive (personal accounts only).
  • HTTPS is required for all connection types.
  • SFTP receivers must allow Act-On IP ranges: 207.189.124.0/24, 207.189.125.0/24, 54.200.92.142, 54.93.34.201, 54.194.14.170, 35.183.73.63.
  • Dropbox subfolders need a leading slash, e.g. /aotest.
  • Amazon S3 needs an IAM user with an IAM policy granting PutObject/GetObject/AbortMultipartUpload/GetBucketLocation/DeleteObject on the bucket and its contents.
Try it like this: To land exports in an SFTP folder your BI team already watches, ask IT to allowlist the six Act-On IP addresses above, then go to Reports > Data Studio > Destinations, add an SFTP connection with the server host, port, path, and credentials, and save. The SFTP destination now appears as an option in the Delivery step of any export.

Supported destination types

Data Studio can deliver to:

  • Downloadable File (default). The export is stored by Data Studio for a short time so you can download it manually.
  • SFTP. Connect a secure FTP location.
  • Cloud Storage: Amazon S3, Dropbox, Google Drive, Microsoft OneDrive (personal only).

Cloud storage logos supported by Data Studio

What you need before you start

  • Act-On administrator access.
  • Credentials or an account for the destination you want to use.
  • For SFTP: the receiving server's host, port, username, password or key, and the target folder path, plus cooperation from IT to allowlist Act-On's IP ranges.
  • For Amazon S3: an IAM user with the correct policy (see below), the Access Key and Secret Key for that user, and the bucket name.

Add a destination

  1. Go to Reports > Data Studio and click Destinations in the left menu.
  2. Click Add and choose the destination type.
  3. Fill in the connection details for that destination type (see the specifics below).
  4. Save the destination.
Note: HTTPS is required for every destination type.

SFTP requirements

If you're receiving Data Studio files by SFTP, your server must allow inbound connections from Act-On's IP ranges:

  • 207.189.124.0/24
  • 207.189.125.0/24
  • 54.200.92.142
  • 54.93.34.201
  • 54.194.14.170
  • 35.183.73.63

Ask your IT or networking team to add these to the allow list before you save the SFTP destination in Data Studio, otherwise connection tests and scheduled runs will fail.

Dropbox notes

When exporting to a Dropbox subfolder, prepend the subfolder name with a forward slash. Example: /aotest. Without the leading slash Data Studio may treat the value as a filename prefix instead of a folder path.

Microsoft OneDrive notes

Only personal OneDrive accounts are supported. Business accounts are not currently available as a destination. If your team uses OneDrive for Business, use SFTP or Amazon S3 instead.

Amazon S3 setup

To link an Amazon S3 bucket, you need:

  • Your bucket name.
  • An AWS Access Key and Secret Key belonging to an IAM user with permission to write to the bucket.

To get the keys, create an IAM user in your AWS account. AWS documentation:

Attach a policy to the IAM user that allows Data Studio to write, read, abort multipart uploads, get bucket location, and delete objects on the bucket. Example policy:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "s3export",
            "Action": [
                "s3:PutObject",
                "s3:GetObject",
                "s3:AbortMultipartUpload",
                "s3:GetBucketLocation",
                "s3:DeleteObject"
            ],
            "Effect": "Allow",
            "Resource": [
                "arn:aws:s3:::AWSBUCKETNAME/*",
                "arn:aws:s3:::AWSBUCKETNAME"
            ]
        }
    ]
}

Replace AWSBUCKETNAME with your bucket name.

Common pitfalls

  • Saving an SFTP destination before IT has allowlisted Act-On's IPs. The connection test will fail, and scheduled runs silently miss until the block is lifted.
  • Trying to connect a OneDrive for Business account. Only personal OneDrive is supported.
  • Omitting the leading slash on a Dropbox subfolder path.
  • Creating an S3 IAM user without s3:GetBucketLocation in the policy. Some Data Studio runs need this permission even though they're writing data.
  • Relying on the Downloadable File destination for exports your team needs regularly. Files are retained for a short window only, and then removed.
What you've unlocked: The new destination is now available in the Delivery step of any export or package. Go back to Creating Exports in Data Studio or edit an existing export and point its output at the new location.

Was this article helpful?

Have more questions? Submit a request