Add Google Analytics tracking

[mpoehler]

With use of the Google Tag Manager and the offline capabilities of workbox.

[mpoehler]

In Google Tag Manager we need two different Containers. One normal Web and one AMP. But they share the analytics setting I guess. Maybe there is a way to make that somehow nice? And all settings like GA-TrackingIds should be injected using some kind of .env mechanism.

• [x] Create an Analytics Account
• [x] Create a GTM Account for Testing purposes
• [x] Create an AMP Container in GTM
• [x] Configure AMP Container to use Analytics Account for Pageviews
• [x] Create a WEB Container in GTM
• [x] Configure WEB Container to use Analytics Account for Pageviews
• [x] Add vue-gtm (https://github.com/mib200/vue-gtm) to the project
• [x] add a signin goal
• [x] provide env name as custom dimension, using to filter views
• [ ] enable Workbox analytics
• [ ] test and confirm that offline works

[mpoehler]

https://builtvisible.com/google-analytics-for-pwas-tracking-offline-behaviour-and-more/

[mpoehler]

We should start to think about the .env - we need to integrate the TrackingId during the AMP-Page generation process as well as in the VueJs app. In the VueJs app we should utilize the embedded .env support.

I would suggest to have the following environments:

• production - the final production env
• staging - a production version, but not the final url
• dev - for use during development
• test - for use with testing

When it comes to Google Analytics,

• production - contains the final GA-Tracking Id, with the custom dimension set to "production"
• staging - contains the final GA-Tracking Id, with the custom dimension set to "staging"
• dev - contains the final GA-Tracking Id, with the custom dimension set to "dev"
• test - contains the final GA-Tracking Id, with the custom dimension set to "test"

It is also important, that .env can be overwritten by variables set in the environment. This is important, because all settings in the CI-Build will be set with environment variables.

[mpoehler]

So next steps:

• create a basic .env / .env.staging / .env.dev in root dir
• check if we can add a trackingId and custom dimension in all environment incl. overwritten by env variables.
• ensure that no env variables are checked into the repository
• create .env.example (that can be added to git and contains descriptions for all key/values)