After configuring the module settings and default properties for a new container, add a container on the container management page.
Module settings
The parent URI for saving snippet files. Snippet files will be saved to "[uri]/google_tag". Enter a plain stream wrapper with a single trailing slash like "public:/".
If checked, then the JavaScript snippet will be compacted to remove unnecessary whitespace. This is recommended on production sites. Leave unchecked to output a snippet that can be examined using a JavaScript debugger in the browser.
If checked, then each JavaScript snippet will be included as a file. This is recommended. Leave unchecked to inline each snippet into the page. This only applies to data layer and script snippets.
If checked, then the JavaScript snippet files will be created during a cache rebuild. If not checked, any missing snippet files will be created during a page response. NOTE: If Drush commands are run as a user other than the web user, then do NOT enable this setting unless the web user has permission to delete files created by the Drush user.
If checked, then the snippet directory will be deleted during a cache rebuild. If not checked, then manual intervention may be required to tidy up the snippet directory (e.g. remove snippet files for a deleted container).
If checked, then the result of each snippet insertion condition will be shown in the message area. Enable only for development purposes.
The settings that apply to all containers.
The tagging server hostname. Default value is "www.googletagmanager.com". Only change this if the site uses a different tagging server.
The name of the data layer. Default value is "dataLayer". In most cases, use the default.
If checked, then the listed classes will be added to the data layer.
The types of tags, triggers, and variables allowed on a page. Enter one class per line. For more information, refer to the developer documentation.
The types of tags, triggers, and variables forbidden on a page. Enter one class per line.
If checked, then the applicable snippets will include the environment items below. Enable only for development purposes.
The environment ID to use with this website container. To get an environment ID, select Environments, create an environment, then click the "Get Snippet" action. The environment ID and token will be in the snippet.
The authentication token for this environment.
The default container settings that apply to a new container.
On this and the following tabs, specify the conditions on which the GTM JavaScript snippet will either be inserted on or omitted from the page response, thereby enabling or disabling tracking and other analytics. All conditions must be satisfied for the snippet to be inserted. The snippet will be omitted if any condition is not met.
Insert snippet for specific paths
Enter one relative path per line using the "*" character as a wildcard. Example paths are: "/node" for the node page, "/user/*" for each individual user, and "<front>" for the front page.
Insert snippet for specific roles
Selected roles
Insert snippet for specific statuses
Enter one response status per line. For more information, refer to the list of HTTP status codes.
The default snippet insertion conditions that apply to a new container.