Skip to main content
Three things leave UTMKit as a file: the links of a workspace, the findings of a finished audit, and the activity log. All three are CSV. This page covers the first two; the activity export is described in Activity log. They open cleanly in Excel and Google Sheets, keep accents and commas intact, and are safe from cells a spreadsheet would run as a formula. Every role can export what it can already see on the page, viewers included. Exports are console-only; there is nothing to export through the API or the MCP. On the links list, choose Export CSV. The file contains every link the current search selects — not the page you were looking at — and the search travels in the file name, so a narrowed file cannot be mistaken for the whole workspace. A search that matches nothing still produces a file with its header row. One row per link, with these columns in this order.
  • short_url — the short link as people see it.
  • destination — the address you gave, before the UTMs were added.
  • destination_with_utm — the address the visitor actually reaches, UTMs applied.
  • utm_source, utm_medium, utm_campaign, utm_term, utm_content — the link’s UTM values, one per column.
  • campaign — the campaign the link belongs to, if any.
  • tags — the link’s tags, comma-separated.
  • note — the free-text note on the link.
  • state — whether the link answers at the edge: Live, Not live yet, Withdrawn, Expired, or Stopped — subscription ended.
  • destination_status — what the daily destination check last got: a status code or a failure word; empty for a link never checked yet.
  • ga4_channel_problem — the UTM parameter names, if any, whose values would keep Google Analytics 4 from filing the link under a proper channel; empty when there is none.
  • clicks_last_N_days — counted visits in the recent window the links list shows. N is written out in the header with the real number of days your plan covers. Empty, never zero, while reports are paused for the plan’s allowance.
  • created_at — the day the link was created.

​
The audit file

On a finished audit’s page (https://app.utmkit.co/audits/…), choose Export CSV. An audit still running has nothing to export, and the page says so. The file is a worklist: one row per thing to fix. The score and the coverage statement stay on the page. Two kinds of row share the columns, told apart by the first one.
  • kind — violation for a value that broke a rule, spelling_group for one spelling in a cluster the audit judged to mean the same thing.
  • parameter — which UTM parameter.
  • value — the value found; empty when the rule is about a missing parameter.
  • rule — the rule that fired; empty on spelling rows, where no rule did.
  • explanation — the sentence the audit page prints for that finding; empty on spelling rows.
  • links_affected — how many of the workspace’s links carry it.
  • imported_affected — how many of the imported URLs carry it, on violation rows.
  • suggested_value — the spelling the audit proposes for a cluster. A proposal, not a decision.
  • suggestion_passes_convention — whether that proposal would itself pass the workspace’s convention.
  • accepted, accepted_by, accepted_on, acceptance_note — whether somebody accepted the finding, who, when, and what they wrote.