--- title: "Demand Comparison: Reconcile CloudX Delivery Against Partner Reporting" description: "Demand Comparison matches CloudX ad units against partner-reported revenue, impressions, and eCPM across all of your connected accounts in one dashboard and API." url: "https://www.cloudx.ai/posts/demand-comparison" published: "2026-10-29T16:00:00+01:00" authors: - "Jacob Young" - "Sanja Zakovska" category: "Product Updates" --- # Demand Comparison: Reconcile CloudX Delivery Against Partner Reporting Compare revenue, eCPM, and impressions between CloudX and your demand partners down to the ad unit, in the dashboard or via the API. *By Jacob Young, Sanja Zakovska ยท Published Oct 29, 2026* Today we're launching Demand Comparison, a single place in the [CloudX Dashboard](https://docs.cloudx.io/en/dashboard) and [CloudX API](https://docs.cloudx.io/en/api) to check how CloudX-mediated revenue, impressions, and eCPM line up against what your [demand partners](https://docs.cloudx.io/en/demand/partners) report. ![Demand Comparison Delta view showing the daily revenue difference curve against the zero line with Revenue, eCPM, and Impressions toggles alongside Delta, Lines, and Waterfall view switches](https://www.cloudx.ai/images/posts/demand-comparison/delta.gif) Every publisher wants to know that their mediation platform is recording revenue, impressions, and eCPM accurately compared to their bidder integrations. Checking that by hand means pulling daily CSVs from each demand partner portal, lining up UTC cutoffs, and matching external placement IDs in spreadsheets. Demand Comparison pulls partner reporting directly into CloudX, matches it against CloudX delivery down to the [ad unit](https://docs.cloudx.io/en/dashboard/ad-units), and shows where differences arise. ## Connect multiple accounts across every studio Publishers with more than one studio or business entity often run several accounts with the same partner. In [Data Sources](https://app.cloudx.io/settings/data-sources), you can connect and label as many accounts as you run across your [demand partners](https://docs.cloudx.io/en/demand/partners) and [mediation platforms](https://docs.cloudx.io/en/dashboard/total-revenue). Demand Comparison brings all of those business accounts and properties into one view, and lets you filter down to a single business or property whenever you want to audit one studio on its own. ![Data Sources connection card for Meta Audience Network showing three labeled studio business accounts connected to the same workspace](https://www.cloudx.ai/images/posts/demand-comparison/accounts.webp) ## Spot where differences arise Discrepancies rarely show up evenly across your entire portfolio. A gap usually starts on a specific day, inside one network, or on a single placement after a release or configuration change. Demand Comparison lets you isolate that exact slice of inventory. Click and drag across any span of days to zoom into a specific time window, and filter by demand source, business account, property, or [ad unit](https://docs.cloudx.io/en/dashboard/ad-units) across revenue, eCPM, and impressions. You can narrow a portfolio-wide gap down to the day, integration, and placement where CloudX delivery and partner [reporting](https://docs.cloudx.io/en/dashboard/reporting) diverged. ## Matched at the ad-unit level When you configure [Network Mapping](https://docs.cloudx.io/en/dashboard/ad-units#after-creating-an-ad-unit) on a CloudX [ad unit](https://docs.cloudx.io/en/dashboard/ad-units), you link it to the corresponding placement on the bidder side. Demand Comparison uses that link to pair CloudX delivery directly with what each partner reports for the same placement on a daily UTC grain. Because the match happens at the placement level, you can see how CloudX and each demand partner line up on revenue, eCPM, and impressions for every mapped ad unit, rather than only comparing account-wide totals. When a partner reports traffic on placements that aren't linked to a CloudX ad unit, or when a partner sync is still catching up for the latest day, Demand Comparison separates those rows and flags them directly so unmapped inventory never looks like a mediation discrepancy. ![Demand Comparison table showing CloudX and partner revenue, eCPM, and impressions side by side across Meta Audience Network, InMobi, and Moloco, with Meta expanded to ad-unit rows](https://www.cloudx.ai/images/posts/demand-comparison/table.webp) ## Integrate with CloudX's Demand Comparison API If you want to integrate CloudX's matching of revenue, impressions, and eCPM against bidder integrations into your own reporting or BI warehouse, the same dataset is available through the [CloudX API](https://docs.cloudx.io/en/api). Both endpoints accept the same filters as the dashboard, including demand source, provider business ID, provider property ID, and CloudX ad unit ID: - [`report/demand-comparison`](https://docs.cloudx.io/en/api-reference/reporting/reportdemand-comparison): demand-source summaries and daily time series. - [`report/demand-comparison/ad-units`](https://docs.cloudx.io/en/api-reference/reporting/reportdemand-comparisonad-units): partner and CloudX ad-unit breakdowns. ```bash curl -G "https://api.cloudx.io/api/v1/report/demand-comparison" \ -H "Authorization: Bearer $CLOUDX_API_KEY" \ --data-urlencode "start_time=1761523200" \ --data-urlencode "end_time=1764115200" \ --data-urlencode "demand_source=meta" \ --data-urlencode "demand_source=inmobi" ``` ## Getting started Demand Comparison is available in the CloudX Dashboard. Connect your partner accounts in [Data Sources](https://app.cloudx.io/settings/data-sources), then open [Demand Comparison](https://app.cloudx.io/demand-comparison) to review your inventory. See the [Demand Comparison docs](https://docs.cloudx.io/en/dashboard/demand-comparison) for setup details. API reference: - [`report/demand-comparison`](https://docs.cloudx.io/en/api-reference/reporting/reportdemand-comparison) - [`report/demand-comparison/ad-units`](https://docs.cloudx.io/en/api-reference/reporting/reportdemand-comparisonad-units) Questions and requests: [hello@cloudx.io](mailto:hello@cloudx.io).