Tracing a wrong post or setting back to the person who made it

After a post goes out by mistake or a setting is changed by error, the client will want to know what happened. It will also want to know who did it and when. Whether you can answer was settled before the mistake, by how your staff get into the account. The options are laid out in managing client accounts at an agency.

The three facts a report needs

A report to the client needs three facts: who, when and what. What happened is the mistake itself, and you need it to delete the post or undo the setting. When decides how far the damage reaches, such as how long the post was public or how many days ads ran on the wrong budget. Who lets you aim the fix at the actual cause.

Why a shared login can’t name the person

A shared login can’t narrow things down to one person because platforms record activity by login. They log which user signed in and what that user changed. Here a user means the login, not the person using it. Google Ads, for example, shows the email address behind each change made in its interface. If three people use one login, the platform’s history shows one user, and all it can tell you is that one of the three did it.

Some platforms also record when and where a sign-in came from. Shopify, for example, keeps each user’s recent sign-ins with IP address and location. That can’t separate staff who work from the same office during the same hours. If remote staff connect from different places, the location is a clue, not proof of who it was. How long each platform keeps its change history is compared in reporting your work in client accounts to the client.

What delegated access and access tools record

Here is how much of the three facts each way of getting in leaves on record. An access tool here means software that signs staff in to a shared login without showing the password and records who used it.

With delegated access, the platform keeps the record. As long as each person signs in with their own invited account, the platform records who. Meta Ads Manager, for example, shows the name of each person with an admin or advertiser role next to their changes. But if one invited account is used by several people, the record is no better than a shared login. What is delegated access? explains why each person needs their own invitation.

With an access tool, the platform still records the shared login. The tool adds its own record one step earlier, listing which person opened which account and when. Match the platform’s change history against the tool’s record by time, and you can narrow it to one person. If several people had the same account open at the same time, matching can’t pick one.

Without records: what to use instead, and its limits

Without a per-person record on a shared login, you have task records, shift schedules and interviews. Task records include the posting calendar, ad upload requests and approval history. Compare who was on posting duty at the time of the mistake with who was working, then confirm with that person.

This method has limits. The result is an estimate, so if the person doesn’t recall it, you can’t confirm it. If several people worked on the same account in the same hours, shift schedules don’t narrow it down. And interviews rely on memory, which gets less reliable the longer it has been since the mistake. When you report to the client, say that the result is an estimate and name what you couldn’t confirm. An estimate reported as fact and later overturned can cost you more of the client’s trust than the mistake itself.

How records help prevent a repeat

Records matter for prevention because they tell you which kind of cause you are dealing with. A wrong setting might come from one person missing something, from a missing review step, or from a person having permissions the job didn’t need. Each has a different fix. A missed detail calls for a second check. A missing step calls for an approval. Too much permission calls for narrower roles.

Without knowing who made the change, you can’t tell these apart. A fix with no known cause has nowhere to aim, so it ends up as a reminder to everyone, and the conditions behind the mistake stay the same.

You can’t add records after the fact. So when you take on a client account, write down where “who” will be recorded for that account, and add it to your list of client accounts.