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

# How to connect

> How to connect the Cafe24 Analytics data source to Adriel: retrieve the Shop ID, authorize OAuth2, select shops, and verify data.

Cafe24 is a Korean e-commerce platform that helps merchants run their direct-to-consumer storefronts. Cafe24 Analytics is the pre-aggregated analytics surface of that platform — sessions, page views, traffic sources, product views and sales, cart actions, payment methods, sales-per-visitor analyses, and visit-path attribution — pulled from the Cafe24 Data API so the numbers match Cafe24's own dashboards.

## Before you connect

The following are required:

* A Cafe24 mall with admin access. Super admin rights are required to retrieve the Shop ID.
* The Cafe24 analytics value-added service enabled for the mall.
* Permission to grant OAuth2 access for the analytics scopes.
* The Cafe24 **Shop ID** (the subdomain in the admin URL). To find it, log in to the Cafe24 Admin page with a super admin account, go to **Shopping mall settings** in the left sidebar, then open **Basic Settings** > **About my mall** > **Shop ID** and copy the value.
* Optional: a custom Cafe24 Developers app (Client App ID and Secret) for per-connection app overrides.

## Connect Cafe24 Analytics

<Steps>
  <Step title="Select the data source and enter the Shop ID">
    On the **Data Sources** page, search for **Cafe24 Analytics** and select it. Enter the **Shop ID** copied earlier.
  </Step>

  <Step title="Authorize the Cafe24 account">
    Sign in to the Cafe24 account in the pop-up window and grant the requested analytics permissions. The refresh token rotates on every refresh.
  </Step>

  <Step title="Select the shops">
    Choose the shops to connect from the list of shops linked to the Cafe24 account.
  </Step>

  <Step title="Submit">
    Click **Submit** to complete the connection. Initial data availability can take up to one business day.
  </Step>
</Steps>

## What gets imported

The last 90 days of daily data are backfilled on first connection, and the cache then refreshes twice daily at 02:00 UTC and 14:00 UTC. Per-query date ranges are capped at 60 days for daily breakdowns, 12 weeks for weekly, and 12 months for monthly. Report families cover 23 Cafe24 Data API endpoints plus 6 computed metrics; each endpoint exposes a single breakdown column, and only one non-time breakdown is allowed per query.

For the complete metric and breakdown list, see the [Cafe24 Analytics data reference](/data-sources/a-f/cafe24-analytics/data-reference).

## Troubleshooting

<AccordionGroup>
  <Accordion title="Numbers differ from the Cafe24 commerce data source">
    Cafe24 Analytics returns Cafe24's pre-aggregated session, funnel, and sales-per-visitor numbers, while the Cafe24 commerce connector returns raw orders, products, and customer detail from the Admin API. The two surfaces measure different things: use Cafe24 commerce for transactional reporting and Cafe24 Analytics for storefront traffic and funnel.
  </Accordion>

  <Accordion title="Query rejected with INVALID_DIMENSIONS_METRICS_COMBINATION">
    Each endpoint allows exactly one non-time breakdown. Queries that combine multiple non-time breakdowns are rejected. Split the report into separate queries.
  </Accordion>

  <Accordion title="Date range longer than the breakdown cap">
    Daily queries cap at 60 days, weekly at 12 weeks, and monthly at 12 months. Longer historical pulls must be split into multiple queries. Data older than the 90-day initial backfill is not retained in cache.
  </Accordion>

  <Accordion title="Refresh requests appear slow">
    The connector forces worker concurrency to 1 and throttles outgoing requests to one per 500 ms per data source to stay inside Cafe24's quotas. Large syncs are paced rather than parallelized.
  </Accordion>

  <Accordion title="OAuth refresh fails after disconnecting in Cafe24">
    The refresh token is single-use and rotates on every refresh. If the OAuth grant is revoked or expires in Cafe24, the connection must be re-authorized. Use the **Reconnect** action to restart the OAuth flow.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Cafe24 Analytics data reference" href="/data-sources/a-f/cafe24-analytics/data-reference">
    Metrics, breakdowns, endpoints, and limits for Cafe24 Analytics.
  </Card>

  <Card title="Cafe24 Analytics FAQs" href="/data-sources/a-f/cafe24-analytics/faqs">
    Common questions and expected behaviors for the Cafe24 Analytics data source.
  </Card>

  <Card title="How to connect Cafe24" href="/data-sources/a-f/cafe24/how-to-connect">
    Connect raw orders, products, and customers from the Cafe24 commerce API.
  </Card>

  <Card title="How to connect Naver Search Ads" href="/data-sources/g-n/naver-search-ads/how-to-connect">
    Connect a common companion ad source for Korean storefronts.
  </Card>
</CardGroup>