> ## Documentation Index
> Fetch the complete documentation index at: https://support.detrics.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Multi-Account Queries

> Query several accounts of the same platform in a single query

A single query targets one platform, but it can cover **several accounts** of that platform at once: all your Meta ad accounts, every Shopify store, or a selection of Google Ads accounts under your connection.

## How Results Are Combined

Detrics runs the query against each account and stacks the resulting rows into one table. The rows are **concatenated, never summed across accounts**: if you query total spend with no dimensions across 3 accounts, you get 3 rows (one per account), not one combined row.

To tell the rows apart, add the **Account Name** or **Account ID** dimension. Without it, rows from different accounts look identical and a multi-account daily report becomes ambiguous: three accounts produce three rows for the same date.

## Currencies and Timezones

Each account reports in its own currency and timezone, and Detrics returns the values exactly as the platform reports them, with no currency conversion. Summing spend across a USD account and an ARS account produces a meaningless number; keep mixed-currency accounts in separate rows or convert in your destination.

## Errors on Individual Accounts

If access to one of the accounts was lost (a removed permission or a deactivated account, for example), Detrics still returns the data from the remaining accounts, together with a warning identifying the affected account. Any other error stops the whole query, so you never receive silently incomplete totals. See [Troubleshooting Connections](/connect/troubleshooting-connections) for fixing access issues.

## Next Steps

<CardGroup cols={2}>
  <Card title="Dimensions & Metrics" icon="table" href="/core-functionality/dimensions-and-metrics">
    The building blocks of every query
  </Card>

  <Card title="Data Freshness" icon="clock" href="/core-functionality/data-freshness">
    Why recent numbers shift, and when data becomes final
  </Card>
</CardGroup>
