Skip to content
UTMCAP

Reliability

Your clicks survive fourteen days of us being down.

A tracker sits between the money you spend and the money you make. The fair question about a young one is what happens when it breaks. This page answers it with what is running today, and ends with what we do not have.

While it is happening

An outage here should not cost you a visitor.

You have already paid the network for the click by the time it reaches us. Losing it because our server is restarting is the one failure a tracker cannot excuse, so the redirect does not depend on our server being awake.

The redirect runs at the edge

Your tracking links are answered on Cloudflare’s network, close to whoever clicked, rather than from one server in one city. Measured across 25 countries this week, half were answered within 37 ms.

One decision engine, two places

The code that decides where a visitor goes is the same code at the edge and on our own server. They cannot drift apart and start sending the same click to different offers.

If our server is down, your links are not

The edge keeps answering redirects, and holds the clicks. It also answers your postbacks, goals and page views itself, then replays each one with the time it really arrived, so a conversion is never dated the moment we came back.

Fourteen days of room

Held clicks and conversions are kept for fourteen days. We would have to be unreachable for two weeks before anything was lost, and an outage that long would be a different kind of problem.

If the worst happens

Backups nobody has restored are not backups.

So ours are restored on a schedule, by a machine, whether or not anything is wrong.

Restore to any minute

The campaign database is archived continuously, so it can be rebuilt as it stood at a chosen minute — the minute before a mistake, not the end of last night.

Clicks copied every fifteen minutes

The click and conversion store is copied to separate object storage every fifteen minutes, with a full copy daily. Losing a server costs at most the last quarter of an hour.

A restore tested every week

Both are restored automatically once a week and the rows counted. A backup nobody has restored is a hope, not a backup. The result is on our own health screen, so a silent failure cannot stay silent.

A second server, warm

A second machine at a different company in a different country keeps a running copy of production and can take over. Promotion is one command and is written down rather than remembered.

Being watched

Checked every minute, from somewhere else.

A monitor that lives on the server it watches goes quiet at exactly the wrong moment. Ours run elsewhere: one on a different network from the app, and a second at a different company again, which alerts even if the first one’s provider is the thing that is down.

status.utmcap.com

Every minute

The app, the edge, the docs and this website, checked from outside.

90 days of history

On the status page, so you can see the pattern rather than the moment.

Two independent alarms

On different networks, so one provider’s outage cannot silence both.

The queue is watched too

Not just "is the site up", but whether held clicks are being delivered.

Your data

Yours, and portable.

One tenant each

Your clicks are yours. Nothing is pooled across customers, and there is no arrangement under which your data could be sold.

Out whenever you want

CSV exports on every plan, the API from Growth up, and your links on your own domains so moving does not mean new creative.

Old clicks age, not vanish

Past your plan’s retention the address is blanked and the row stays, so your history still reports and late conversions still attribute.

Every company that touches your data on our behalf is named in the Data Processing Addendum, with what it does and where it is. The privacy policy says which parts of a click are personal data and for how long.

What we do not have

The part most pages like this leave out.

You can check everything above. These are the gaps, named here so you are not surprised by them later.

Questions

The ones worth asking any tracker.

What happens to my clicks if UTMCAP goes down?
Your tracking links keep working. The redirect is answered at the edge, the click is held, and your visitors reach your offers as usual. Postbacks and page views are answered and held too, then replayed with the time they really arrived. Nothing is lost unless we are unreachable for more than fourteen days.
Where is my data kept?
On servers we run ourselves, in more than one country, with encrypted backups in separate storage. We do not publish which building a server sits in, for the same reason you would not. The companies that host and process data on your behalf are each named in the Data Processing Addendum, which is what matters for your own compliance.
Can I get everything out?
Yes, at any time, on every plan including the free one. Reports and logs export to CSV, and the API gives the same figures from the Growth plan up. Your tracking links run on domains you own, so leaving does not mean reprinting your creative.
What happens to old clicks?
They are anonymised rather than deleted once your plan’s retention passes — the address and the browser string are blanked, the row and its figures stay. Reports from last year keep working, and a late conversion still finds its click. Nothing is anonymised before thirty days, whatever the plan says.
How would I know you were down before my customer did?
The status page is public, and it is written by a checker that runs every minute outside our own servers, so it does not depend on the thing it is watching.

Point a domain at us and run a click through it.

The free plan takes a hundred thousand clicks a month and no card. If it does not do what you need, you have lost twenty minutes.