Performance per account table
The Performance per account table lists every ad account with full metrics (spend, CPM, CTR, CPC, ATC, purchases, sales, ROAS) and a platform badge.
Written By Salvatore Sinigaglia
Last updated About 1 hour ago
The Performance per account table lists every ad account with full metrics (spend, CPM, CTR, CPC, ATC, purchases, sales, ROAS) and a platform badge.
Performance per account table
The Performance per account table is the workhorse comparison surface in Wevion Analytics. It lists one row per selected ad account, each tagged with a platform badge, so you can compare accounts and platforms side-by-side. The Advertising view shows media metrics (spend, CPM, CTR, link clicks, CPC, ATC, purchases, sales, cost/purchase, CVR, ROAS); the Store & Business view shows blended metrics against store revenue. This table replaces the retired Cross-Channel comparison matrix.
Who is this for
Mediabuyers comparing accounts and platforms at a glance, and deciding where to scale, hold, or cut.
Advertising view columns
Each row is one ad account with a platform badge:
Store & Business view columns
In the Store & Business view the per-account table blends each account's spend with store outcomes, so you read accounts through a commerce lens (revenue contribution, orders, and the blended efficiency ratios) rather than platform-attributed conversions.
How to read it
- Group by platform: rows carry a platform badge, so you can scan all Meta accounts, all Google accounts, etc., and compare a platform's accounts among themselves.
- Compare ROAS with spend: the winning pattern is high ROAS on meaningful spend. A high ROAS on tiny spend is an unvalidated test.
- Watch CPC and CTR together: high CTR + low CPC means an engaged audience at an efficient cost; low CTR + high CPC means you're wasting reach.
- Costo/acq (CPA) for lead or purchase efficiency: lower is better; compare across accounts on the same platform for a fair read.
Decision frameworks
Scale or cut an account
- ROAS well above target with meaningful spend β scale (do it in Ads Manager)
- ROAS well below target with meaningful spend β cut or fix creative/targeting
- In between β hold and optimise
Diagnose a platform
If one platform's accounts all show climbing CPM and falling ROAS, the issue is the channel, not a single account β rebalance budget toward stronger platforms.
Compare against the previous period
Enable Compare to previous period in the date picker to add deltas to the KPI grid above the table, so you can tell whether the accounts are trending better or worse β not just their current snapshot. See an-113 comparing periods.
What the table doesn't show
- Per-campaign / adset / ad breakdown β use Ads Manager for row-level detail and edits
- Per-creative performance β use the creative analytics gallery (
/analytics/creatives) - Why an account performs the way it does β drill into Ads Manager or the platform's own dashboard
Common mistakes
- Sorting by spend and treating the top as "best": the biggest spender isn't necessarily the most efficient β read ROAS and CPA too.
- Reading a single row in isolation: the value is the comparison across accounts and platforms.
- Ignoring the spend column when comparing ROAS: low-spend ROAS is noisy.
Common issues
- An account is missing: it wasn't included in your selection, or had no data in the window.
- Numbers differ from a platform's native UI: 15-minute sync plus 24-72h postback lag (see an-114).
- Empty table: no accounts selected β open the cascade selector and apply a selection.
FAQ
What does the Performance per account table show in Wevion Analytics?
It lists one row per selected ad account, each with a platform badge, and full metrics for the period. In the Advertising view that means spend, CPM, CTR, link clicks, CPC, ATC, purchases, sales, cost per purchase, CVR, and ROAS. In the Store & Business view the same accounts are shown through a commerce lens, blending their spend against store revenue and orders. It's the main way to compare accounts and platforms side-by-side.
How do I compare platforms with this table?
Because every row carries a platform badge, you can group and scan accounts by platform β all Meta accounts together, all Google accounts together, and so on β and compare their spend, ROAS, CPC, and CPA. Pair it with the Advertising view's Spend Γ ROAS scatter, which rolls the same data up to one bubble per platform, for a higher-level platform comparison.
How do I decide whether to scale or cut an account?
Read ROAS together with spend and CPA. An account with ROAS clearly above your target and meaningful spend is a scale candidate; one with ROAS well below target and meaningful spend is a cut-or-fix candidate; anything in between you hold and optimise. Confirm big budget moves against blended MER in the Store & Business view, since platform ROAS can mislead. Then act in Ads Manager, where edits happen.
Why do the table numbers differ from a platform's native dashboard?
Small differences are expected. Wevion syncs platform insights roughly every 15 minutes, and purchase-based metrics like ROAS and cost per purchase settle over 24-72 hours via postback, so recent days keep filling in. A platform's own dashboard is closer to real-time. Use a last_7d minimum window for ROAS and CPA reads, and treat modest variance as normal rather than a bug.