> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQs

> Common questions, expected behaviors, and troubleshooting for the Mobon data source.

## Why don't my mobile and web numbers add up to the combined metric?

Most Mobon metrics come in three variants: a combined value plus separate mobile and web splits. The mobile and web splits do not always sum exactly to the combined metric, because placement attribution can differ between the two surfaces. For top-line reporting, the combined metric is the reliable figure. The mobile and web splits are best used when the goal is to compare placement performance rather than to reconcile a total.

## How far back does my Mobon historical data go?

Adriel imports up to approximately 5 years of daily history when the Mobon data source is first connected. Because Adriel caches the data, the longer the data source stays connected, the more historical data is retained. Dates earlier than the initial import return no data for the missing range, so queries that reach back beyond the 5-year window show empty results for the uncovered period.

## Why are my Mobon amounts shown in Korean won?

Mobon is a Korean ad network, and its reported amounts default to Korean won (KRW). Spend, sales, and cost-per-conversion values therefore render in KRW unless normalized downstream. When Mobon is aggregated on a dashboard alongside data sources in other currencies, currency normalization needs to be accounted for so that combined totals stay meaningful.

## Why don't my recent changes appear right away?

Mobon is a cache-based data source, so widgets read cached daily snapshots rather than querying the platform live. Newly made changes are not immediate; they appear after the next scheduled sync rather than the moment they happen in Mobon. Mobon is not a real-time data source, and there is no on-demand fetch. For the exact refresh schedule, see the [Mobon data reference](/data-sources/g-n/mobon/data-reference).

## Why did my Mobon connection ask me to reconnect?

When a Mobon request fails authentication, Adriel automatically attempts a single token refresh and retry before surfacing an error. Transient failures usually clear on that automatic retry. Persistent authentication failures, however, cannot be recovered automatically, and the data source needs to be reconnected with valid credentials. Reconnecting through the data source settings restores the sync. If the connection still fails after reconnecting, email `support@adriel.com` with the affected data source and dashboard details.

## What is the difference between Mobon and Mobon v3?

Two Mobon data sources are available. The current variant is the recommended choice for new connections and provides a native daily cache with combined, mobile, and web metric splits. An earlier variant remains available for existing connections, but it emulates daily breakdowns through row aggregation rather than a native daily cache. New connections should use the current variant. For the newer data source, see the [Mobon v3 data reference](/data-sources/g-n/mobon-v3/data-reference).

## Related

<CardGroup cols={2}>
  <Card title="Mobon data reference" href="/data-sources/g-n/mobon/data-reference">
    Metrics, breakdowns, refresh cadence, and limits for the Mobon data source.
  </Card>

  <Card title="How to connect Mobon to Adriel" href="/data-sources/g-n/mobon/how-to-connect">
    Steps to authenticate and connect the Mobon data source.
  </Card>

  <Card title="Mobon v3 data reference" href="/data-sources/g-n/mobon-v3/data-reference">
    Reference for the newer Mobon v3 data source variant.
  </Card>

  <Card title="Mobon release notes" href="/data-sources/g-n/mobon/release-notes">
    Recent changes to the Mobon data source.
  </Card>
</CardGroup>