google-tag-manager

Overview

Google Tag Manager is a Tag Management System (TMS) that allows you to quickly and easily update measurement codes and related code fragments, collectively known as Tags, on your Website or Mobile App.

Once the small segment of Tag Manager Code has been added to your Project, you can safely and easily deploy Analytics and Measurement Tag Configurations from a Web-Based User Interface.

https://marketingplatform.google.com/about/tag-manager/

Usage

Prerequisites

Helm must be installed first in order to use this Chart.

Please refer to Helm Documentation to get started.

Helm Chart Repository

Once Helm has been set up correctly, add locally the Helm Chart Repository as follows:

helm repo add gtm https://jobtome-labs.github.io/google-tag-manager

If you had already added this Repository earlier, run helm repo update to retrieve the latest versions of this Chart.

You can then run helm search repo gtm to see the Chart.

Install Google Tag Manager Chart

To install the Google Tag Manager Chart:

helm install gtm gtm/google-tag-manager

Uninstall Google Tag Manager Chart

To uninstall the Google Tag Manager Chart:

helm delete gtm

Helm Tests

To run Chart Tests:

helm test gtm

Example Values for GKE

The following Example Helm Values are for a GKE (Google Kubernetes Engine) Context.

In this context, the GKE Ingress Controller is being used, along with Backend/Frontend Configs.

containerConfig: "<your-container-config>"

previewServer:
  replicaCount: 1

  service:
    type: NodePort

  pdb:
    enabled: true

  ingress:
    enabled: true

    annotations:
      kubernetes.io/ingress.class: "<ingress-class>"
      external-dns.alpha.kubernetes.io/hostname: ps.gtm.jobtome.com
      external-dns.alpha.kubernetes.io/ttl: "200"
      cert-manager.io/cluster-issuer: "<cluster-issuer>"
      acme.cert-manager.io/http01-edit-in-place: "true"

    hosts:
      - host: ps.gtm.jobtome.com
        paths:
          - path: /
            pathType: ImplementationSpecific

    tls:
      - secretName: ps-gtm-jobtome-com-tls
        hosts:
          - ps.gtm.jobtome.com

  frontendConfig:
    enabled: true

    redirectToHttps:
      enabled: true

      responseCodeName: MOVED_PERMANENTLY_DEFAULT

  backendConfig:
    enabled: true

    timeoutSec: 30

    healthCheck:
      checkIntervalSec: 5
      timeoutSec: 3
      healthyThreshold: 1
      unhealthyThreshold: 2
      type: HTTP
      requestPath: /healthz
      port: 8080

serverSideTagging:
  previewServerUrl: https://ps.gtm.jobtome.com

  service:
    type: NodePort

  pdb:
    enabled: true

  autoscaling:
    enabled: false

    minReplicas: 3
    maxReplicas: 10

  ingress:
    enabled: true

    annotations:
      kubernetes.io/ingress.class: "<ingress-class>"
      external-dns.alpha.kubernetes.io/hostname: sst.gtm.jobtome.com
      external-dns.alpha.kubernetes.io/ttl: "200"
      cert-manager.io/cluster-issuer: "<cluster-issuer>"
      acme.cert-manager.io/http01-edit-in-place: "true"

    hosts:
      - host: sst.gtm.jobtome.com
        paths:
          - path: /
            pathType: ImplementationSpecific

    tls:
      - secretName: sst-gtm-jobtome-com-tls
        hosts:
          - sst.gtm.jobtome.com

  frontendConfig:
    enabled: true

    redirectToHttps:
      enabled: true

      responseCodeName: MOVED_PERMANENTLY_DEFAULT

  backendConfig:
    enabled: true

    timeoutSec: 30

    healthCheck:
      checkIntervalSec: 5
      timeoutSec: 3
      healthyThreshold: 1
      unhealthyThreshold: 2
      type: HTTP
      requestPath: /healthz
      port: 8080

In addition, you can enable NEGs.

  service:
    neg:
      enabled: true