Analytics

The Analytics page is the merchant-wide view of how the storefront performs. It is split into three tabs — Collections, Search and Recommendations — one per analytics area, and every number covers the selected period compared with the equally long period immediately before it.

​

Limits and behavior

• The Analytics page appears only for stores with analytics enabled. Without it, the sidebar item is hidden and a direct link shows “The analytics page is not enabled for your account.”
• Analytics is enabled per area. The Search and Recommendations tabs render only when their area is enabled; the Collections tab is always available when the page is.
• The period is selectable: 30d (default), 7d, 1d or Custom (start and end date). Every metric is compared with the equally long period immediately before the selected one; there is no year-over-year comparison on this page.
• The period and market selection is shared across pages — the same selection follows you between Dashboard, Analytics and Collections.
• Attributed metrics (revenue, add-to-carts, orders) are approximate and last-touch, with a 7-day attribution window. Attributed revenue is summed across markets without currency conversion.
• Impressions are counted from when impression tracking shipped and cover only surfaces that report visibility, so CTR can read high until coverage is complete.
• CSV export numbers are store-wide (all markets), and the export modal’s time range is independent of the page’s selection (it defaults to 30d).
• When the metrics backend is unavailable, tiles show empty values rather than errors; the corresponding API endpoints return a null body, and the CSV export endpoint returns HTTP 503.
• Analytics API keys: at most 50 active keys per store; the key secret is shown once at creation and cannot be retrieved again.

​

Collections tab

The Collections tab is the merchant-wide overview. It shows: Clicking a KPI tile opens a daily-trend view for that metric over the selected period. Below the KPI row:

• The merchant-wide conversion funnel from impressions through clicks and add-to-carts to purchases, with stage-to-stage conversion rates. Add to cart appears as a stage once add-to-cart tracking events are flowing.
• Top collections by revenue, with page-level traffic.
• Losing traffic — the collections losing the most traffic versus the previous period.
• A Pinned vs Auto rollup with the buckets Pins healthy (auto CTR at most 5% ahead of the pins), Check pins (5–30% ahead), Unpin advised (30%+ ahead) and No pins. See Collection analytics for how the verdict works.
• A Benchmark shortcut for side-by-side collection comparison.

​

Search tab

The Search tab covers how shoppers search the store over the selected period: The tab also shows the search funnel (searches → result clicks → add to carts → orders) and two query tables: Most common searches and Most common searches without results, per market.

​

Recommendations tab

The Recommendations tab breaks engagement down By surface, ranked by clicks, with these columns per recommendation surface:

​

Export to CSV

The page header has an Export to CSV button. The export produces one file, one row per metric, with the previous period beside each value; numbers are store-wide (all markets).

1. Click Export to CSV.
2. Pick a time range (30d, 7d, 1d or a custom range — independent of the page’s selection).
3. Select the metric sections to include.
4. Click Export.

Result: a CSV file downloads. Sections that could not load fully or have no data for the period are named in the modal and left incomplete or out of the file.

​

Analytics API keys

Analytics API keys give a merchant’s own systems read-only access to the analytics report endpoints without a browser session — for example a scheduled weekly CSV pull. A key is a string starting with dpk_, sent in the X-API-Key request header. It is scoped to one store and works only on the report endpoints listed below; it cannot modify anything. To create a key:

1. Open Settings, then General.
2. In the API keys card, enter a key name.
3. Click Create key.

Result: the key secret is displayed once, with the notice “Copy this secret now — it won’t be shown again.” The list below shows each key’s name, prefix and creation date. Key management (create, list, revoke) requires a portal login; keys cannot manage other keys. A store can have at most 50 active keys — creating more returns HTTP 409. Revoking a key takes effect immediately.

​

Analytics API endpoints

The following endpoints accept either a portal JWT or a merchant API key via the X-API-Key header. All paths are under /api/v1/merchants/{merchant_id}. The export request body: Comparison responses carry period metadata with source: "snapshot" or "live": periods are served from stored snapshots when one exists and computed from live data otherwise. Live-sourced stock and position figures reflect today, not the historical period.

​

Where the numbers come from

Every metric on this page uses the same backend aggregation as the per-collection metrics — the analytics hub and the collection pages agree. Metric definitions are documented in the tooltips next to each label in the portal.