How to use Google Analytics 4

richard2022 · December 14, 2022, 8:27am

We are using google universal analytics and it is scheduled to end in 2023/07.
We are considering switching to google analytics 4.
In google analytics 4, the script is supposed to be written in the section.
Is it possible to add the script description to the section of jitsi meet web?
If not, is it possible for you to consider adding it in the future?

damencho · December 14, 2022, 12:13pm

You can use base.html file to add it there on your deployment

github.com

jitsi/jitsi-meet/blob/f5ac1b62713f97648ecf8554ca2d9a42b463d558/index.html#L8


      
          <html itemscope itemtype="http://schema.org/Product" prefix="og: http://ogp.me/ns#" xmlns="http://www.w3.org/1999/html">
            <head>
              <!--#include virtual="head.html" -->
              <meta charset="utf-8">
              <meta http-equiv="content-type" content="text/html;charset=utf-8">
              <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0">
              <meta name="theme-color" content="#2A3A4B">
              <!--#include virtual="base.html" -->
          
          
    <link rel="apple-touch-icon" href="images/apple-touch-icon.png">
              <link rel="stylesheet" href="css/all.css">
              <!--#include virtual="fonts.html"-->
              <link rel="manifest" id="manifest-placeholder">
          
          
    <script>
                  window.EXCALIDRAW_ASSET_PATH = 'libs/';
                  // Dynamically generate the manifest location URL. It must be served from the document origin, and we may have
                  // the base pointing to the CDN. This way we can generate a full URL which will bypass the base.

richard2022 · December 22, 2022, 2:42am

Dear damencho.

I wrote to the head section in “/usr/share/jitsi-meet/index.html” and it worked fine.

Thank you very much.

damencho · December 23, 2022, 7:54am

Don’t forget to re-add it after update.

You can always put a file base.html in /etc/jitsi/meet folder with that and add an nginx rule to point to it similar to this:

github.com

jitsi/jitsi-meet/blob/77e02a09946ace8600ad68d3617e1b6e39be40b1/doc/debian/jitsi-meet/jitsi-meet.example#L80


      
          
          
index index.html index.htm;
          error_page 404 /static/404.html;
          
          
gzip on;
          gzip_types text/plain text/css application/javascript application/json image/x-icon application/octet-stream application/wasm;
          gzip_vary on;
          gzip_proxied no-cache no-store private expired auth;
          gzip_min_length 512;
          
          
location = /config.js {
              alias /etc/jitsi/meet/jitsi-meet.example.com-config.js;
          }
          
          
location = /external_api.js {
              alias /usr/share/jitsi-meet/libs/external_api.min.js;
          }
          
          
location = /_api/room-info {
              proxy_pass http://prosody/room-info?prefix=$prefix&$args;
              proxy_http_version 1.1;

This way your changes will survive updates.