Skip to main content

Workspace

Where the work lives: links, campaigns, rules, tags, reports and the chat’s conversations. One per client or team. Every page and every assistant action operates inside the workspace you have open, and a member of one workspace sees nothing of another. Sign-up creates your first; owners create more. See Workspaces & organizations.

Organization

What holds the subscription and the workspaces. Billing, custom domains, branding and single sign-on belong to the organization and serve every workspace in it, so an agency pays once and works per client. See Workspaces & organizations and Billing.

Member roles

Every member reads the links, campaigns, rules and reports; a role decides what they may change, and the activity log is the one read kept to admins and owners. A viewer reads only. A member creates and edits links and campaigns. An admin also manages rules, members, domains, branding and client reports, and reads the activity log. An owner does all of that and alone creates workspaces, sets up single sign-on and changes the subscription. See Members and roles.

Rule, convention

The convention is how UTM values must be written in a workspace: the casing, the separator between words, which of the five parameters are mandatory, and whether a breach is blocked or only warned about. With approved values and dependency rules, these are the workspace’s rules; a governed link is one that passed them. See The convention.

Approved value

A closed list of values for one parameter. Once utm_medium has approved values, only those pass; a parameter with none accepts anything the format allows, so you can close one parameter at a time. Retiring the last value opens the parameter again. See Approved values.

Dependency rule

“When utm_source is google, utm_medium must be one of cpc, organic.” It narrows one parameter based on another’s value, and a link carrying the driving value with a pairing outside the list is refused. See Dependency rules.

Campaign

A named group of links, and the name the report uses for them. A campaign also supplies the default utm_campaign for the links under it, derived from its name in your convention’s format, though a link may carry a different one if you say so. See Campaigns.

Short domain

The host a short link is published on. Links use the shared UTMKit domain by default; an organization can connect its own domain and publish from every one of its workspaces, subject to your plan’s allowance on the plans page. See Custom domains.

Token

A personal access token, prefixed utmk_, minted on the API tokens page and shown once. It fixes the workspace it works in and carries only the permissions you ticked, never more than your role allows. It opens the REST API and the MCP server. See Authentication.