> ## 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.

# Data reference

> Metrics, breakdowns, refresh cadence, and limits for the LINE Ads data source in Adriel.

## Introduction

LINE Ads is the advertising platform of LINE, the messaging app operated by LY Corporation that is dominant in Japan, Taiwan, and Thailand. The connector pulls campaign performance from the LINE Business API v3 across LINE feed, chat, and discovery placements, as well as LINE-internal placements such as Sponsored Stickers and LINE Friends ads.

As a marketing connector, metrics, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration.

To connect this data source, see [How to connect LINE Ads to Adriel](/data-sources/g-n/line-ads/how-to-connect).

## Data refresh strategy

### Architecture data

Architecture covers ad accounts, campaigns, ad sets, ads, and keywords. It refreshes twice daily, at **4:00 PM UTC** and **5:00 AM UTC**. On data source creation, the cache fills with **730 days** of historical architecture data at the ad account, campaign, ad set, ad, and keyword levels.

### Reports data

Reports include daily performance metrics for ad accounts, campaigns, ad sets, ads, and keywords.

**Cache-only.** Report data comes from cached daily performance snapshots. When a dashboard is opened, the response is composed by aggregating the most recent snapshot rather than by fetching from LINE on demand.

**Refresh schedule.** Reports refresh at **10:00 PM UTC** and **7:00 AM UTC**. Each refresh syncs the **last 30 days** for the breakdowns `adAccount`, `campaign`, `adSet`, and `ad`, and for the breakdown combinations `os/adAccount`, `age/adAccount`, `gender/adAccount`, and `location/adAccount`. Data is considered reliable within this cache sync window; data outside it may be incomplete or not fully accurate due to legacy caching behavior.

<Note>
  Metrics based on uniqueness (such as reach) can be overvalued when viewed across a date range longer than one day, because each day's cached snapshot is aggregated independently.
</Note>

## Architecture levels

Ad account → Campaign → Ad group (ad set) → Ad

## Date range limits

To keep query sizes manageable, the connector enforces a maximum look-back window per time breakdown.

| Breakdown | Max range |
| --------- | --------- |
| Daily     | 93 days   |
| Weekly    | 1 year    |
| Monthly   | 2 years   |

## Metrics

<Note>
  **How to read the columns**
  **Data type** uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.
  **API Key** in code style like `spend` is the literal LINE Business API field name. *Italic text* describes how a value is produced when it doesn't map cleanly to a single API field.
</Note>

### Performance

| Metric      | Description                             | Data type  | API Key                                        |
| ----------- | --------------------------------------- | ---------- | ---------------------------------------------- |
| Spend       | Reported spend.                         | Currency   | `spend`                                        |
| Impressions | Number of times the ads were displayed. | Number     | `impressions`                                  |
| Clicks      | Number of ad clicks.                    | Number     | `clicks`                                       |
| CTR         | Click-through rate.                     | Percentage | *Adriel-computed (clicks ÷ impressions)*       |
| CPC         | Cost per click.                         | Currency   | *Adriel-computed (spend ÷ clicks)*             |
| CPM         | Cost per thousand impressions.          | Currency   | *Adriel-computed (spend ÷ impressions × 1000)* |

### Conversion

| Metric           | Description                            | Data type | API Key           |
| ---------------- | -------------------------------------- | --------- | ----------------- |
| Conversions      | Attributed conversion events.          | Number    | `conversions`     |
| Conversion value | Total value of attributed conversions. | Currency  | `conversionValue` |

### Engagement

| Metric           | Description                                                                | Data type | API Key           |
| ---------------- | -------------------------------------------------------------------------- | --------- | ----------------- |
| Friend additions | LINE-specific: friends added from Sponsored Stickers and LINE Friends ads. | Number    | `friendAdditions` |

## Breakdowns

### Campaign structure

| Breakdown         | Description                 | API Key     |
| ----------------- | --------------------------- | ----------- |
| Ad account        | Group by ad account.        | `adAccount` |
| Campaign          | Group by campaign.          | `campaign`  |
| Ad group (ad set) | Group by ad group (ad set). | `adSet`     |
| Ad                | Group by ad.                | `ad`        |

### Placement, audience, and geography

<Note>
  The OS, age, gender, and location breakdowns are available only at the ad account level. Splitting them by campaign, ad set, or ad is not supported by the LINE Business API.
</Note>

| Breakdown | Description                                                | API Key     |
| --------- | ---------------------------------------------------------- | ----------- |
| Placement | Split by placement, such as LINE feed, chat, or discovery. | `placement` |
| OS        | Operating system, at the ad account level.                 | `os`        |
| Age       | Age bucket, at the ad account level.                       | `age`       |
| Gender    | Gender, at the ad account level.                           | `gender`    |
| Location  | Location, at the ad account level.                         | `location`  |

### Time

| Breakdown       | Description           | API Key |
| --------------- | --------------------- | ------- |
| Daily breakdown | Split reports by day. | `date`  |

## Limitations

* **Ad-account-scoped breakdowns** — the OS, age, gender, and location breakdowns are available only at the ad account level and cannot be combined with the campaign, ad set, or ad levels.
* **Cache-only reports** — performance data is served from cached daily snapshots produced through LINE's asynchronous CSV report pipeline (a report job is requested, polled until ready, then downloaded and parsed), so it is never live-fetched and may lag the platform slightly.
* **Uniqueness caveat** — metrics based on uniqueness, such as reach, can be overvalued across a date range longer than one day.
* **Cache sync window** — each refresh re-syncs only the last 30 days. Older data is preserved in the cache but is not re-synced, so values outside the sync window may be incomplete or not fully accurate.

## API references

* [LINE Developers portal](https://developers.line.biz/) (LINE Business API v3)

## See also

* [How to connect LINE Ads to Adriel](/data-sources/g-n/line-ads/how-to-connect) (paired how-to)
* [Naver GFA data reference](/data-sources/g-n/naver-gfa/data-reference) — for a comparable Asian shared-account display platform
* [Yahoo Ads data reference](/data-sources/o-z/yahoo-ads/data-reference) — for paired Japanese-market planning