TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

← The field manual

MANUAL · CH.07

How to hand over tracking: accounts, record, test, in that order

Filed

Baris Asa, Synctag, tracking specialist, London · Last checked:

A tracking handover moves three things from the agency, freelancer or analyst leaving to whoever takes over: control of the accounts (Google Tag Manager, GA4, Google Ads, Meta), a written record of what the tags do, and proof that the two match. Five steps, in order: list who owns each account, move ownership to the business (two administrators on logins it controls), freeze the live version, walk through the record together, then let the new owner test it before the old access goes.

The business whose site it is should own every account. Agencies and freelancers get user access on top. Quick check: in Tag Manager open Admin, then User Management; in GA4, Admin, then Account access management; in Google Ads, Admin, then Access and security. If no administrator is a login your business controls, ideally on your company domain, you have access, not ownership.

Your part, as the business: run that check today, then send the person leaving the handover checklist below and ask for steps 1 to 3 back in writing. Steps 3 to 5 are run by the person leaving and the person taking over. Your job is to sit in on the walk-through (step 4) and sign off the close (step 5).

StepWho does itLeaves behind
1. List ownersPerson leavingOwner list
2. Move ownershipPerson leavingBusiness logins, 2 admins
3. FreezePerson leavingExported version, quiet period
4. Walk throughBoth, plus the businessChecked record, unknowns marked
5. Test, then closePerson taking overPassed test, access closed

This chapter is the handover itself. What the written record contains (measurement plan, container map, change log) is on the F-501 page; if no record exists, writing it comes first. Who can write the record or run the handover for you: tracking plan and documentation.

The same steps protect the agency taking over. It starts from a record it has tested, not one it inherited on trust.

Step 1: who owns each account, and who should?

The business should own every account, with two administrators on logins it controls; agencies work through user access. Step 1 lists every account the tracking depends on, and whose login holds admin on it. Do it before anyone gives notice, if you can. Access is easiest to move while everyone is still answering emails.

The usual list for an online store:

  • Google Tag Manager (GTM): which GTM account the container (the file that holds all your tags) sits in, and who is Admin there.
  • GA4: which account the property sits in. Only a GA4 Administrator can add or remove users.
  • Google Ads: the account, and any manager account (an agency’s umbrella account) linked to it. Only an Admin can unlink a manager account.
  • Meta: the business portfolio (Meta’s company account, formerly Business Manager) that owns the pixel or dataset (Meta’s newer name for where the pixel’s data lands), not only the ad account.
  • Google Merchant Center and Google Ads billing: check which business owns each, and whose payments profile pays for the ads.
  • Server container, if there is one: the Google Cloud project and billing account it runs on, or the hosting provider account.
  • Consent platform, the store’s tracking apps, and any BigQuery project.
  • Looker Studio: each data source set to owner’s credentials, which means it pulls data with the login of whoever set it up.

Write one row per account: product, account name or ID, admin logins, and whether each login belongs to the business. Add any admin nobody recognises. A row where every admin is an outside email address is the finding. Often the container was created in the agency’s GTM account when the work began. That’s normal while they run it; at handover it moves.

Step 2: how is ownership moved to the business?

The goal: every account has two administrators with your company’s email, before anything else changes. Tag Manager asks for at least two active administrators. Google Ads says why: with one, you may lose access if that person becomes unavailable.

  • Google Ads: the person leaving adds two business logins as Admin. If the agency manages it through a manager account, the business can unlink that later.
  • GTM, container in the business’s account: add two business logins as account Admin, with Publish (the permission to push changes live) on the container.
  • GTM, container in the agency’s account: Tag Manager’s help pages describe no way to move a container between accounts; the documented route is export and import. Export the live version, create a container in a GTM account the business owns, and import the file. The new container has a new ID, so the snippet on the site is replaced, then tested in step 5.
  • GA4, property in the agency’s account: move it. GA4 can move a property, with its data streams and reporting data, to another account if you hold the Administrator and Editor roles on both. Data-stream settings stay intact, so the tags don’t change, and Google Ads links stay connected. Copy or screenshot the change history you want first: entries from before the move stay with the old account. Choose Replace existing property permissions; with Keep, everyone with account-level access in the agency’s account keeps access to the property. (When a move is blocked: see the questions below.)
  • Meta: check which business portfolio owns the pixel or dataset. If it belongs to the agency and is shared with you, you can use it, but the owner can remove the share. Ask for the highest access level the owner can share. Meta documents sharing, not transfer. If the owning business can’t hand it over, create a dataset in your own portfolio and run it alongside the old one before campaigns switch to it. Generate any Conversions API access token from a system user (a non-person login) in the business’s own portfolio, not from a person’s or the agency’s login.
  • Server container: whoever owns the Google Cloud project and its billing account owns the server. If that is the agency, agree in writing how the project, or a rebuilt container, passes to you.
  • Looker Studio: reports on owner’s credentials keep pulling data as the person who set them up, until that person revokes them. An editor on your side switches each data source to a login the business owns (Data credentials, then Make me the owner).

Step 3: what does freezing the live version mean?

Freezing means two things. Export the GTM version that is live today. Then agree a quiet period: no changes to tags, theme, checkout or consent banner until the handover ends. It’s the same freeze as stage 2 of the tracking audit, for the same reason. A container that moves during the handover can’t be checked against its record.

Two things are handover-specific. First, list work in progress: a half-built event, a test still running, a fault found and not yet fixed. File each known fault under its code from the fault index, so the new owner reads it the same way.

Second, open each workspace (a draft area inside GTM). A workspace can hold changes that were never published. They stay in the container after the person leaves, with nobody left who knows what they were for. Publish them under a named version, or write them down and discard them.

Step 4: what happens in the walk-through?

One session, three people: the person leaving, the person taking over, someone from the business. The business’s job in the room is to say which reports it acts on and to confirm what each conversion is meant to count. Open the live container and the record side by side and go through them tag by tag.

For each tag, the person leaving says what it sends, where, when and why, and the person taking over checks it against the record. Where they differ, the container wins and the record is corrected in the session. Where nobody knows, it goes on record as unknown, to be traced later in Preview mode (GTM’s test view of which tags fire). Don’t guess. A guess written into a record is worse than a gap, because the next person trusts it.

Cover what isn’t in the container:

  • Scheduled jobs: offline conversion uploads, CRM imports, anything that sends data on a timer.
  • Server-side sends: the GA4 Measurement Protocol (events sent to GA4 from a server), the Meta Conversions API (Meta’s server-to-server feed), any server container.
  • Secrets: API secrets and access tokens are passwords that let a server send data into GA4 or Meta without logging in. Anyone who saw one can keep sending data until it’s replaced. Record where each is stored and who can see it, never the secret itself.
  • Reports: which dashboards people actually open, and which number in each one they act on.

If there’s no record to walk through, stop here. The container is F-501 , and the handover becomes writing the record first. A container nobody has ever checked against the store’s orders is also unmeasured, with no baseline: U-001 . End that in the same handover: the test order in step 5 is the first check.

Step 5: how does the new owner prove it works?

The person taking over checks the record alone, while the person leaving can still answer. Two tests:

  • The five-tag test from F-501 : five tags picked at random, each explained from the record alone, without asking the person leaving.
  • One real order, placed and refunded, watched in Tag Assistant (Google’s tool for watching tags fire) and GA4 DebugView (GA4’s live view of incoming events), with each platform receiving what the record says it should. How to run it: stage 4 of the audit chapter. If the container was re-imported in step 2, this is also the test of the new snippet.

If either test fails, the record gets fixed now. When both pass, close in this order:

  1. Downgrade the old access to read-only (Tag Manager container: Read; GA4: Viewer; Google Ads: Read only). In Tag Manager also change their account permission from Admin to User, and in GA4 downgrade at account level as well as property level; an account Admin can grant themselves access again.
  2. Replace the secrets they could see, such as the GA4 Measurement Protocol API secret and the Meta Conversions API access token. Create the new one, update every server, upload and app that uses it, confirm events still arrive, then delete the old one.
  3. Watch conversion counts in each ad platform for one to two weeks: long enough for a weekly upload or scheduled import to run at least once without the old logins. A drop that lines up with the access change points to something that still ran on the old login. Check that first.
  4. Remove the old access and put the date on record in the change log.

The incoming agency gets its own access the same way, from the business’s side: a User on the GTM account with Publish (or Edit) on the container, and GA4 access on the property it works on rather than the whole account.

Handover checklist

  • Owner list: every account, its admin logins, whether each belongs to the business.
  • Two business administrators on GTM, GA4 and Google Ads.
  • GTM container in a business-owned account (moved by export and import if not), snippet replaced and tested.
  • GA4 property in a business-owned account, moved with Replace existing property permissions.
  • Merchant Center and the Google Ads payments profile owned by the business.
  • Meta pixel or dataset owner known; server container’s cloud project and billing owner known.
  • Looker Studio data sources switched to business-owned credentials.
  • Live GTM version exported and stored; quiet period agreed.
  • Workspaces published or cleared; work in progress and known faults on record by code.
  • Walk-through done; unknowns marked, not guessed.
  • Scheduled jobs, server-side sends and where each secret lives, listed.
  • Five-tag test and one test order passed.
  • Old access downgraded to read-only (account level too), secrets replaced without a gap, one to two weeks watched, access removed, date on record.

What if nobody on your side has admin?

Sometimes whoever set it up has moved on and can’t be reached. If they can be reached but steps 1 to 3 aren’t moving, ask for them in writing with a date, and check what the contract says about account ownership. Anyone on your side who is already an Admin can add the business’s logins and start at step 2. If nobody on your side has admin, you can’t take the accounts over.

What you can do is rebuild on accounts you own. If your access to the container lets you export it, export the live version and import it into a new container in your own GTM account. If you don’t, the container map is rebuilt from what the site sends, traced in Tag Assistant and the browser’s network panel. A new GA4 property starts empty. The old data stays in the old property, so keep whatever read access you have for comparison. Then run steps 3 to 5 against the new set-up.

Rebuilding from what the site sends is the tracking plan and documentation work.

Where do handovers usually go wrong?

  • Doing it on the last day. Access is moved in a rush, the walk-through is skipped, and questions come up after nobody is left to answer them.
  • Removing access before the test. The question always comes after the login is gone.
  • Taking user access for ownership. Being added to an account someone else owns is not owning it. Step 1 shows the difference.
  • Forgetting what isn’t in GTM. Server containers, scheduled uploads, store apps and Looker Studio credentials break quietly, weeks later.

Common questions

What should a tracking handover include?

An owner list for every account, admin control on the business’s own logins, an export of the live Google Tag Manager version, the written record (see F-501), known faults and work in progress on record by code, a passed test by the new owner, and the date the old access closed. The full list is in the handover checklist above.

Who should own the Google Tag Manager and GA4 accounts?

The business whose site it is, through logins it controls, with at least two administrators. Agencies and freelancers get user access on top. Google recommends at least two active administrators in Tag Manager, and only a GA4 Administrator can add or remove users.

Can a GTM container or a GA4 property be moved out of an agency’s account?

A GA4 property can: GA4 moves it, with its data streams and reporting data, to another account, if you hold the Administrator and Editor roles on both. Choose Replace existing property permissions, or the agency’s account-level users keep access. The move is blocked for a subproperty, for a property linked to Google Ad Manager until it’s unlinked, and when the destination account is at its property limit (50 by default). A Tag Manager container has no documented move: it is exported and imported into a new container in the business’s own account; the new container has a new ID, so the snippet on the site is replaced and tested.

When should the old agency’s access be removed?

In two stages. When the new owner passes the handover test, downgrade the old access to read-only, at account level as well as container and property level, and replace the API secrets and tokens they could see, switching every sender to the new one before the old one is deleted. After one to two weeks of steady conversion counts, remove the access and put the date on record in the change log.

How long does a tracking handover take?

Steps 1 to 3 are account settings; the waiting is on people answering, not on the settings. Step 4 depends on whether a record exists. If it doesn’t, writing it is the F-501 fix and comes first. Step 5 is an afternoon of testing, then one to two weeks of watching conversions before the old access is removed.

Also filed as

  • tracking handover checklist
  • how to hand over Google Tag Manager to a new agency
  • GTM and GA4 handover
  • taking over tracking from an agency
  • who should own the GTM and GA4 accounts
  • remove old agency access from GA4 and GTM

Faults explained here

Sources

  1. Tag Manager: User permissions (account Admin or User; container No access, Read, Edit, Approve, Publish; make sure there are at least 2 active administrators; recovery route: export the container and import it into a new account; checked 9 Nov 2026)
  2. Tag Manager: Export and import containers (Admin, Export Container, choose a version or workspace; import into a container)
  3. Tag Manager: Versions (every publish records a version; give it a name and description that make the change easy to understand)
  4. Tag Manager: Workspaces (up to 3 in a standard container; a workspace can hold changes that are not yet published)
  5. Analytics: Access and data-restriction management (Administrator can manage users; Editor can't manage users)
  6. Analytics: Move a property (Administrator and Editor roles on both accounts; data streams and reporting data move, data-stream settings intact; Google Ads links remain; subproperties can't move; Ad Manager-linked properties must be unlinked; destination property limit, 50 by default; Keep or Replace existing property permissions; change history before the move stays with the source account; checked 9 Nov 2026)
  7. Google Ads: About access levels (only Admin can give access, change access levels and unlink manager accounts; with one administrator you may lose access if that user becomes unavailable)
  8. Meta for Developers: Sharing a pixel between businesses (the pixel-owning business shares access with set tasks; the owning business can remove the share)
  9. Tag Manager: Server-side tagging on Cloud Run (needs a Google Cloud project and a billing account)
  10. Looker Studio: Data credentials (owner's credentials use the owner's authorisation; data sources keep retrieving data as that person until they revoke; an editor can choose Make me the owner)
WHO RUNS IT

Baris Asa, a London tracking specialist working as Synctag, writes the record and runs the handover for ecommerce brands and the agencies behind them.

Tracking plan and documentation →