Note: In this article, we have used the Facebook Multi Account Connector as an example to explain the powering-up process for a multi-account connector. The same principles apply to any multi-account connector.

​

Multi-Account Connector Vs Single Account Connector

Every Multi-Account Connector has a corresponding single Account Connector. For example, the Facebook Ads Advanced Multi Accounts Connector has a corresponding Facebook Ads Advanced single Account Connector. You might prefer to use the Multi Accounts version of a Connector if the following are true:

1. You have multiple Connector Accounts to a particular system in Domo, OR you have a single Connector Account to a particular system in Domo and plan to add more Accounts later.

AND

2. You would like to import the data from one or more of these Accounts into Domo into a single dataset, rather than keeping the data from each Account separate.

You may prefer to use the single Account version of a Connector if you have one or more Connector Accounts associated with a system in Domo, and you would like to keep the data from each Account in a separate DataSet.

​

Powering Up A Multi-Account Connector

Powering up refers to the complete process of successfully configuring a dataset. The difference between powering up a Multi Account Connector and powering up a single Account Connector is that multi-Account Connectors let you select one or more Accounts to pull data into one dataset. Follow these steps to configure a Multi Account Connector:

1. Select one or more Accounts to run the Connector.
2. Choose a report, and set any configuration options.
3. Name the dataset and select the update frequency.

​

Selecting the Accounts to use

From the Credentials section, you can select one or more Accounts to run a Connector When you click Select Account, a drop-down list appears. It shows the list of all the authenticated Connector Accounts of the single Account Connector type you can access. Select the checkbox next to each Account for which you want to run the Connector. To create a new Account, click Add Account, enter the required credentials, and connect to the system. After the Account is successfully authenticated, it appears in the drop-down list. Note: You might need to create a new Account after you have initially configured your dataset. Note that the Accounts created after a dataset is configured and saved must be explicitly added to the list of Accounts to run. New Accounts are not automatically selected by default. To add a new Account to the dataset, go to the Credentials section. Click the box with the list of selected Accounts, and then add the new Account to the list.

​

Selecting the report to be run

In the Details section, select the report you want the Connector to run. If the report requires more configuration options (for example, a date range), set the appropriate values. These configuration options applies to all Accounts selected for this dataset.

​

Naming dataset and selecting update frequency

In the Scheduling section, select how often the Connector should run. When the Connector runs on the specified schedule, it will pull data for all selected Accounts at the same time. You can also set the dataset’s update method (for example, Replace, Append, or Merge), if the Connector supports it. The Connector will apply this method to the data for all selected Accounts during a scheduled run. Note: Multi Account Connectors can re-run a Connector for one or more specific Accounts. When a user manually reruns a Connector for specific Accounts, the data for those Accounts is replaced for that run only. For more information, see Viewing Dataset History. In the Name and Describe Your Dataset section, provide a name for the dataset.

​

Reading the DataSet

Multi Accounts Connectors pull data for each selected Account and add the data to the dataset you named in the configuration. Each row in the dataset is associated with only one Account. When you run a Multi Account Connector, it parses the response from the source system and adds the corresponding columns to the dataset, just as a single Account Connector would. Additionally, it adds three columns to each row to help you identify the Connector Account that generated that row. The three columns are:

Column Name	Purpose
Account_ID	A numerical identifier of the Connector Account associated with this row of data.
Account_NAME	The system name of the Connector Account associated with this row of data.
_Account_DISPLAY_NAME	A user-specified name for the Connector Account associated with this row of data.

​

Dataset Update History

You can view a dataset’s update history by navigating to the History tab of the dataset. This tab shows the number of rows updated during each Connector run, just like the update history for a single-Account Connector. For multi-Account Connectors, the History tab also shows the number of Accounts that ran successfully next to the number of rows updated. For example, in the screenshot below, the Connector was configured to run with two Accounts, and it successfully ran both of them. You can get more details about a Connector run for a specific Account by viewing the Run Details dialog box. To open this dialog box, click the text that shows how many Accounts ran successfully. The Run Details dialog box shows the breakdown of the number of rows the Connector pulled for each selected Account, as well as the status of the data pull for each Account during that update. For example, in the screenshot below, the Connector tried to pull data from two Accounts during the May 22nd run at 5:36 p.m. Both Accounts succeeded and pulled one row of data. In the example below, the Connector tried to pull data from two Accounts but succeeded with only one.

Fields in Run Details Dialog Box	Description
Account	Shows all the Account names selected to create the dataset. Each row shows the status of a specific Account.
Start Time	The time when the DataSet update started.
Duration	The time it took for the Connector to run for that Account.
Updated Rows	The number of rows the Connector pulled into the dataset for that Account.
Result	Shows the results of the dataset run for each Account. A green checkmark and a success message indicate a successful run. If an Account fails to run, an error message appears.
Retry	Shows the number of Accounts selected to rerun. For example, in the image below, the user selected only one Account to rerun.

​

Reruning a Specific Account

You can use Multi-Account Connectors to rerun the entire dataset or specific Accounts. You might want to rerun the entire dataset if:

1. Historical data accumulated for each Account can be pulled from the source system.

OR

2. You want to replace the entire dataset with new data for each Account.

You might want to rerun specific Accounts if:

1. It takes a long time to update the entire dataset.

OR

2. You need to preserve the historical data that has already accumulated for each Account.

Note: You can rerun a specific Account even if its last run for that Account was successful. To rerun a specific Account follow the steps below:

1. Go to the History tab on the DataSet details page.
   
2. Go to the entry for the Connector’s last run, and then click the link that shows how many Accounts were updated successfully. For example, in the image below, you would click the 1/2 Accounts Successful link in the entry for May 22, 2025.
   
   The Run Details dialog box appears, showing details for each Account.
3. Select the checkbox next to the specific Account(s) that you want to rerun, and then click the Retry Account link. The Run Details dialog box closes, and you are redirected to the dataset’s History tab. From there, you can monitor the run’s progress.
   

​

Dataset Partitioning

Multi-Account Connectors add columns to each row in the dataset to identify which Account the row is associated with. The Connector also adds a value to the BATCH_ID and BATCH_LAST_RUN fields to indicate when that row was last updated.

​

FAQs

Can I set different settings for individual Accounts? This isn’t currently possible. The Connector must run the report with the same configuration options for every selected Account. How are credits consumed in a Multi-Account Connector? The Connector consumes one credit per Account per run of the Connector. These Connectors are more cost-effective than configuring multiple single Account Connectors because they reach the credit consumption cap faster than the single Account Connectors, and therefore use less credits. What does the “Fail the DataSet if an Account fails” option do? When the Connector runs for more than one Account, it’s possible for some Accounts to return an error. For example, if you have selected three Accounts (X, Y and Z), and Account Y is no longer successfully authenticated, the Connector can still retrieve data for Accounts X and Z. It will simply get an error from the source system for Account Y. By default, the Connector ignores errors generated by Account Y, and continues to process data for Accounts X and Z. At the end of the entire Connector run, the Connector will report the update as successful, even if the data for Account Y fails. If you prefer the Connector to stop as soon as it receives an error for an Account, select the Fail the Dataset if an Account Fails checkbox. This option will stop the Connector update immediately if an error occurs and mark the entire dataset update as unsuccessful. This option allows you to specify whether it’s okay to ignore an error from the source system for an Account and continue requesting data for other selected Accounts. In the previous example, this would mean the Connector would retrieve data for Account X.