Exports

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 report export: a reporting CSV generated from stored analytics rollups and attribution facts. It uses click-time attribution data where available, not the link's current UTM state.

The Exports area also tracks async bulk QR ZIP jobs, including link QR, static QR, and Retail & GS1 generated asset exports. 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:

How to export the link catalog

1. Go to the main Links view in your dashboard.
2. Optionally apply filters (by space, tag, domain, status) to limit the export to a specific subset.
3. Click the Export button in the toolbar.
4. Select Link catalog as the export type.
5. 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 report export

What it contains

An analytics report export produces a CSV file with one row per reporting group within the date range you specify. It is designed for campaign reporting, reconciliation, and BI import, not as a raw clickstream export. Columns can include:

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.

Hosted-page and card engagement metadata, such as block ids, file ids, providers, and target hosts, is available in analytics drilldowns where supported. Bulk analytics report exports keep event naming canonical and do not include full outbound URLs, lead values, RSVP identity values, raw IPs, full User-Agent values, visitor hashes, raw nim_ct, raw external click IDs, or full referrer URLs.

Conversion exports use the same async export system. They may include touch_id, touch_time, click-time UTM fields, sanitized destination snapshots, order/event identifiers, and variant or experiment identifiers needed for attribution reconciliation.

How to generate an analytics export

1. Go to Exports in the dashboard navigation.
2. Click New export.
3. Select Analytics export as the export type.
4. Set the date range. Exports are available for any range within your plan's data retention period.
5. Optionally filter by domain, space, or tags.
6. 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.json file describing every requested link, whether it succeeded or failed, and which render source Nimriz used.

What manifest.json contains

Each result row can include:

How to queue a bulk QR ZIP

1. Go to Links in the dashboard.
2. Select one or more links.
3. Click the bulk QR action in the toolbar.
4. Confirm the PNG export job.
5. 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.

---

Retail & GS1 ZIP jobs

Retail & GS1 generated assets can be exported from QR Codes → Retail & GS1. Select one or more generated GS1 QR or GS1 DataMatrix assets, choose whether to include validation reports, and queue the ZIP export.

Each Retail & GS1 ZIP includes a manifest.json with generated code ids, product and GTIN context, canonical URI, symbology, validation status, and per-item render status. Validation reports, when included, are stored as JSON files under validation-reports/.

---

Async export jobs

Large exports are generated asynchronously. When you trigger a large export:

1. Nimriz creates an export job and shows its status in Exports → Recent exports.
2. The job runs in the background. You can navigate away and come back.
3. When complete, the export shows Ready to download. Click to download the CSV.
4. 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

---

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 reporting 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

{
  "dataset": "clicks",
  "format": "csv",
  "range_start": "2026-01-01",
  "range_end": "2026-03-31",
  "include_bots": false
}

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.

For Retail & GS1 bulk ZIP jobs:

POST /api/exports/jobs
Authorization: Bearer <WORKSPACE_API_KEY>
Content-Type: application/json

{
  "job_kind": "qr_bulk_download",
  "qr_source": "gs1_retail",
  "gs1_generated_code_ids": [
    "44444444-4444-4444-4444-444444444444",
    "55555555-5555-5555-5555-555555555555"
  ],
  "include_validation_reports": true
}

---

Troubleshooting

The export is missing columns I expected

• Confirm you are using the correct export type. Link catalog exports contain configuration columns; analytics report exports contain reporting 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.

---

Related guides

• Analytics and privacy
• Spaces and tags
• UTM parameters
• Integration patterns