The Person Who Set Up the Tracking Left, and Now Nobody Can Fix It

Every tracking asset your clients depend on is owned by an account, and every account belongs to somebody. A pixel sits inside a business portfolio. A container belongs to a Google account. A property has a list of administrators with names on it. For as long as those people are reachable and cooperative, none of this matters at all. The day one of them is not, a five minute fix becomes a six week recovery, or simply becomes impossible.

This is not a tracking bug. There is nothing misconfigured, nothing firing on the wrong trigger, no tag to repair. It is a structural problem that sits underneath all of those, and it determines whether you can act on anything you find. Monitoring that tells you a tag broke is worth very little if you cannot get into the container to fix it.

The shapes this takes

Almost every agency has at least one of these in their portfolio right now, usually without knowing which client it is.

The pixel in somebody’s personal business portfolio

A freelancer set up Meta tracking four years ago. They created the pixel under their own business portfolio because that was the account they were logged into, and they shared access with the client. The data has flowed ever since. The client has never owned the asset producing it, and in many cases does not know that is possible.

The container owned by a developer’s personal Google account

A tag manager container created under a personal Gmail address, with the agency and client added as users. It works identically to a properly owned container until the person who created it stops responding to email, at which point the account with the highest level of control is unreachable.

Access you have, ownership you do not

This is the most common and the most deceptive. You have access to the Google Ads account and can do your job every day, but your access level does not let you grant access to anyone else, change who owns it, or recover it if the holder disappears. Google Ads manager accounts have distinct levels of user access, and linking a manager account does not by itself make you the administrative owner of a client account. Plenty of agencies discover the distinction at precisely the wrong moment.

Domain verification held by a party you do not control

Domain verification, the thing that governs who is allowed to configure events for a website, can sit with a business portfolio that is not the client’s and not yours. Everything works until you need to change event configuration and find that the right to do so belongs elsewhere.

Why it stays invisible

Because nothing about ownership affects data collection. A pixel owned by a stranger fires exactly as well as a pixel owned by the client. The events arrive, the reporting populates, the campaigns optimise. There is no warning, no degraded state, and no screen anywhere that says “you will not be able to fix this later.”

The bill arrives on a specific day, and it is always one of these:

• The client switches agencies, and the outgoing agency is slow, unhelpful, or simply disorganised about handover.
• An employee leaves. Their account is deactivated by IT, and it turns out they were the only administrator of something important.
• A freelancer moves on, changes their email, or stops replying.
• Something breaks and needs an urgent change, and the person who can approve it is on another continent or no longer in the industry.

Notice that four out of four are personnel events, not technical ones. This risk is created by how people join and leave, which is why it never shows up in a technical audit.

Auditing it, client by client

This takes about twenty minutes per client and is worth scheduling once a year, plus every single time you onboard. For each client, write down the answer to one question per asset: who is the owner, by name?

1. Meta business portfolio.Who are the admins? Is the client one of them? Is any admin an individual outside both your agency and the client’s company?
2. The pixel or dataset. Which business portfolio owns it? Owning the ad account and owning the dataset are two different things, and they are regularly held by different parties.
3. Google Ads. Who holds administrative access on the account itself, as opposed to access granted through your manager account? Confirm at least one administrator is somebody at the client.
4. Tag manager container. List the users with publish rights. Check whether any is a personal address rather than a company one.
5. Analytics property. Same question, and check the property is in an account the client controls.
6. Domain verification. Which portfolio verified the domain?

Two red flags to look for as you go. First, any asset with exactly one administrator, whoever it is, because one administrator is a single point of failure with a holiday schedule. Second, any administrator who is an individual rather than a company, because individuals change jobs and companies tend not to vanish overnight.

What good looks like

The target state is simple to describe and politically awkward to implement.

• The client’s company owns every asset. The pixel, the ad account, the container, the property, the domain verification. All of it sits in a business entity the client controls and would keep if every supplier they have disappeared tomorrow.
• Your agency has access, not ownership. You are granted the access you need through a partner or manager relationship. When the relationship ends you are removed cleanly, and nothing of theirs leaves with you.
• At least two administrators on everything, one of whom works at the client.
• No personal accounts anywhere. Company addresses only, on both sides.
• Written down. One page per client listing each asset, its identifier, its owner, and its administrators. This document is the entire deliverable, and it is worth more than it looks.

The conversation nobody enjoys

Some agencies hold client assets deliberately, because it makes leaving harder. It is worth being honest that this is the reason it persists, and equally honest about why it is a bad trade.

It makes you responsible for assets you do not want liability for. It guarantees a painful, reputation-damaging exit whenever a client does leave, and clients talk to each other. And it fails on its own terms, because a client who feels held hostage is a client looking for a reason to go. The agencies that hand over ownership cleanly and compete on the work tend to keep clients longer, and they sleep better.

Raising it with a new client is easier than it sounds, because the framing is protective rather than procedural: you are making sure that if anything ever happens to your agency, their tracking is still theirs. No reasonable client argues with that.

The day one checklist

Ownership is enormously easier to establish during onboarding than to retrofit two years in, because at onboarding everybody is cooperative and nobody has anything to lose. Build it into your kickoff as a standard step rather than treating it as a special request.

1. Ask who built the current tracking, and whether that person or company is still involved. The answer tells you most of what you need to know.
2. Have the client confirm, in their own account, that they hold admin on the business portfolio, the ad accounts, and the analytics property.
3. Request access through a manager or partner relationship rather than being added as an individual user, so your access survives your own staff changes.
4. Add a second administrator on anything that has only one, before you touch any campaign work.
5. Record the asset identifiers. Pixel IDs, container IDs, measurement IDs, customer IDs. Write them in the client file, not in somebody’s inbox.

The whole exercise takes under an hour per client and it is the single cheapest insurance policy in the entire relationship. It also doubles as a quiet competence signal, because most agencies never ask.

What to do when you have already lost it

If an asset is stranded with somebody unreachable, your options are limited and none of them are fast. Both Meta and Google have processes for claiming or recovering assets, they require documentation, and they take time. Start them early rather than waiting for a crisis.

Sometimes the honest answer is to rebuild. A new container, a new property, a new dataset, owned correctly this time. It costs you historical continuity, which is a genuine loss, and it ends the problem permanently. Make that decision deliberately and with the client, rather than discovering it is the only option during an outage.

Why this belongs in a tracking conversation

Because it determines your response time to every other problem in this blog. A conversion tag firing on the wrong trigger is a ten minute fix if you can publish the container, and an open-ended negotiation if you cannot. Detection and the ability to act are two different things, and most agencies only invest in the first.

If you want to see what is actually installed on a client site before you go asking who owns it, our free tracking scan reads the public source and the published container in about thirty seconds and lists every pixel, tag and container with its real identifier. That list is a useful starting point for an ownership audit, because you cannot ask who owns an asset you did not know existed. What it cannot tell you is who controls them, since ownership lives inside the platforms rather than on the website.

Once ownership is sorted out and you can actually act, Taglert rechecks every connected account every thirty minutes and emails you the day tracking changes, which is the half of the problem that can be automated.