Backups

Your tracker holds two things you can’t rebuild: your setup, and your history. Campaigns, flows, offers, landers and domains on one side; every click, lander view and conversion on the other.

What a backup contains

Part	What’s in it
Configuration	Campaigns, flows, offers, landers, domains, users, traffic sources, networks
History	Every click, lander view and conversion
Settings	Your keys and passwords, so a restored server comes back as itself

Uploaded lander files are stored separately and need to be included explicitly. If you host landers on the tracker rather than linking to them, mention it when you set backups up.

Setting up backups

Backups aren’t switched on by default, because where they should go is your call — the same server is the one place they shouldn’t live.

Message @roitrack on Telegram and we’ll set them up with you. It takes a few minutes. Worth deciding first:

How often. Nightly suits most people. Heavy spenders often want more.
Where they go. Your provider’s snapshots, another server, or object storage. Anywhere that isn’t the tracker itself.
How long you keep them. Two weeks is a sensible default.

Restoring

Get in touch and we’ll do it with you. Have ready:

The backup you want to restore and roughly when it was taken
Whether the original server still exists. If it does, don’t destroy it — it’s the fallback.
Whether you need the licence moved. Restoring onto a new server means unpinning first, and we’ll handle that in the same conversation. See IP pin & migrating VPS.

Message us before starting anything yourself. Restores are the one operation where a hasty first attempt can take the second attempt away from you.

Before anything risky

Ask for a backup before you update, migrate, or make a change you’re unsure about. It costs a couple of minutes and it’s the difference between an inconvenience and a bad week.

Related: Updating · Migrating to a new VPS