A package groups two or more exports into a single delivery. You can send them as separate CSVs inside a ZIP, or combine them into one merged CSV joined on shared fields. Packages are how you turn several small exports into one consolidated file that a recipient or downstream tool can open in one step.
Who does this: Act-On user with Data Studio and existing exports to combine
Time needed: 5 to 10 minutes, assuming the underlying exports already exist
Why this matters: Recipients who consume your data (BI engineers, finance, sales ops) usually prefer one file over several. Packages remove the manual step of downloading and merging exports after each run. They also let you schedule the consolidated output once, rather than scheduling each export individually.
Quick Reference (Advanced Users) - Click to Expand
- Go to Reports > Data Studio > Packages > New Package.
- Combine types:
- Disjoint CSV Files in a ZIP Archive: one ZIP containing each export as a separate CSV.
- One Merged CSV File: exports joined into a single file on shared fields.
- Merged CSV only supports exports of the same grouping type (all detailed, all aggregated, or all summarized).
- Package schedule overrides each child export's schedule for the package run.
- Child exports inside a package are always produced as CSV, regardless of their individual format settings.
Try it like this: Create a monthly package that ZIPs together your Email Performance, Form Performance, and Landing Page Performance exports. Recipients get one ZIP on the first of each month, with each dataset in its own CSV inside.
What you need before you start
- The exports you want to combine already created. See Creating Exports in Data Studio.
- A decision on whether you need separate files in a ZIP or one merged CSV (see Pick a combine type below).
- A destination for delivery if you don't want a downloadable file. See Configuring Destinations for Data Studio Exports.
Note: Package output is unformatted data. Charts, pivots, and other visualisations are not produced by Data Studio; use a BI tool or Excel for those.
Pick a combine type
- Disjoint CSV Files in a ZIP Archive: each export becomes its own CSV inside a single ZIP. Best when the exports cover different data sets and you just want one delivery.
- One Merged CSV File: Data Studio joins the exports into a single table using fields you map. Best when the exports share a dimension (for example, message ID or contact email) and you want a consolidated view.
Important: Merged CSVs can only combine exports with the same grouping type. All exports in the merge must be detailed log data, all aggregated, or all summarized. If you need to join across grouping types, use Disjoint CSVs in a ZIP and combine them in a BI tool or in Excel.
Create the package
- Go to Reports > Data Studio and click the Packages tab.
- Click New Package.
- Enter a Name and, optionally, a Description.
- Select the exports you want to combine from the list of existing exports.
Choose how to combine
- Select either Disjoint CSV Files in a ZIP Archive or One Merged CSV File.
- If you selected One Merged CSV File, define the mapped columns for the merge:
- Quick: add shared columns individually or use All of the above to add every shared column.
- Custom: create a new column in the merged output and map each source export's field into it.
Set the schedule
Choose On Demand, Daily or Weekly, or Monthly. The package's schedule drives each child export when it runs as part of the package. Individual child exports also continue to run on their own schedules (if any) outside the package.
Set delivery
- Choose the Destination.
- Enter a File Name.
- Configure email notifications if you want alerts on completion.
- Click Finish.
Note: Child exports inside a package are always produced as CSV, even if the individual export was configured as ZIP or GZ. The package's own format controls the final container.
Common pitfalls
- Trying to merge exports with different grouping types (for example, a detailed log export with an aggregated rolled-up export). Data Studio can't join these. Use Disjoint CSVs in a ZIP instead.
- Expecting child exports to use their own schedules inside the package. They use the package's schedule for package runs. They still run separately on their own schedules outside the package.
- Two child exports writing to the same output file name. The package run will fail with an error during combining. Token cost for each successfully generated export is still charged.
- Forgetting that a scheduled package runs in addition to any scheduled child exports. That can mean the same export is generated twice in a day; adjust schedules if that's not what you want.
What you've unlocked: A single scheduled delivery that consolidates several data sets. Point the package at an SFTP or cloud destination so consuming teams don't have to log in to pick up files, and see the Data Studio FAQs for how the package schedule interacts with individual export schedules.