Skip to main content
Metrics type: Key Metrics • Category: Ad Platform

​
At a glance

MediaMath-attributed conversion value via the T1 conversion-tracking pixel (or server-side via Adaptive Segments). Includes view-through credit from CTV and display impressions where configured. Status note (May 26): the platform’s conversion-tracking infrastructure has had episodic instability since the Jun 23 restructure; verify your pixel is firing and reconciling cleanly month-to-month.

​
Calculation

Calculated automatically from your MediaMath data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

The same enterprise homeware brand. Window 02 Apr 26 to 01 May 26. Shopify-side revenue this window: 1.18M.UTM−taggedMediaMath−sourcerevenue:1.18M. UTM-tagged MediaMath-source revenue: 58,400. GA4 Paid Display + Paid Video attributed: $84,200. What’s interesting:
  1. Account-level revenue 164,600vsShopify−truth164,600 vs Shopify-truth 58,400 = 2.82× DSP over-claim. This is the standard structural gap; nothing MediaMath-specific. View-through credit ($53,600) is mostly the wedge.
  2. CTV PMP (NBC) at $38,200 view-through revenue is hard to validate independently, no click events, no GA4 equivalent. Run a CTV holdout test in one geo for 14 days to confirm incrementality before betting the channel.
  3. Retargeting at 4.5× ROAS is the standout campaign; same dynamic as on every DSP, retargeting reaches users who already showed intent.
  4. Display Prospecting at 2.93× ROAS is the workhorse; healthy enterprise display number.
  5. The 30D prior had $148,800 revenue; this window up 11% vs spend up 18%, slight ROAS compression. Common shape for a maturing campaign portfolio.
  6. Reconciliation flag: if T1 UI shows materially different revenue, suspect a pixel-firing or batch-processing issue; the post-restructure platform has had episodic stability problems. Don’t accept the divergence at face value.
Quick sanity tests:
  • Revenue up + spend up + ROAS flat = healthy.
  • Revenue down + clicks held = pixel issue. Check pixel health first on MediaMath, more common cause than on peer DSPs post-restructure.
  • Revenue up but Shopify-side flat = DSP claim inflating; multi-touch over-claim.
  • CTV view-through revenue dropped sharply = view-through window probably reduced from 7d to 1d.
  • All campaigns revenue dropped simultaneously = global pixel/site outage.

​
Sibling cards merchants should reference together

​
Reconciling against the vendor’s own dashboard

Where to look in MediaMath T1: T1 → Reports → Campaigns → Conversion Value at organisation level. Should match this card to within sub-percent rounding. MediaMath-specific reconciliation caveat: Pixel-fired conversion ingest has been episodically unreliable since the Jun 23 restructure. If this card differs from T1 UI by >5%, suspect a platform-side issue before adjusting downstream. Why our number may legitimately differ from T1: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

My MediaMath revenue dropped 30% but spend is unchanged, what should I check first? Pixel health, before anything else, on MediaMath specifically. The post-restructure platform has had episodic conversion-tracking instability that peer DSPs (TTD, DV360) have not. Open T1 → Pixels → diagnostics; check that the conversion pixel is firing on order-confirmation in the last 24, 48 hours. If pixel is healthy, then proceed to standard checks: audience freshness, attribution-window changes, site config. Why does MediaMath revenue under-report compared to TTD or DV360? Two reasons in 2026: (1) the pixel infrastructure has had stability issues since restructure, leading to occasional under-counting; (2) view-through tracking on CTV has been less reliable as some inventory partners deprioritised MediaMath integrations during the restructure period. If you see persistent under-counting (>10% gap to peer DSPs on like-for-like inventory), raise with MediaMath account management. Should I trust the MediaMath revenue number for ROAS? Within MediaMath’s own walls, yes (the ROAS card uses the same numbers consistently). For business-truth comparison, discount the MediaMath claim by 40, 60% to approximate Shopify-truth contribution, same heuristic as other DSPs. Treat the absolute number with extra scepticism on this connector and reconcile to T1 UI more often than you would on TTD. My CTV revenue dropped 50%, what happened? First check the view-through window setting (1 day vs 7 days). If unchanged, suspect: (a) a PMP deal lapsed or was renegotiated; (b) inventory partner rebalanced toward TTD/DV360 post-MediaMath restructure; (c) the conversion pixel had an outage. Always check pixel before campaign config on this connector. Why is my retargeting revenue stable but prospecting revenue dropped? Retargeting works on first-party audience data, which is platform-resilient. Prospecting depends on access to broader inventory pools and SSP partnerships, which compressed for MediaMath post-restructure. If prospecting reach is degrading, it’s a structural platform issue more than a campaign issue. Can the “today” revenue figure be trusted? Less than rolling 7-day, more than on peer DSPs because of slower ingest. Use 7-day rolling for actionable reads. My multi-region account, how does revenue work? MediaMath organisations are typically single-currency. Multi-region advertisers run separate orgs per region; this card is per-org. Aggregate across regions requires FX at the report layer. Should I migrate to TTD before the data quality issue gets worse? That’s the strategic question many enterprise advertisers have already answered yes to. The data-quality risk is real but bounded; if your contract has another 12+ months and your PMPs are still delivering, the migration cost may not pay back. Maintain a TTD shadow account in parallel (cheap insurance) and migrate when the contract cycles or when stability degrades materially. Why is the alert trigger threshold (-20% vsP) tighter on MediaMath than I’d expect? Because pixel/platform-instability false-alerts on this connector are more common; a 20% drop is the level at which you should investigate (rather than dismiss as noise). On TTD or DV360, a 30% threshold would be appropriate; here, 20% is the right balance between alert-fatigue and missed real issues.

​
Tracked live in Vortex IQ Nerve Centre

Total Revenue is one of hundreds of KPI pulses Vortex IQ tracks across MediaMath and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.