Multiple installations of Google Tag Manager detected about angular-google-tag-manager HOT 2 CLOSED

hi @puneetverma05 ,
this library, and google tag manager itself, find their main use in being present in every page of your site/ application, invoking multiple times the "addGtmToDom" method has the multiple instances as a direct consequence . This is clearly a misuse of the library.

I think the main mistake is in this phrase: ": I' don't want to inject GTM on all Pages so not using outside router-outlet" , the ideal use is install the GTM service outside the router outlet so you can have a singleton instance of the library (loaded only one time), the main idea is manage tags effects and triggers INSIDE google tag manager (take a quick look to this and this).
If you need to push specific events inject the gtm service to compnents, an then use it like this.gtmService.pushTag(gtmTag); take a look to my tutorial here

If you handle google tag manager activation directly inside your code you well need to deploy a new version of the application on every logical change of GTM: which is a bad idea and one of the problem that GTM itself fix: you release one time a single instance of GTM scripts and manage specific GTM logics ad settings inside the GTM console without touching your codebase.

from angular-google-tag-manager.

A workaround can be if there is no data in dataLayer we can inject gtmToDom else we can skip?

const dl = this.gtmService.getDataLayer();
      if(!dl.length) {
      this.gtmService.addGtmToDom();
    }

from angular-google-tag-manager.