Set up Google Analytics via TagManager for the project main domain and subdomains (our gmail)

There is a project for an online game that can be played in a browser, it opens on a subdomain of the main site. There is also a main domain, where there should be N landing pages (currently there is 1) and traffic should be directed (search, social networks, context, QR codes, etc.), there is a registration subdomain, personal account, password recovery, etc. 

https://mlmsimulator.com/ - for landing pages and static pages, this is the main entry point for all traffic

https://my.mlmsimulator.com/ - registration, password recovery, personal accounts

https://play.mlmsimulator.com/ - the game itself (Angular)

This is a newly registered Gmail inbox. Alternative email, phone, everything is ours. 

Accounts:

- Google TagManager

- Google Analytics

are empty. 

Accordingly, for the specified domains, it is necessary to correctly set up structures in Analytics and configure analytics through TagManager, the TagManager code should be provided for placement on the website pages. With a brief instruction that is usually offered by TagManager itself.

Add yourself (your email) to the appropriate working access levels for further work from your email in Analytics and TagManager (Important! Ask clarifying questions if something is not described and add correctly, not blindly to the highest access level. Such actions will indicate that you do not understand the necessary access volumes)

Check whether the code is installed correctly by the programmers, whether the statistics are being collected correctly (clearly indicate from your side after checking in the correspondence: "statistics is being collected correctly, everything is okay." or "not correctly, redo 1, 2, 3, etc.")

If possible, recommend which custom reports should be set up right away. 

The first thing we need is to create a client avatar and have aggregate analytics that we can use to form the avatar. 

Set up tracking of button clicks and have the corresponding custom report for this on the landing page. (The landing page will be multilingual, should all buttons be tagged with the same classes, or is it better to have different classes for each language?) How is it better to organize reporting on these buttons if the landing pages will change?

Set up a goal for registration (note, the landing page is on the domain, registration occurs on the subdomain, after registration the user logs in and the page is no longer publicly accessible (should a public page for successful registration be made?)), so that the steps to achieve the goals are visible considering the buttons clicked on the landing page.

In the old analytics, it was possible to "kind of save the old statistics" before certain changes (I don't remember what it's called, let me know if you don't - I'll find it myself). It is important to see this in the new one and whether it has been transferred to the new statistics?

Recommend an analog of the Orc's web viewer, while it's free. It is important to see how the user behaves, primarily on the landing pages and in the game itself. Personal accounts are in question (if you can recommend something - I would be grateful)

What is expected after completing this work:

- take the pixel from the newly registered fb account and add it through TagManager (check whether the statistics are being collected correctly)

- connect fb to Google Analytics

- set up (consult) on e-commerce, set it up in analytics (it is planned to sell subscription plans)

If you see that there is a reason to do something else - recommend, we will form tasks for the future. 

We are interested in inquiries from Middle, Senior level specialists. Companies, studios, teams do not disturb.