Exports
Export your link catalog and click-level analytics data as CSV for reporting and integrations.
Two types of exports
Nimriz provides two distinct export types, each designed for a different purpose.
Link catalog export-a snapshot of your current link configuration. This shows what each link looks like today: its destination URL, UTM fields, tags, space assignment, expiration, and lifetime click count.
Analytics export-a record of what actually happened at click time. This uses click-time data, not the link's current state. It is the source of truth for attribution, since UTM values captured at click time are preserved even if the link was edited later.
The Exports area also tracks async bulk QR ZIP jobs. These are not CSV exports, but they use the same background-job queue and recent-jobs history.
Link catalog export
What it contains
A link catalog export produces a CSV file with one row per link in your workspace (or matching your active filters). Columns include:
| Column | Description |
|---|---|
url_id | The link's permanent UUID. Use this as your stable reference when syncing with external systems. |
short_code | The slug (e.g., spring-launch). |
short_url | The full short URL (e.g., https://links.example.com/spring-launch). |
domain | The domain the link is on. |
destination_url | The current destination URL. |
utm_source | Current UTM source value. |
utm_medium | Current UTM medium value. |
utm_campaign | Current UTM campaign value. |
utm_term | Current UTM term value. |
utm_content | Current UTM content value. |
custom_query_params | Custom query parameters as a JSON string. |
space | The space name (blank if unassigned). |
tags | Comma-separated list of tag names. |
status | active, disabled, or expired. |
expires_at | Expiration timestamp (ISO 8601), or blank if no expiration. |
password_protected | true or false. |
redirect_status_code | 302 or 301. |
clicks | Lifetime click count (updated periodically, not real-time). |
created_at | Link creation timestamp. |
How to export the link catalog
- Go to the main Links view in your dashboard.
- Optionally apply filters (by space, tag, domain, status) to limit the export to a specific subset.
- Click the Export button in the toolbar.
- Select Link catalog as the export type.
- Confirm. A CSV file downloads immediately for small datasets.
For large workspaces, the export is generated as an async job. You will see a notification when it is ready to download.
Analytics export
What it contains
An analytics export produces a CSV file with one row per click event, within the date range you specify. Columns include:
| Column | Description |
|---|---|
clicked_at | Timestamp of the click event (ISO 8601, UTC). |
url_id | The link UUID that was clicked. |
short_code | The slug at the time of the click. |
domain | The domain on which the click occurred. |
touch_type | short_link_click or qr_scan. |
country | ISO 2-letter country code (best-effort). |
region | Region/state code (best-effort). |
city | City name (best-effort). |
device_category | mobile, tablet, or desktop. |
browser_family | Browser name (best-effort). |
os_family | OS name (best-effort). |
referrer_host | Referring domain (often blank due to privacy). |
social_source | Derived social platform, if identifiable. |
bot_flag | true if the click was classified as automated traffic. |
utm_source | UTM source value at click time. |
utm_medium | UTM medium value at click time. |
utm_campaign | UTM campaign value at click time. |
utm_term | UTM term value at click time. |
utm_content | UTM content value at click time. |
variant_key | A/B test variant key, if routing rules were active on this link. |
Note: Analytics exports use click-time UTM values, not the link's current UTM state. If you changed a link's utm_campaign after some clicks happened, the export will show both the old and new values for their respective click windows.
How to generate an analytics export
- Go to Exports in the dashboard navigation.
- Click New export.
- Select Analytics export as the export type.
- Set the date range. Exports are available for any range within your plan's data retention period.
- Optionally filter by domain, space, or tags.
- Click Generate export.
Analytics exports are always async-they run as background jobs and are typically ready within a few minutes for smaller date ranges.
Bulk QR ZIP downloads
Growth, Professional, and Enterprise workspaces can queue a ZIP of QR assets from the main Links table.
What the ZIP includes
- One rendered QR asset per successful link selection.
- Files generated from each link's saved effective QR state, including preset bindings, per-link overrides, transparent backgrounds, frames, and logos.
- A
manifest.jsonfile describing every requested link, whether it succeeded or failed, and which render source Nimriz used.
What manifest.json contains
Each result row can include:
| Field | Description |
|---|---|
url_id | Permanent UUID of the selected link. |
status | ready or failed. |
short_code | Link slug when available. |
domain_name | Domain used for the QR asset when available. |
file_name | Generated filename inside the ZIP for successful renders. |
qr_style_hash | Canonical style hash for the rendered asset when available. |
render_source | Whether Nimriz rendered from the link's effective saved state or a specific preset-driven request. |
error | Failure reason when a selected link could not be rendered. |
How to queue a bulk QR ZIP
- Go to Links in the dashboard.
- Select one or more links.
- Click the bulk QR action in the toolbar.
- Confirm the PNG export job.
- Open Exports to watch the job move from queued to ready.
Current bulk QR job rules
- The dashboard flow exports PNG assets at 1024px.
- The job stays in the shared Exports history so you can leave the page and return later.
- Partial success is allowed. If at least one QR asset renders, Nimriz still prepares the ZIP and lists failed items in
manifest.json. - Bulk QR ZIP downloads do not create a separate QR inventory. They are snapshots of the QR settings already attached to the selected links.
Async export jobs
Large exports are generated asynchronously. When you trigger a large export:
- Nimriz creates an export job and shows its status in Exports → Recent exports.
- The job runs in the background. You can navigate away and come back.
- When complete, the export shows Ready to download. Click to download the CSV.
- Download links are temporary-they expire after a limited time. Download the file promptly once it is ready.
If an export job fails:
- Check the error message shown in the Exports view.
- Common causes: date range too large (try a shorter range), or a temporary service issue. Retry with a narrower scope.
Export limits and plan considerations
| Consideration | Details |
|---|---|
| Link catalog size | No row limit on catalog exports; very large workspaces may take a few seconds. |
| Analytics date range | The available range depends on your plan's data retention period. |
| Concurrent exports | Only a limited number of export jobs can run simultaneously per workspace. |
| Download expiry | Export files are available to download for a limited time after generation. |
Using exports for integrations
Link catalog exports are useful for:
- Syncing your Nimriz link inventory to external databases or BI tools.
- Auditing your link library (verifying UTM consistency, finding expired links, checking for broken destinations).
- Importing a link list into a spreadsheet for team review.
Analytics exports are useful for:
- Feeding click-level data into your data warehouse or BI tool.
- Attribution analysis combining Nimriz click context with your own conversion data.
- Reconciliation with your web analytics tool at a campaign level.
API-triggered exports
Exports can also be initiated programmatically. The link catalog download is available at:
GET /api/links/export
Authorization: Bearer <WORKSPACE_API_KEY>
For analytics export jobs:
POST /api/exports/jobs
Authorization: Bearer <WORKSPACE_API_KEY>
Content-Type: application/json
{
"type": "analytics",
"date_from": "2026-01-01",
"date_to": "2026-03-31"
}
Poll for job completion:
GET /api/exports/jobs/:job_id
Download when complete:
GET /api/exports/jobs/:job_id/download
For bulk QR ZIP jobs:
POST /api/exports/jobs
Authorization: Bearer <WORKSPACE_API_KEY>
Content-Type: application/json
{
"job_kind": "qr_bulk_download",
"url_ids": [
"22222222-2222-2222-2222-222222222222",
"33333333-3333-3333-3333-333333333333"
],
"image_format": "png",
"image_size": 1024
}
Optional render_source lets automation pin the job to a preset-based render contract instead of each link's effective saved state.
Troubleshooting
The export is missing columns I expected
- Confirm you are using the correct export type. Link catalog exports contain configuration columns; analytics exports contain click-level columns.
- Some columns (like UTM fields) will be blank for links that do not have those fields set.
The analytics export shows different UTM values than the current link settings
This is expected. Analytics exports use click-time UTM values, which are captured at the moment of each click and are immutable. If you edited the link's UTM fields after some clicks, the export reflects the historical values accurately.
The export job failed
Try reducing the date range (e.g., export one month at a time instead of the full year). If the issue persists, contact support with the export job ID visible in the Exports view.
My bulk QR ZIP contains fewer files than I selected
Open manifest.json inside the ZIP. Nimriz allows partial success for QR batch jobs and records the failed link rows there instead of cancelling the entire archive.
I cannot find a previously downloaded export file
Export download links are temporary. If the link has expired, you will need to generate a new export. The export job itself (visible in Exports → Recent exports) shows the job status, but the download file is regenerated on demand.