Center Data Export (ZIP)
If a center terminates the contract and wants to take its Cockpit data with it, authorized users can generate a read-only ZIP export. During this process, no data is deleted or changed in the cockpit.
Where in the Dashboard
Content → Shopping Center → Edit Center → Tab “Management” → Export Center Data (ZIP).
When exporting, a progress dialog will open (showing percentage and current step, e.g., database, Umami, bot statistics, images). Do not close the window during the export – the ZIP download will start automatically when everything is ready.
Find in the documentation: Topic Finder (Center & Organization) or search at the top (Ctrl+K / ⌘+K) for “Data export”.
Authorization
Export is possible for:
- Super Admin
- Center Administrator / Marketing Manager (Organization), if the center belongs to their own organization
- Users with the center assignment “Export Data” (
canExportDataunder Settings → Users → Center Assignment)
Content of the ZIP Archive
| Folder/File | Content |
|---|---|
README.txt | Quick guide |
manifest.json | Timestamp, counter, status of media downloads |
data/*.json | Master data, shops, branches, chains, news, events, offers, jobs, services, offices, page content, center plan metadata, categories, … |
data/umami-analytics.json | Website Analytics (Umami): aggregated metrics and trends for 30, 90, and 365 days – only if analytics is active for the center and Umami is accessible (see below) |
data/bot-analytics.json | AI Assistant / Bot: usage by channel (website, kiosk, companion), top searches, intents, mentions, journey funnel – periods of 30/90/365 days |
data/chatbotInteractions.json | Raw data of all bot interactions (anonymized: no chat response texts) |
data/centerUsageEvents.json | Raw data usage events (kiosk/companion/website, e.g., journey steps) |
csv/*.csv | Excel-compatible extracts (shops, news, offers, …) |
csv/bot/ | Bot & AI evaluation for Excel (see below) |
media/ | Images only: SVG, JPG/JPEG, PNG (no 3D models, videos, PDFs) |
Not included (data protection/security): Passwords (e.g., analytics page password), user accounts of other centers.
Media: The media/ folder will only download SVG, JPG/JPEG, and PNG files. 3D models (GLB, GLTF, …), videos, PDFs, and other formats are excluded; their URLs remain in the JSON files under data/ and are listed in manifest.json under excludedMediaUrls.
Size limits (images): Maximum single file size 25 MB, total media archive max. around 400 MB.
Umami Statistics in the Export
If the center uses Website Analytics (Umami) (analyticsEnabled, Umami website ID under Center → Analytics), the export will attempt to retrieve the same aggregated metrics as in the dashboard when creating the ZIP file (page views, visitors, visits, trends by day/month).
| Situation | Result in umami-analytics.json |
|---|---|
| Analytics off or another provider | included: false with a brief explanation |
Umami active, server has UMAMI_PASSWORD | included: true, periods under periods |
| Umami active, API not configured | included: false, note on Umami Dashboard |
The ZIP download does not fail if Umami is not accessible – only the statistics data will be missing. Status is also noted in manifest.json under umamiAnalytics.
Bot and AI Assistant Statistics
For customer analysis (Excel): Folder csv/bot/ — German labeled CSV files with UTF-8-BOM. Quick guide: csv/bot/00-LESEHILFE.txt.
File in csv/bot/ | Content |
|---|---|
01-overview-periods.csv | Usage website / kiosk / companion for 30, 90, and 365 days |
02-top-searches.csv | Most frequent search queries per period |
03-top-intents.csv | Recognized user intents (German designation) |
04–09 | Mentions of shops, gastronomy, services, offers, events, categories |
10-companion-journey.csv | Companion journey steps |
11-interactions-detail.csv | Individual interactions (date, channel, search, intent, names instead of just IDs) |
12-usage-events.csv | Usage events (kiosk/companion/website) prepared in a readable format |
Technical raw data (archive): still under data/:
| File | Content |
|---|---|
bot-analytics.json | Aggregated metrics as in the dashboard (30/90/365 days) |
chatbotInteractions.json | Raw data of all bot interactions |
centerUsageEvents.json | Raw data usage events |
No personal raw chats are exported – only what the system reliably stores for analytics (queryNormalized, mention IDs, intents).
Technical (for developers)
- UI: asynchronous with status dialog –
POST …/export/start,GET …/export/status?jobId=,GET …/export/download?jobId= - Direct download (without progress):
GET /api/centers/[centerId]/export - Implementation:
apps/dashboard/src/lib/center-export/ - Only SELECT queries, no migration, no deletion
Procedure upon Termination (recommended)
- Execute export and archive ZIP
- Contractually document that the export has been received
- Optionally deactivate or delete the center – separate step under “Dangerous Actions”
See also: Users & Organization (right to “Export Data”).
Nutzungsstatistik: Seitenaufrufe werden anonymisiert erfasst. Im Umami-Dashboard nach diesem Pfad filtern: /en/dashboard/center-datenexport