Memo for installing and configuring Google Analytics
The job was useful brief brief on installing Google Analytics. I think it might be interesting :)
Installing Google Analytics Code
1. Subdomain / Cross Domain Tracking - the first step is to determine whether the site is located in several subdomains, and if so, you need to set up the correct tracking between them using the setDomainName () function. Sometimes for tracking subdomains use different profiles with different Google Analytics IDs, but in our opinion it is more convenient to use one profile and appropriately configured filters, which are a little lower.
')
2. Code for search engines - since Google Analytics by default does not understand any Russian search engines other than Yandex, we always add “handlers” of domestic search engines to the tracking code. We use the addOrganic () function.
3. E-Commerce - the module is placed in the event that real transactions are conducted on the site. To install it, you need to change the “Thank you for your purchase” page so that the tracking function fills in the corresponding values ​​for the purchases made.
Check the code on the site
After the client has reported the installation code, you need to check the code for correctness.
1. Typos are a very unpleasant mistake, because in this case Analytics will display the message “code found, data is being collected”. In this case, the data in the account may not appear - it all depends on where exactly a typo was made.
2. Is the code everywhere? Checking the ubiquity of the installation is not so easy if the site is dynamic. You can use the service you want to mark them with utm tags.
GA settings
1. Profile for raw data - it is good practice to create at least two profiles - one for the raw data and the other for using filters.
â—¦ In case of subdomain tracking, you need to create a profile to display the full URL.
â—¦If there are unnecessary parameters in the URL, we make a separate profile in which we get rid of them
2. Setting up an internal search - if the site has a search, it is sure to be configured.
3. Setting goals and checking reexp goals in reports - remember to set up goals. If a regular expression is used for the target, you need to go to the content report and insert it into the filter under the report. This field understands regexps, and with its help it is very easy to check if there is an error.
4. AdWords and Analytics binding - do not forget about AdWords and Analytics binding. You need to go to AdWords on the “Reporting - Google Analytics” tab and check if the link is configured. It is also necessary to check if the auto-tagging is enabled in the “My Account - Settings” tab.
From materials by Timofey Putintsev
Installing Google Analytics Code
1. Subdomain / Cross Domain Tracking - the first step is to determine whether the site is located in several subdomains, and if so, you need to set up the correct tracking between them using the setDomainName () function. Sometimes for tracking subdomains use different profiles with different Google Analytics IDs, but in our opinion it is more convenient to use one profile and appropriately configured filters, which are a little lower.
')
2. Code for search engines - since Google Analytics by default does not understand any Russian search engines other than Yandex, we always add “handlers” of domestic search engines to the tracking code. We use the addOrganic () function.
3. E-Commerce - the module is placed in the event that real transactions are conducted on the site. To install it, you need to change the “Thank you for your purchase” page so that the tracking function fills in the corresponding values ​​for the purchases made.
Check the code on the site
After the client has reported the installation code, you need to check the code for correctness.
1. Typos are a very unpleasant mistake, because in this case Analytics will display the message “code found, data is being collected”. In this case, the data in the account may not appear - it all depends on where exactly a typo was made.
2. Is the code everywhere? Checking the ubiquity of the installation is not so easy if the site is dynamic. You can use the service you want to mark them with utm tags.
GA settings
1. Profile for raw data - it is good practice to create at least two profiles - one for the raw data and the other for using filters.
â—¦ In case of subdomain tracking, you need to create a profile to display the full URL.
â—¦If there are unnecessary parameters in the URL, we make a separate profile in which we get rid of them
2. Setting up an internal search - if the site has a search, it is sure to be configured.
3. Setting goals and checking reexp goals in reports - remember to set up goals. If a regular expression is used for the target, you need to go to the content report and insert it into the filter under the report. This field understands regexps, and with its help it is very easy to check if there is an error.
4. AdWords and Analytics binding - do not forget about AdWords and Analytics binding. You need to go to AdWords on the “Reporting - Google Analytics” tab and check if the link is configured. It is also necessary to check if the auto-tagging is enabled in the “My Account - Settings” tab.
From materials by Timofey Putintsev
Source: https://habr.com/ru/post/92851/
All Articles