Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Technology › The Marketing Stack

Backing Up Marketing Tool Data and Settings

How to keep your own copy of what marketing tools hold: which records and settings to copy, where copies live, when to take them and how to restore safely.
Guideintermediate13 min readUpdated

Why the copy inside the tool is not enough

The marketing stack hub asks that every tool have an owner who can log in with administrative rights, knows its connections and holds its contract. A copy held outside the tool is the part of ownership that still works when the login does not. Vendors run and protect their own services under their own terms, and nothing here depends on what those terms say. The risks that matter for this guide sit on the business's side of the account, and there are four of them.

The first is a change the business makes itself. An import set to overwrite on a match, a merge, a bulk edit or a workflow that writes to the wrong field can damage a whole list before anyone notices. The tutorial on importing contact lists is plain that changes an import makes to existing records cannot be reversed by deleting the import, and the diagnosis for CRM values that change back after a sync repairs that kind of damage from an export taken before the load. That repair exists only if somebody took the export.

The second is losing the account. An agency holds the only administrator seat and is slow to hand it over; the one person who could log in leaves; the account is taken over by somebody else. The procedure for a compromised marketing account recovers access through the platform's own route, which is the right first move. Getting the login back is not the same as getting back everything that was changed or removed while the account was out of reach. Where the seat sits with an agency rather than an intruder, the diagnosis for an agency that won't hand over the ad accounts traces why it holds the accounts and how to take them back in order.

The third is the end of a contract. The tutorial on retiring a marketing tool takes its exports while access lasts, before notice runs out, because a closed account takes its records with it. A copy kept all along turns that rush into a check.

The fourth is history that exists only if somebody started keeping it. The BigQuery export guide notes that the export of GA4 events begins the day after the link is made and fills in nothing earlier. Event history in the business's own warehouse starts on the day someone decided it should.

What deserves a copy of its own

A backup of everything is neither possible nor wise. Copy what the business could not rebuild from somewhere else, and the settings that took real work to get right. Start from the list of tools in the stack record and ask of each one which records live only there, and which configuration nobody could recreate from memory.

What to copyWhy the tool's own copy is not enoughWhere the copy comes from
Suppression entriesIf they are lost, opted-out people become reachable from the next import or syncAn export from the tool that holds them, kept with the reason and date
Consent evidence: source, date and wordingWithout it, permissions held in other tools cannot be shownThe form tool or platform that captured the permission
Contact and customer records in the system of recordA damaging bulk change cannot be reversed by deleting itAn export before each bulk change, and on a routine
The tag containerVersion history covers a bad publish, not a lost or overwritten accountAn export of the container as a file
Automations, templates, forms and field definitionsRebuilt from memory, they come back differentThe tool's export where it offers one; otherwise a written record
Lists shared from an agency's manager accountThey belong to the agency that holds that accountA copy kept in the business's own account
Event historyExplorations look back only as far as the property's retention setting allows; the warehouse holds only what was exportedAn export into the business's warehouse

Suppression comes first. A suppression list is the record that keeps people who opted out or objected from being contacted again when their details turn up in a new file. The entry reports the ICO's direct marketing guidance as asking for opt-outs to be honoured promptly, and the email list hygiene SOP turns that into a standing rule: suppress, do not delete. A business that loses its suppression entries cannot honour choices it no longer knows about. Consent evidence comes next: the guide to list building and consent treats exports from one platform to another as acceptable where the consent records move with the contacts, which is only possible if those records exist outside the platform that collected them.

For configuration, the site's analytics guides document one case. The guide to containers and workspaces explains that a GTM container can be saved out as a file, which can later be imported elsewhere, and it recommends that file as the safeguard to take ahead of any sizeable change; the container governance guide puts the same export first in its audit routine. For other tools, check each one's documentation for what it can export and record the answer; this guide does not say what any particular product offers. Where a tool exports nothing useful, a written record is the copy: the integration register already holds each connection's fields, identifier, schedule and checks, which is where the rebuild of a lost sync starts.

Lists held in somebody else's account need their own copy too. The Google Ads guide to manager accounts and access points out that lists shared from an agency's manager account belong to the agency, so the business keeps its own version in an account it owns.

Some things need no separate copy. A report that can be rebuilt from data the business holds, a downstream copy of records whose master lives in the CRM, and anything past its retention period are not worth keeping twice. Copy the system of record rather than every tool it feeds, and the restore has one source of truth rather than several that disagree.

A copy is personal data too

Every backup of contacts, customers or events is another copy of personal data, and the GDPR applies to it as fully as to the original. Its principles, as the site's GDPR entry sets them out, include holding only what the purpose needs, keeping data in identifiable form no longer than necessary and keeping it secure, with the business able to show it complies. A backup taken with good intentions can break all three if it copies every field, sits forever in a shared folder and is opened by whoever finds it.

The guide to retention across marketing tools asks the business to find every copy before setting any period, and backups belong on that list. Three rules keep them inside it. Copy only the fields a restore would need: a suppression backup needs the identifier, the reason and the date, not a full profile. Give each set of copies an expiry drawn from the Retention Period of the records it holds, so that a deletion in the live tool is followed, in time, by the end of the copy that predates it. And record each set in the retention schedule as a copy kept on purpose, with its owner, so that a later reviewer sees it was kept deliberately.

A lost or misplaced backup file is a loss of personal data like any other. Whether such an event needs reporting is for the business's data protection owner to judge, not the person who notices; tell that owner at once.

Where copies live and who can reach them

A copy protects the business only if it survives the event it is meant to cover. That rules out a few tempting places. A copy kept inside the same tool is lost with the account. A copy on someone's laptop, in a personal drive or in a mailbox leaves with that person. A copy in an agency's shared folder belongs, in practice, to the agency. Keep copies in storage the business owns and controls, separate from the tools they protect.

Inside that storage, restrict each set of copies to the named people who would carry out a restore and the owner who answers for them. Add the storage location to the review of who can access your marketing tools, because a folder of exports is a marketing system with personal data in it, and access to it drifts like access to anything else. Label every file with the tool, the date it was taken, what it contains and when it expires, so that a person restoring under pressure can pick the right one without opening every file.

Record the arrangement where the stack is already recorded. The marketing stack management playbook keeps one stack record for every tool, with its owner and deputy; a line for each tool saying what is copied, where, by whom and how restores are tested belongs beside them. A copy nobody knows about is as good as no copy on the day it is needed.

When to take a copy

Some moments call for a copy whatever the routine says, and the routine fills the gaps between them. The distinction between one-way and two-way doors gives the rule for the first moment: before any change that cannot be walked back, keep a way back. The guide to test environments and test data lists deletions, merges and bulk updates of records among its one-way changes: once they run, the earlier state survives only in an export taken beforehand.

MomentWhat to copyWhy then
Before a bulk update, an import that may overwrite, a merge or a deletion runThe records and fields the change touchesThe earlier state is the thing a repair will need
Before a large change to the tag containerThe container, as an exported fileA rebuild from memory differs from what was live
On a routine the owner setsSuppression entries, consent evidence and the system of recordChanges arrive between big events; a stale copy restores stale choices
When an agency or an account owner leavesShared lists, configuration and anything held in their nameOnce access is removed, exports are no longer theirs to give
Before a contract endsEverything the retirement plan keepsA closed account takes its records with it
When a new history startsThe event export into the warehouseHistory is kept only from the day it begins

The routine is the owner's call, set from how fast each record changes and how much of it the business could bear to lose. A suppression list that grows every day needs a tighter routine than a set of form templates that barely changes. Write the routine down with the copy's owner and check, at each access review, that the latest copy is where it should be and has the date it should have.

Handovers deserve a warning of their own. The agency offboarding checklist lists removing access first as a mistake, because an agency that can no longer log in can no longer export reports or transfer accounts. The same order applies to a departing employee: take the copies, transfer ownership, and only then remove the access.

Restoring without undoing later choices

A copy that has never been restored is a hope rather than a backup. Test each kind of copy before it is needed: load it into a test account or workspace where the tool provides one, or, where it does not, open the file and check that the fields, the count of records and the dates are what a restore would require. A test restore that finds a missing column on a quiet afternoon is cheap; finding it on the morning after a bad import is not.

When a real restore is needed, restore as little as possible. Identify the records and fields the damaging change touched, by its batch tag or its date where the change carried one, and put back only those values. Overwriting a whole tool from an older copy throws away every legitimate change made since the copy was taken, from new customers to corrected addresses.

Then protect the choices people have made since the copy was taken. Someone who unsubscribed, objected or asked to be deleted after the copy date must not come back with the restore. Load the current suppression entries before anything else, check the restored records against them and against the log of deletions, and send anything in doubt to whoever owns data protection. The consent map shows which tools hold each permission and how a withdrawal travels between them, which tells you where a restored record could carry an old permission back into the stack.

Watch the connections as well. A restore into one tool can be undone by the next scheduled sync, or carried straight on to every tool that sync feeds. Pause or filter the routes the integration register lists for that tool, restore, check a sample of records, and only then let the syncs run again.

Know what no restore can reach. Messages already sent, data already uploaded to ad platforms and workflow steps that already ran happened outside the copy. A restore puts the records right; anything that left the business on the strength of the wrong records is handled as an incident. Record every restore with the date, the copy used, what was put back and who approved it, so that a later change in the numbers has an explanation.

A mail-order seed company keeps its own copies (illustrative)

Illustrative example — not a real result

Yeldrimon Seeds sets up its copies and uses one

Yeldrimon Seeds, an invented mail-order seed company with a growers' club, sells online and by catalogue. Its stack record lists 14 tools. Asked which records live in only one place, the team finds three: 4,300 suppression entries held only in the email platform, the consent wording for 11,200 subscribers kept only in a form tool it plans to replace, and 2 shared negative keyword lists that sit in its former agency's manager account.

The marketing operations lead sets up a restricted folder in the company's own storage with 3 named people able to open it. The suppression entries are exported weekly with only the address, reason and date; the consent records are exported once in full and attached to the matching contacts before the form tool goes; the negative lists are copied into the company's own account. The CRM's member records are exported before every import or bulk edit, and the tag container before each publish that changes more than a single tag, and the BigQuery export is linked that week, since no earlier event history can be added later. Each set of files carries an expiry taken from the retention schedule, and the schedule gains a line for the folder.

A test restore of the suppression export into a test list shows the file has lost its date column. The export is fixed before anyone relies on it.

Five months later, a catalogue-request file is imported into the CRM with overwrite switched on and resets the club renewal month and the email permission on 1,240 member records. The CRM sync to the email platform is paused, the 1,240 records are restored from the export taken the previous afternoon before the file was loaded, and the restored records are checked against the current suppression list: 3 members who unsubscribed in the hours since the export stay suppressed. A sample of 50 records is checked before the sync resumes, and the restore is logged with the copy used and the approver.

Common mistakes

  • Copying everything. Full exports of every tool multiply personal data without making a restore easier. Copy what cannot be rebuilt, with only the fields a restore needs.
  • Keeping copies with no expiry. A backup older than the retention period holds data the live tools have already deleted. Give every set of copies an end date from the schedule.
  • Storing copies where they disappear. A copy inside the same account, on one person's laptop or in a supplier's folder is lost with the account, the person or the supplier.
  • Taking the copy after the change. An export made after a bad import preserves the damage. Copy before every change that cannot be walked back.
  • Never testing a restore. A file nobody has opened can be empty, truncated or missing the column that matters.
  • Restoring over later choices. An old copy loaded without the current suppression entries brings back people who opted out since. Load suppression first and check against the deletion log.
  • Restoring while the syncs run. The next sync can overwrite the restore or spread it. Pause the routes first.

Frequently asked questions

Is the vendor's own backup not enough?

It protects something different. A vendor's arrangements for its own service are set out in its terms and documentation, and this guide claims nothing about them. Whatever they cover is for the vendor's terms to say, so read them rather than assume. A copy the business holds itself covers what happens inside its own account, such as an import that overwrites the wrong field, and it still exists after access is lost or the contract has ended, as long as someone has checked that it can be restored.

Do backups break our data retention rules?

Not if they are treated as copies like any other. A backup that holds personal data is processing under the GDPR, so it follows the same storage limitation and security principles as the record it copies. Give each set of copies an expiry taken from the retention schedule, list it among the copies the schedule covers, keep only the fields a restore needs, and let whoever owns data protection decide anything the schedule does not settle.

How do we know a backup actually works?

By restoring from it before you need to. Load a copy into a test workspace or a test account where the tool provides one, or open the file and check that the fields, the record count and the dates are what a restore would need. A copy that has never been opened can turn out to be empty, cut short or missing the one column the restore depends on, and the time to find that out is a quiet afternoon rather than the day after a mistake.

Terms used on this page

Frameworks

Where this page is used

Sources

  1. Regulation (EU) 2016/679 (GDPR) — EUR-Lex
  2. Direct marketing guidance — Information Commissioner's Office (UK)
  3. Google Tag Manager Help — Google Tag Manager Help
  4. [GA4] Set up BigQuery Export — Google Analytics Help

Related