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
1
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.
2
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.
3
Select the shops
Choose the shops to connect from the list of shops linked to the Cafe24 account.
4
Submit
Click Submit to complete the connection. Initial data availability can take up to one business day.
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.Troubleshooting
Numbers differ from the Cafe24 commerce data source
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.
Query rejected with INVALID_DIMENSIONS_METRICS_COMBINATION
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.
Date range longer than the breakdown cap
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.
Refresh requests appear slow
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.
OAuth refresh fails after disconnecting in Cafe24
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.
Related
Cafe24 Analytics data reference
Metrics, breakdowns, endpoints, and limits for Cafe24 Analytics.
Cafe24 Analytics FAQs
Common questions and expected behaviors for the Cafe24 Analytics data source.
How to connect Cafe24
Connect raw orders, products, and customers from the Cafe24 commerce API.
How to connect Naver Search Ads
Connect a common companion ad source for Korean storefronts.
