Skip to content
All guides

Business tools

Buy a Separate Yandex Account to Hold Client Metrica Tags?

Whether a bought Yandex account should create a client's Metrica tag or only be invited to it depends on how the engagement ends. Guest access levels and the transfer option point to a clear rule.

Contents

Where client analytics should live

A marketing team that sets up web analytics for clients soon meets a custody question. If each client's Yandex Metrica tag is created under someone's personal Yandex ID, a private login ends up holding other people's business data, and handing it over later gets awkward. A Yandex account bought for client analytics keeps that data away from personal mail and files.

Whether the separate account should hold the tag, or only be invited to a tag the client holds, depends on how the engagement will end. Metrica's access options make the difference concrete.

How Metrica shares a tag

Metrica Help describes individual access granted by username under Settings and Access. A View user sees the tag's settings and statistics and can save reports, but cannot manage access, goals or segments. A Can edit user fully manages the tag but cannot delete it or move it to another account. Anyone reading statistics this way must be registered and logged in to Yandex, so every colleague or client who reads reports needs a Yandex login of their own.

Two further mechanisms shape the decision. An account owner can add representatives, who get full rights to view, edit and delete any tag in that account, including guest tags. And a tag's owner can transfer it to another account from the tag settings. If you are not the owner, Help describes a different route: confirm your right to manage the site in Yandex Webmaster and submit a transfer form, which works only when the tag tracks that confirmed site alone.

Two clients, two different answers

Hypothetical: a two-person team works for a neighbourhood bakery and a dental clinic. The bakery has no Yandex ID and expects to receive its analytics when a six-month contract ends. The clinic's manager already has a Yandex login and wants to stay the owner of everything, reading reports but leaving the setup to the team.

For the bakery, the team creates the tag in an account bought for that client. When the contract ends, the bakery signs up for its own login and the team uses Transfer to another account, so the history moves with the tag and the team's account keeps nothing it should not. For the clinic, the manager's login creates the tag and adds the team's bought account with Can edit. When that work ends, the clinic removes the guest access and nothing needs to move.

Both bought accounts are useful, but they do different jobs. One holds a tag until a planned transfer; the other is only a working login that receives access.

A handover routine for a held tag

When a bought account holds a client's tag, decide the handover at the start rather than at the end. Write down which account holds which tag, who keeps its password and phone, and the date the contract ends. Give the client View access on their own login as soon as they have one, so during the contract they already read the same reports they will own afterwards.

At the end, the owner's transfer moves the tag out of your account. If the client has instead taken over the site's rights in Webmaster first, the transfer form described in Help is their route, provided the tag tracks only that site. Either way, remove remaining guest access and representatives afterwards, so the emptied account keeps no leftover rights to the client's data.

Why representatives deserve caution

Representative access is convenient because it reaches every tag in an account at once. That breadth is also the risk: a representative can delete tags, including guest tags. If you keep several clients in one account and add a freelancer as a representative, you expose all of them with a single grant.

The same logic argues against holding many clients' tags in one bought account. One account per client means more logins to look after, but each transfer, revocation and handover then stays independent, which matters most when contracts end at different times.

Fit and not-fit conditions

A separate bought account fits when you will create tags that clients may later receive, when your team wants analytics apart from personal Yandex IDs, or when the client has no login yet. It is less necessary when the client already owns the tag and only needs to invite you; any Yandex login you control can then accept Can edit access, including one bought for that project.

It does not fit when you cannot make the account fully yours. Before relying on it, replace the password, the phone number and the recovery details. Yandex's user agreement makes the account holder answerable for all activity under the login and bars reselling access to Yandex services without Yandex's authorization. Holding an account bought on rStock means using it under those terms; nothing in the purchase grants a permission Yandex has not given.

Choosing an analytics account on rStock

rStock operates independently of Yandex, as a marketplace where approved stores list accounts. For analytics custody, read Yandex listings for a clean account with no earlier use, a replaceable phone number, recovery details you receive and a clear statement of prior history. Compare the store's rating, reviews and insurance balance alongside the description, keeping in mind that those signals describe the store rather than your future use of the account.

Payment comes from your rStock balance, and the account appears as a delivery record on your order page; check it within the dispute window shown there. Then open the Yandex category and choose a quantity that matches the number of clients whose tags you plan to hold, not a round number.

Frequently asked questions: Buy a Separate Yandex Account to Hold Client Metrica Tags?

Keep reading