Skip to main content

​
Introduction

Mobon is a Korean digital ad network operated by Enliple that distributes performance display and retargeting campaigns across Korean publishers. The Adriel connector (current variant, Mobon v3) pulls daily campaign performance from the Mobon API Center, with most metrics broken out across total, mobile, and web placements. Metrics and currencies are standardized so widgets can aggregate Mobon data alongside other sources without extra configuration. To connect this data source, see How to connect Mobon to Adriel.

​
Data refresh strategy

Mobon is a daily-cache connector. Report data comes from cached daily performance snapshots refreshed from the Mobon API; widgets always read cached data rather than querying the API live.

​
Architecture data

Architecture covers the advertisers and campaigns surfaced by the Mobon API. It refreshes on the same cadence as report syncs and is cached for one hour for picker lookups.

​
Reports data

On data source creation, the cache fills with 1825 days (approximately 5 years) of historic daily data. Reports then refresh at 0 minutes past the hour, every 5 hours UTC. Each refresh syncs the last 30 days, so the recent rolling window stays accurate while older snapshots remain frozen at their last captured value.

​
Architecture levels

Mobon exposes campaign-level performance under each advertiser: Advertiser (or agency) → Campaign

​
Date range limits

Cached daily data is available for up to 1825 days (approximately 5 years) from the initial fetch, with the trailing 30-day window refreshed every 5 hours. Queries that span dates earlier than the initial backfill return no data for the missing range.

​
Metrics

How to read the columns Data type — how the metric is formatted (Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean). Widgets and formulas use this to render values correctly. API Key — code style like viewCnt is the literal Mobon API field name. Italic text describes how a value is produced when it doesn’t map cleanly to a single API field.
Most core metrics are reported with combined, mobile, and web variants. Selecting only the combined metric is sufficient for top-line reporting; the mobile and web splits are useful when breaking out placement performance.

​
Delivery

​
Cost

​
Conversions

​
Revenue

​
Return

​
Breakdowns

​
Time

Adriel provides these time breakdowns on top of the Mobon data. They group cached daily rows into the selected period.

​
Account and campaign

​
General

Adriel provides these breakdowns to control row grouping and to label rows by data source.

​
Limitations

  • Data is cache-only. It refreshes on a fixed schedule (the last 30 days every 5 hours), so recent changes appear only after the next scheduled run rather than immediately. Mobon is not a real-time data source.
  • Historical data is available for up to 5 years from the initial fetch. Dates earlier than the initial backfill return no data.
  • Amounts default to Korean won (KRW). When aggregating Mobon alongside accounts in other currencies, account for currency normalization downstream.
  • Mobile and web splits do not always sum exactly to the combined metric, because placement attribution can differ. Use the combined metrics for top-line reporting.
  • A legacy Mobon variant (API-key authentication against an older endpoint) remains available for existing connections, but new connections should use the current variant. The legacy variant emulates daily breakdowns through row aggregation rather than a native daily cache.
  • The current variant performs one automatic token refresh and retry when an API call returns HTTP 401 or 403 or reports an invalid token. Persistent authentication failures require reconnecting the data source.

​
API references

  • Mobon API Center (current variant): https://api-center.mobon.net/api/ (stats endpoint report/ad/stats)
  • Legacy Mobon endpoint: https://www.mediacategory.com/servlet/API/3.0/JSON/sNo/0/API_REPORT

​
See also