t1k:marketing:monetization:cloudx
| Field | Value |
|---|---|
| Module | monetization |
| Version | 1.16.9 |
| Effort | high |
| Tools | — |
How to invoke
Section titled “How to invoke”/t1k:marketing:monetization:cloudxCloudX
Section titled “CloudX”CloudX mediation setup and revenue reporting integration (per-demand-source dashboards).
When to Use
Section titled “When to Use”- Pulling CloudX mediation revenue via the reporting API
- Building per-demand-source (bidder) revenue breakdowns
- Ingesting CloudX revenue into
ad_revenue_daily→ marketing-hubunified_metrics_daily
CloudX is an ad-network MEDIATION / aggregator (publisher-side reporting), not a single demand source.
Reporting API — endpoint & auth
Section titled “Reporting API — endpoint & auth”- Base:
https://provisioning.cloudx.io/api/v1 - Auth:
Authorization: Bearer <reportKey>— key formatsk_…, a single global account key (NOT per-app, NOT OAuth). - Endpoint:
GET /report/breakdown.
Request params
Section titled “Request params”| Param | Value |
|---|---|
start_time / end_time | Unix SECONDS, inclusive. Range ≤ 31 days per call. |
by | dimension CSV — any of day,country,os,app,ad_unit,format,bidder |
metrics | CSV — any of revenue,impressions,ecpm,requests,clicks,ctr,fill_rate |
granularity | daily |
test_mode | production |
Response shape
Section titled “Response shape”{ "dimensions": [], "metrics": [], "rows": [ { "dimensions": { "k": "str" }, "metrics": { "k": 0.0 } } ], "row_count": 0}rowscapped at ≤ 100k.dimensionsvalues are strings;metricsvalues are numbers.
revenue semantics
Section titled “revenue semantics”revenueis decimal USD — NOT micros. Never divide by 1e6.- Sample volume ~$53–68/day.
- Gross-vs-net not yet confirmed with the vendor — assume gross USD; confirm before trusting totals.
Per-demand-source dimension — bidder (no two-call conflict)
Section titled “Per-demand-source dimension — bidder (no two-call conflict)”by=biddergives the per-demand-source breakdown — CloudX’sAD_SOURCEequivalent (cf. AdMobAD_SOURCE, AppLovinnetwork).- CloudX reporting is publisher-side: there is no per-buyer “responses / filled” count.
fill_rateis reported, but there is no responses base behind it.
Quirks
Section titled “Quirks”- Range ≤ 31 days → chunk longer backfills into ≤31-day windows.
- All periods are UTC.
- The
daydimension is already formattedYYYY-MM-DD(no epoch math on output rows). - As a MEDIATION, isolate CloudX’s own-mediation revenue when aggregating to avoid double-counting against any overlapping MAX demand (mirror the AdMob
MEDIATION_GROUPrule documented in the admob skill). CloudX’s mediated total already spans its demand sources — do not also add a network that CloudX itself mediates.
Platform service
Section titled “Platform service”apps/cloudx-api(peer ofmintegral-monet-api), port 17402.- Ingests into
ad_revenue_daily→ marketing-hubunified_metrics_dailywithsource='cloudx'.
References
Section titled “References”- CloudX reporting (live-verified 2026-06-24):
GET https://provisioning.cloudx.io/api/v1/report/breakdown(Bearersk_…).