UTMCPdocs
Open the app →

Your account

Two roles and what separates them, the six things under Settings, and where the API key lives.

#People

Two roles, and the difference is narrow on purpose:

Role Can
Admin Everything, including inviting people and acting on pending invitations
Member See who they work with, and change nothing about the team

A member sees the people list. Only an admin sees pending invitations, because an admin is the only one who can act on them — showing a list to someone who cannot do anything with it is a screen that only raises questions.

Everything in the product has been scoped by organisation from the start, so adding a person changes who can reach the data rather than creating a second copy of anything.

#Settings

Six tabs:

Tab For
Profile Who you are
General Account-wide preferences
Notifications Which emails you get
Security Your password, and the devices signed in
API Your key
Billing Plan, invoices, payment

Security is worth opening once even if nothing is wrong. The signed-in devices list is the only place a session you do not recognise becomes visible, and ending one there is immediate.

#The API key

Under Settings → API. It is the credential for reading your own data programmatically, and it carries the same access your account has.

Treat it as a password: it belongs in a secrets store, not in a spreadsheet, a shared document, or a repository. If one has been somewhere it should not, replace it rather than hoping.

It is not the tracking tag's site key, which is a public value that appears in the source of every page carrying the tag and is meant to.

#Billing

Plan and invoices are under Settings → Billing.

Plan limits are enforced on the click path, and the counter reconciles rather than being exact to the click — so a figure that lags slightly behind a report is not a bug.

Invoices are issued automatically on renewal and emailed as PDFs, on paid plans and free ones alike.

Refunds are within 14 days, and crypto payments are not refundable — stated here because it is the kind of thing worth knowing before paying rather than after.

#Getting help

The Support screen gathers what a first message needs: which install, which domain, what time, what was on screen — in a block you can copy.

Most of the delay in getting help is the round trip spent asking those, and half of it is knowable from that page. Send it with the campaign alias, and if it is a landing page problem, the exact address a visitor reaches.