Updating

Updates run from the dashboard. Settings → System checks for a newer release and installs it.

Your data isn’t touched — clicks, conversions, campaigns and landers all carry across. Only the application itself is replaced.

What you’ll see

The dashboard goes briefly unavailable while the update applies, and a live log runs on the same screen so you can watch it. Don’t reload or intervene while it’s running. It’ll come back on its own.

Tracking keeps running throughout. Clicks and conversions are still recorded while the dashboard is restarting.

Before you update

Ask for a backup first — message @roitrack on Telegram. Updates are routine, but a snapshot turns a bad update from a problem into an inconvenience. See Backups.

Your version

Shown in Settings → System.

Updates need a valid licence

Update files come through the licence server, which checks your key first. An expired or revoked licence blocks updates, though your tracking keeps running.

Installing doesn’t need a key — you install first and activate second — but updating does. Check Settings → Licence and the portal.

When an update fails

“No licence key” — set it in Settings → Licence.

Licence server unreachable — either your server can’t reach the internet, or the licence is expired or revoked. Check the portal first.

Still on the old version afterwards — check the log on Settings → System. If it doesn’t explain itself, send us a screenshot.

Dashboard doesn’t come back — give it two or three minutes; container restarts aren’t instant. If it’s still down after that, message @roitrack. Include what version you were updating from and to. Your tracking is almost certainly still running.

Rolling back

Possible, but not something to do on instinct. Some updates change how data is stored, and going back isn’t always a straight reverse — sometimes restoring the pre-update backup is the cleaner fix.

Get in touch and we’ll work out which applies to your case and do it with you.