FAQs

​

What is the difference between the Cafe24 Analytics and Cafe24 commerce connectors?

Both connectors read from the same Cafe24 store, but they surface different data and are set up separately. Cafe24 Analytics reads Cafe24’s own pre-aggregated analytics reports through the Cafe24 Data API: visitor sessions, page views, traffic sources, product views, cart actions, payment methods, sales-per-visitor analyses, and visit-path attribution. These are the same numbers a mall owner sees inside Cafe24’s analytics console. The Cafe24 commerce connector reads the Admin API instead, and reconstructs sales performance from raw orders and products. Use it when the report needs order-level or product-level detail rather than pre-aggregated traffic and sales analytics. Many teams connect both and combine them on one dashboard. For the full field list on each side, see the Cafe24 Analytics data reference and the Cafe24 commerce data reference.

​

Why can’t I combine two Cafe24 Analytics breakdowns in one widget?

Cafe24 Analytics is organized as separate report families, and each family is a distinct Cafe24 Data API report that exposes exactly one grouping column. A single query can therefore target only one breakdown at a time. A widget that requests more than one non-time breakdown is rejected with the error code INVALID_DIMENSIONS_METRICS_COMBINATION. Because the available metrics are tied to the selected report, metrics from one report family also cannot be paired with a breakdown from another. To compare two groupings, build one widget per breakdown. A time breakdown such as Daily, Weekly, or Monthly can still be applied alongside the single report breakdown.

​

Why is data older than 90 days missing from Cafe24 Analytics?

Adriel imports up to the last 90 days of daily data when the data source is first connected. Reporting on dates before that initial window returns no rows right after connecting. Because Adriel caches the data it retrieves, the longer the data source stays connected, the more history accumulates in the cache. A newly connected store starts with the 90-day import and builds coverage from there, so ranges that were empty at first fill in over time. Separately, each query has a maximum span per time breakdown: longer pulls must be split into several queries. The exact per-breakdown caps are listed in the Cafe24 Analytics data reference.

​

Why are large Cafe24 Analytics queries slow?

Requests to the Cafe24 Data API are paced and processed one at a time per data source to stay within Cafe24’s quotas, so a widget that spans many days across several report families takes longer to return than a small one. To speed a report up, narrow the date range, reduce the number of report families on a single dashboard, or use a coarser time breakdown such as Weekly or Monthly for long spans instead of Daily. Splitting one very wide widget into a few focused widgets also helps, since each query then covers less data.

​

Why don’t Cafe24 Analytics numbers match my raw order reports?

Cafe24 Analytics returns Cafe24’s own pre-aggregated dashboard figures, not order-level records. Those figures can differ from the raw order and product totals surfaced by the Cafe24 commerce connector, which reconstructs sales from individual orders. The two are counting different things, so small gaps between them are expected. For pre-aggregated traffic and sales analytics, use the Cafe24 Analytics data source. For order-level and product-level detail, use the Cafe24 commerce connector.

​

Related