Intro
Enterprise Stacker is a highly configurable alternative data structure that transforms large amounts of data quickly and easily. It allows you to combine data from multiple platforms in such a way that multiple inputs can be defined as one single metric without the use of SQL or custom programming. Stacker also provides change records to administrators through the Domo activity log, ensuring security and optimizing governance possibilities. You can access the activity log from the navigation header by selecting More > Admin. Under Governance, select Activity log. Using Enterprise Stacker, you can combine the following two tables that come from two different channels into one impressions table.
Views as the metric we are stacking, here is our output impressions table:

When to use Enterprise Stacker
Enterprise Stacker works well in the following situations:Use Case | Benefits of Stacker |
|---|---|
Data exists in multiple platforms or DataSets |
|
One Master DataSet is required or preferred |
|
Data size is more than 50-100M rows |
|
- Output is dynamic based on configured dimensions and metrics
- Wildcard inputs — thousands of DataSets combined quickly
- Thousands of input data sources
- Hundreds of possible metrics/dimensions
This article describes Enterprise Stacker setup and how to complete various tasks within it in the following topics:
- Getting Enterprise Stacker
- Prerequisite s
- Creating a job
- Adding multiple metrics to a job
- Activity logs
Getting Enterprise Stacker
Contact your Account Executive (AE) or Technical Consultant (TC) to begin the deployment process. Domo will access your instance to deploy Enterprise Stacker and align it with the provided system user account’s email.Prerequisites
There are a few things to prepare and consider before using Enterprise Stacker:- Ensure the cleanliness of the data before stacking. Check the numerical and data values to ensure the columns include only numerical values.
- Ensure you’re applying the data type consistently (string, double, date, and so on).
- If you are using a wildcard metric, ensure that at least 99% of the DataSets that match the wildcard rule have the columns you wish to query in their schema.
Creating a Job
- In Enterprise Stacker, select + New Configuration.
-
Choose which DataSet to use for the metric:
Select a DataSet — Allows you to search by name and select one DataSet
Select all DataSets that match a rule — Allows you to select all DataSets where the name contains whatever string you specify.

- Name your metric and you can, optionally, set a metric alias. This is an alternative name you could use to search for this metric in your output DataSet.
- Select Next.
- Choose the value column that corresponds to the metric.
Note: If you must, you can choose a string. The Enterprise Stacker engine attempts to cast the string as a numeric value. However, if there are true string values in your column and it cannot be cast as a number, then you receive an error after you run the job.
-
(Optional) Create an aggregation on the value column. Select Next.
Note: When you choose to aggregate a value, Stacker will automatically group by all other non-aggregated columns that are included in the table.
-
Choose a date column. This should be the date that lines up with the numeric metric you chose. You can select I don’t have a date column if you don’t want to specify one. Select Next.
Note: You can select a string type column here if needed. Stacker will attempt to cast the string as a date type. However, if there are values that aren’t true dates in your column and cannot be cast as a date, then you will receive an error after you run the job.
-
(Optional) Apply any necessary filters by selecting + add a filter. Select the column, operand, and value you would like to filter on. Filters provide the option for rolling windows of data, reducing data size, targeting specific numbers, targeting specific date ranges, etc. You can add as many filters as you would like. Select Next.
Note: Filters are applied with an
andmethod. You cannot apply one filter or the other. -
(Optional) Add additional columns. You can create custom constant columns, select which columns are included, rename columns, and select data types
-
Custom constant column — Select
and type in the column name and choose a value you would like to be populated on every row for this DataSet.
- Select DataSet columns — Choose which columns to include in the output DataSet.
- Rename columns — You can rename any column you choose to include from the DataSet.
-
Select data type —
Choose the data type you want the column to be in the output.

-
Custom constant column — Select
- Select Next.
- Name the output DataSet. This is also the name of this Enterprise Stacker job.
Note: Since Stacker uses the job name as the name for the output DataSet, there must be one, and only one, DataSet at any time that has the same name as the Stacker job tied to it. Otherwise the job fails and the data does not update.
- Select an Update Schedule for the job.
- Select Finish.
Adding Multiple Metrics to a Job
- Select the job you want to add additional metrics to.
- Select + Add Metric and follow the steps to create a job.

Metric Actions
In the Configuration tab for the job, you can
Copy,
Edit, or
Delete a metric.

Note: After you delete a configuration, it cannot be recovered, and the DataSet is orphaned and stops updating.
Edit Job Configuration
To change the DataSet name or the job run schedule, select
Edit Configuration.
