Tag Manager on mulitple EC2 instances

arno-sim · January 31, 2022, 2:10pm

We have Matomo installed on multiple EC2 instances at AWS. We are also using the Tag Manager withing this installation of Matomo.

We are running into issues where the container JavaScript files are only stored on the instances where the user saves them. So if we have 5 instances we need to update 5 container JavaScript files on 5 different EC2 instances.

Is there any simple way to make this work within Matomo Tag Manager? Else we have to implement something like a EFS mount.

Kind regards,

Arno

arno-sim · February 10, 2022, 2:09pm

I found this report on the github website:

github.com/matomo-org/tag-manager

regenerate-released-containers create wrong MatomoConfiguration variable

opened 10:15PM - 04 Dec 19 UTC

closed 06:34PM - 05 Dec 19 UTC

makarovstas

I have distributed Matomo deployment, and use **./console tagmanager:regenerate-…released-containers** for sync js containers between servers. When I open container_xxx.js, generated by this command, in another server (not where I created initially), I see that **idSite** parameter in **MatomoConfiguration** equals **0**: ``` window.MatomoTagManager.addContainer({ "id": "56xv3rVC", "idsite": 346, "versionName": "", "revision": 0, "environment": "live", "tags": [ { "id": 252, "type": "Matomo", "name": "0e0129bdf61bc36b86fc6f771bf30694", "parameters": { "matomoConfig": { "name": "Matomo Configuration", "type": "MatomoConfiguration", "lookUpTable": [], "defaultValue": "", "parameters": { "matomoUrl": "https:\/\/mysitetracker.com\/", "idSite": 0, "enableLinkTracking": true, "enableCrossDomainLinking": false, "enableDoNotTrack": false, "enableJSErrorTracking": false, "enableHeartBeatTimer": false, "trackAllContentImpressions": false, "trackVisibleContentImpressions": false, "disableCookies": false, "setSecureCookie": false, "cookieDomain": "", "cookiePath": "", "domains": [], "alwaysUseSendBeacon": false, "userId": "", "customDimensions": [], "bundleTracker": true, "registerAsDefaultTracker": true, "jsEndpoint": "piwik.js", "trackingEndpoint": "piwik.php" }, "Variable": "MatomoConfigurationVariable", ........ ....... "variables": [ { "name": "MatomoConfiguration", "type": "MatomoConfiguration", "lookUpTable": [], "defaultValue": "", "parameters": { "matomoUrl": "https:\/\/mysitetracker.com\/", "idSite": 0, "enableLinkTracking": true, "enableCrossDomainLinking": false, "enableDoNotTrack": false, "enableJSErrorTracking": false, "enableHeartBeatTimer": false, "trackAllContentImpressions": false, "trackVisibleContentImpressions": false, "disableCookies": false, "setSecureCookie": false, "cookieDomain": "", "cookiePath": "", "domains": [], "alwaysUseSendBeacon": false, "userId": "", "customDimensions": [], "bundleTracker": true, "registerAsDefaultTracker": true, "jsEndpoint": "piwik.js", "trackingEndpoint": "piwik.php" }, "Variable": "MatomoConfigurationVariable" } ] ``` This problem occurs only for new created sites, if I edit Matomo Tracker variable, save and publish MTM - idSite is normal after regenerate-released-containers

We will test this tomorrow and see if this is the solution.

arno-sim · February 11, 2022, 1:00pm

Just a short update for everyone that is looking at the same problems, the mentioned github link provides the correct solution for us.