Contents

One Dashboard Across Several Ad Accounts: Structuring Data for Combined Reporting

A dashboard that combines several advertising accounts is only useful when everyone agrees on what its fields mean.

  • Sections8

Editorial team Spend Ledger

Start with a shared reporting contract

A dashboard that combines several advertising accounts is only useful when everyone agrees on what its fields mean. A row of totals can look precise while concealing differences in time zones, currencies, attribution settings, or campaign definitions. Before connecting data, write down the rules the report will follow and make them visible to the people who prepare, review, and use it.

The reporting contract should describe the accounts included, the purpose of the view, the reporting period logic, and the meaning of each metric. It should also explain how missing, delayed, or unavailable data will be shown. A blank value is not the same as zero, and an account that has not refreshed is not necessarily an account with no activity.

Keep this agreement practical rather than turning it into an exhaustive policy document. The goal is to make comparisons interpretable and to prevent a later change in reporting logic from silently changing the story. When a definition or rule changes, record what changed and when it took effect in the report documentation.

Make account and campaign names comparable

Naming conventions let readers identify what they are looking at without relying on private knowledge held by one team member. Use a consistent pattern for account labels and campaign names, with fields that distinguish business area, market or audience, objective, and campaign status where those distinctions matter to the analysis.

The convention should be clear enough to apply to accounts prepared internally and to accounts managed through an agency arrangement. Do not use a name to imply ownership or authority that the team does not have. Record the account’s actual role and the responsible business contact in a separate reference table, rather than packing every detail into a long label.

Avoid encoding information that is likely to change into a name that will be treated as permanent. For example, if a campaign’s objective changes, preserve the original record and document the change rather than renaming history in a way that makes earlier activity appear to have had a different purpose. Keep labels readable in charts and tables, and define abbreviations in the report notes.

A useful shared register can include the account’s display name, business purpose, market, access status, reporting owner, and whether it is active, paused, or retired. Keep access limited to people who need it, and ensure that account management follows the platform’s own permissions and verification requirements. Reporting convenience does not change who is authorised to access an account.

Define metrics once, then apply them consistently

A combined report should have a metric dictionary. For each field, specify what is being measured, its source, its unit, and any conditions that affect interpretation. If a metric has a platform-defined meaning, use the platform’s current definition and note the relevant setting. Do not assume similarly named fields are equivalent across accounts or reporting views.

Separate platform-reported results from calculations made in the dashboard. For example, a cost-per-action measure may be calculated by dividing spend by a selected action count, but the action definition must be explicit. If accounts optimize for different actions, a single blended cost can hide that distinction. Show the action type or group results only where the underlying events are genuinely comparable.

Treat attribution settings, conversion windows, and event configuration as part of the metric context, not as footnotes that can be ignored. If settings differ, either bring them into alignment where appropriate and permitted, or present results in separate groups with the difference clearly stated. Never imply that a total is directly comparable when its components use incompatible definitions.

Keep the dictionary close to the dashboard, and assign someone to maintain it. When a platform changes how it labels or calculates a field, review the impact before updating the report. Current definitions and account requirements should be checked against the platform’s official help and policy pages; where values or settings can change, use those sources rather than relying on a remembered threshold.

Normalize currency and time before comparing totals

Currency treatment can make a combined spend figure misleading. Decide whether the dashboard will show each account in its reporting currency, convert values into a shared reporting currency, or provide both views. If conversion is used, document the source and timing of the exchange rate and retain the original amount and currency for auditability. A converted value is an analytical presentation, not a replacement for the amount recorded by the platform or payment system.

Do not combine currencies by simply adding the displayed amounts. If conversion cannot be applied consistently, show account-level values separately or group them by currency. Make clear whether fees, taxes, credits, or other adjustments are included, and avoid treating a billing amount as interchangeable with advertising spend unless the underlying data supports that interpretation.

Time zones need the same care. An account’s reporting day may follow its configured time zone, while the dashboard or business reporting period may use another. Choose a common reporting basis and document how account-level timestamps are mapped to it. Where a precise alignment is not possible, label the affected view and avoid presenting daily comparisons as if all accounts close at the same moment.

A rolling period and a calendar period can answer different questions. Define which one the dashboard uses and apply it across accounts. Data may also arrive at different times or be revised after an initial report. Display a refresh status or reporting cutoff, and distinguish provisional data from data that has been checked. Do not fill delayed data with estimates without clearly identifying them as assumptions.

Give every data feed an accountable owner

Each connection between an ad account and the combined report needs a named role responsible for its health. That owner may be an internal operator or an agreed agency contact, but the responsibility should not be vague or dependent on whoever happens to notice a problem. The owner should know what data is expected, how often it is checked, and who to notify if access or delivery changes.

Document the feed’s source, the account it represents, the fields it supplies, and the person or team responsible for resolving issues. Record how access is granted and reviewed under the platform’s permitted access model. A dashboard should not rely on personal credentials being shared informally, nor should a reporting process encourage circumventing platform permissions or verification.

For agency-managed accounts, agree in writing on reporting access, data fields, refresh expectations, retention, and what happens when the service arrangement changes. Clarify who can see account-level information and who is responsible for explaining discrepancies. An account is a work asset within an authorised business relationship, not a shortcut around platform rules. If account access is disputed or restricted, use the platform’s official support and appeal channels rather than trying to conceal a change in control.

Set a routine for checking feed status and investigating gaps. When data stops arriving, mark the affected account as incomplete rather than quietly dropping it from the total. A removed account should also have a documented reason and effective reporting date so readers can understand why the composition of the dashboard changed.

Keep one governed place for the combined view

Choose one agreed home for the combined report and make it clear which version is authoritative. Copies in personal files, chat attachments, and separate team workspaces can diverge quickly. Provide access according to role, and keep the source data and transformation notes available to the people responsible for maintaining the report.

Organize the dashboard so readers can move from an overall view to the account-level detail that explains it. The combined total should be accompanied by a clear account list, currency and time-zone notes, metric definitions, and refresh status. Filters should be labelled in plain language, and the initial view should not depend on a particular person remembering hidden selections.

Keep raw or source-level records separate from the presentation layer. That makes it easier to trace a displayed value back to its account and reporting period, and to identify whether a discrepancy arose in the platform data, a conversion, or a dashboard calculation. Preserve enough context to review changes without exposing information to people who do not need it.

The dashboard should also state its limits. It may not include every billing adjustment, offline outcome, or internal cost, and a platform-reported conversion is not automatically a complete measure of business value. Where the report is used for decisions about spend or return, show the relevant assumptions and distinguish reported results from internal estimates.

Check the combined total before relying on it

A total is trustworthy only when its components are present, comparable, and correctly transformed. Before using it in a review, check that the expected accounts appear, that none has been duplicated, and that each account is mapped to the intended business unit. Confirm that the reporting period and refresh status are consistent with the dashboard’s stated rules.

Then trace selected values from the combined view back to their account-level source. Check that spend is not being counted twice, that the chosen action definition is consistent, and that currency conversion and time-zone handling match the documentation. Look for abrupt changes caused by a new setting, missing feed, renamed campaign, or account moving between active and retired status.

A useful review asks more than whether the arithmetic adds up. Ask whether the total answers the question readers think it answers. A pooled cost per action can be mathematically correct while masking major differences in objectives or markets. In that case, keep the pooled figure only as a broad summary and show the relevant segments beside it.

When a value cannot be reconciled, flag it and explain what remains uncertain. Do not repair a discrepancy by changing account settings or access arrangements outside permitted processes. If the issue involves a platform restriction, review, or verification, follow the platform’s official support or appeal route and address the underlying cause.

Add or retire accounts without losing context

When an account is added, do not let it enter the headline total before its role, permissions, currency, time zone, metric settings, naming, and feed owner are documented. Check that it follows the reporting contract and that its data can be compared with existing accounts. If it cannot, place it in a clearly labelled separate group until the difference is understood.

When an account is paused or retired, retain its historical reporting according to the organization’s data practices and applicable platform requirements. Mark its status and the point at which it stopped contributing to current totals. Removing it from the current view should not erase the fact that earlier periods included it.

Make changes visible in the dashboard notes or a maintained change log. Explain whether a shift in the combined result reflects performance or a change in the set of included accounts. This is especially important when accounts are transferred between internal teams or agency arrangements, because responsibility and access can change while historical data remains relevant.

Review the structure periodically, but keep the process proportionate. The objective is not to make every account identical; it is to show what can be compared, what cannot, and why. A well-maintained combined view gives the team a common basis for discussion while preserving the account-level detail needed to interpret results responsibly.