top of page
Typographic Black and Blue.png

How to Set Up Cross-Account Reporting in Meta Business Manager for D2C Agencies

You manage 12 D2C brands. Each has its own ad account, Pixel, Business Manager. Every Monday you spend 3 hours pulling spend, ROAS, and creative metrics from 12 different dashboards into one spreadsheet for the agency review.


Meta's cross-account reporting can collapse that 3 hours into 10 minutes — if you set it up correctly. Most Indian D2C agencies never use it because the setup buries critical steps in documentation. Here's the practical guide.


First: Confirm What 'Cross-Account Reporting' Actually Means


Meta has three different cross-account capabilities, often confused:


  • Business Manager portfolio view: high-level summary of all ad accounts you manage — limited metrics, basic.

  • Ads Reporting cross-account: build custom reports spanning multiple ad accounts in one view with full metric flexibility.

  • Marketing API integration: pull data from all accounts into a third-party BI tool (Looker, Tableau, custom dashboards) — most powerful, requires development.


This guide covers Ads Reporting cross-account, which is the right answer for 90% of agencies managing 5-30 brands. Marketing API is for agencies at 30+ accounts with engineering resources.


Prerequisites Before Setup


  • All ad accounts must be in the same Business Manager OR you must have agency partnership access via Business Manager partner-share.

  • Your user role must be Admin or Reports User on each account.

  • Each Pixel and conversion event setup should already be standardized across brands — non-standardized event names create reporting chaos.


If your agency manages brands via individual user invites instead of Business Manager partnership, cross-account reporting won't work. Migrate to partnership structure first.


The Setup Sequence


Step 1: Centralize Ad Accounts in One Business Manager


Business Settings → Accounts → Ad Accounts → Add → 'Request access to an ad account'. Send a partnership request to each client's Business Manager. Once accepted, the ad account appears in your agency's Business Manager.


Step 2: Open Ads Reporting


Ads Manager → Reports → Ads Reporting. Click Create Report. Select 'All ad accounts' or use the account-multi-select to pick the brands you want in the report.


Step 3: Configure the Report Structure


Choose dimensions and metrics:


  • Dimensions: Ad account name, Campaign objective, Date (weekly/monthly), Country (India breakdown if relevant)

  • Metrics: Spend, Purchases, Purchase value, ROAS, CPC, CPM, CTR, Frequency

  • Filters: Active campaigns only, last 30 days, INR currency


Step 4: Save and Schedule


Save the report as a template. Schedule it for automatic delivery — weekly Monday morning, or daily for high-volume agencies. Email goes to all stakeholders. Excel/CSV format works best for further analysis.


The Three Most Useful Cross-Account Reports for D2C Agencies


1. Portfolio ROAS by Brand


Dimensions: Ad account name, Week. Metrics: Spend, Purchase value, ROAS, CPA. Surfaces underperforming brands at a glance. Trigger: any brand falling below 2.5x ROAS for 2 consecutive weeks.


2. Campaign Objective Performance Across Brands


Dimensions: Campaign objective, Ad account name. Metrics: Spend share, ROAS, Frequency. Tells you which objectives work across the portfolio vs which are brand-specific anomalies.


3. Creative Format Performance Across Brands


Dimensions: Creative format (Video, Image, Carousel, Reels), Ad account name. Metrics: CTR, CPC, ROAS. Surfaces which formats are universally outperforming vs brand-specific.


Common Mistakes Agencies Make


  1. Including paused or test campaigns in the cross-account view, polluting the data with stale numbers.

  2. Mixing currencies: brands running USD spend alongside INR brands without flagging the currency dimension. Resulting ROAS numbers are mathematically wrong.

  3. Not standardizing conversion event names across brands. 'Purchase' in one account and 'OrderCompleted' in another won't aggregate.

  4. Failing to set date timezone: cross-account reports default to your Business Manager timezone. If clients are in different regions, day boundaries shift.

  5. Building reports too granular: pulling ad-level metrics across 12 brands produces 50,000+ rows. Stick to campaign or account level for portfolio views.


How Wittelsbach AI Replaces Cross-Account Reporting


Bach AI provides agency-grade portfolio views out of the box. Connect all your client Meta accounts via Business Manager partnership and you get unified ROAS, CPM, and creative performance across brands with automated weekly digests. Plus brand-by-brand revenue leak detection that Meta's cross-account reporting can't surface. Bach AI is live at [app.wittelsbach.ai](https://app.wittelsbach.ai). Two clicks to connect Meta.


Frequently Asked Questions


Can I see Pixel-level data across accounts?


Limited. Cross-account reports show ad-level conversions but not Pixel-level event firing diagnostics. For Pixel/CAPI health across multiple brands, you'll need to check Events Manager for each account individually, or use a third-party tool that aggregates Events Manager API data.


Does cross-account reporting cost extra?


No, it's included in standard Business Manager functionality. Some advanced Marketing API access (data freshness under 1 hour, custom dimension exports) requires Meta Business Partner status, which is free but requires application. For most Indian agencies, the standard Ads Reporting cross-account is sufficient.


How fresh is the data in cross-account reports?


Approximately 24-hour lag for full attribution settlement. Real-time data (current day) is available but noisy. For accurate ROAS reporting across brands, always run cross-account reports excluding the current day. Most agencies run them with a 1-day lag built into the filter.


Can I share cross-account reports with my clients?


Carefully. Scheduled reports go to the email addresses you specify. Make sure each client only receives reports for their own brand — sending a cross-brand report to one client exposes competitor data. Best practice: build separate single-account reports per client, keep the cross-account view internal to the agency.


Does cross-account reporting work for brands using different Pixel setups?


Yes, with caveats. The report aggregates ad-level metrics that Meta computes, regardless of Pixel implementation. But comparing CPA or ROAS across brands with very different Pixel quality (one at 60%, another at 95%) is misleading — the lower-quality Pixel underreports. Standardize Pixel quality before cross-comparing performance.

Comments


bottom of page