A recent update to Google Tag Manager<\/a> introduced container notifications<\/strong>.<\/p>\n By subscribing to container notifications, your Google Tag Manager login email address can be configured to receive an email for some of the key workflows in Google Tag Manager: containers getting published, and containers being submitted for approval<\/a> (Tag Manager 360 only), for example.<\/p>\n Be sure to check out the official help center article<\/a> about container notifications.<\/p>\n In this article, I\u2019ll walk you through the feature and share a couple of tips on how to make it even more useful!<\/p>\n \n \n Subscribe to the Simmer newsletter<\/a> to get the latest news and content from Simo Ahava into your email inbox!\n <\/p>\n <\/span><\/p>\n <\/p>\n <\/a><\/p>\n<\/div>\n You\u2019ll find container notifications for an individual container under Admin<\/strong>:<\/p>\n <\/p>\n <\/a><\/p>\n<\/div>\n You can also set default<\/strong> notification settings in your User Settings<\/strong><\/a>.<\/p>\n Click the overflow menu<\/strong> in the top-right corner of the GTM UI (the menu with the three vertical dots) and choose User Settings<\/strong>. Scroll down to the Default Container Notifications<\/strong>. Whatever you set here will be on by default in all the containers you manage.<\/p>\n <\/p>\n <\/a><\/p>\n<\/div>\n When you set Default Container Notifications<\/strong>, they will apply to all containers you have access to until you go to each individual container, change the value of a notification setting, and Save<\/strong> it.<\/p>\n A bit confusingly, the settings for an individual container do not tell you whether or not the current settings override<\/em> or inherit<\/em> the default container notification setting.<\/p>\n<\/blockquote>\n To receive an email notification, you can configure the following events to trigger one:<\/p>\n The Always<\/strong> option sends an email whenever a version is published into any<\/em> environment<\/a>.<\/p>\n The Live Environment only<\/strong> option sends an email only when a version is published into the live environment.<\/p>\n The Always<\/strong> option sends an email whenever a container version is created (but not published).<\/p>\n Tag Manager 360 only.<\/p>\n<\/blockquote>\n When an approval request<\/a> is submitted for a workspace, you can configure your email address to receive a notification.<\/p>\n The Only when I am tagged as an approver<\/strong> will do exactly what it says. If you have been designated as an approver for an approval request, you will receive the email.<\/p>\n Always<\/strong> will send you an email whenever an approval request is submitted.<\/p>\n Tag Manager 360 only.<\/p>\n<\/blockquote>\n The Only when I am tagged as an approver<\/strong> option configures your email to receive a notification when an approval request where you have been designated as an approver is withdrawn (i.e. deleted).<\/p>\n Always<\/strong> will send you an email when an approval request is withdrawn.<\/p>\n Tag Manager 360 only.<\/p>\n<\/blockquote>\n The Only for approvals I requested<\/strong> option sends you an email when an approval request that you<\/em> submitted gets sent back by an approver because it needs more work.<\/p>\n Always<\/strong> will send you an email when an approval request gets sent back by an approver.<\/p>\n When you do receive an email notification for a container version, it looks like this:<\/p>\n <\/p>\n <\/a><\/p>\n<\/div>\n In addition to the information on what was added, updated, or deleted in the version, there\u2019s a link directly to the version information (See the version details<\/strong>).<\/p>\n There are also direct links (well hidden in the footer) to unsubscribe from this category of notifications or to jump directly to container notification settings.<\/p>\n An email for approval requests is a bit plainer. Here\u2019s a sample notification for when your approval is requested:<\/p>\n <\/p>\n <\/a><\/p>\n<\/div>\n You can connect a trigger service like Zapier<\/a> to create even more elaborate notifications out of your container notification emails.<\/p>\n <\/p>\n <\/a><\/p>\n<\/div>\n Above is an example of what a Gmail -> Slack<\/strong> Zap looks like. The Zap is configured to search for <\/p>\n <\/a><\/p>\n<\/div>\n Note that Gmail only works with Slack for company email addresses Zapier has a gazillion apps for integrating into the workflow. Take a look at the offering here<\/a>.<\/p>\n The notification feature is a welcome one. Being notified of changes to a container has been a very popular feature request, and it even prompted me to write a custom Slack integration<\/a> guide, which instructs how to build a simple Google Cloud<\/a> messaging system.<\/p>\n Having this feature natively in the Google Tag Manager user interface is great. It does exactly what it should, but this doesn\u2019t mean it couldn\u2019t be better<\/em>.<\/p>\n I\u2019d like to see the option of adding other email addresses that have access to the account rather than just the one you\u2019re logged in with. It would also be cool if there were even more triggers for the notification, such as workspaces being deleted, user permissions being modified, new containers created, and so forth. But, I\u2019m certainly happy with the feature as it stands today.<\/p>\n Let me know in the comments what you think about this UX upgrade to Google Tag Manager!<\/p>\n<\/p><\/div>\n\n","protected":false},"excerpt":{"rendered":" A recent update to Google Tag Manager introduced container notifications. By subscribing to container notifications, your Google Tag Manager login email address can be configured to receive an email for some of the key workflows in Google Tag Manager: containers getting published, and containers being submitted for approval (Tag Manager 360 only), for example. Be […]<\/p>\n","protected":false},"author":1,"featured_media":81279,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12033],"tags":[1498,1531,14492,14495,17019,1791],"dealstore":[],"offerexpiration":[],"class_list":["post-81278","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-analytics","tag-container","tag-google","tag-gtmtips","tag-manager","tag-notifications","tag-tag"],"yoast_head":"\n
\n X<\/span><\/p>\n
\n The Simmer Newsletter<\/strong>\n <\/p>\nTip 120: Container notifications in Google Tag Manager<\/h2>\n
![\"Container](\"https:\/\/www.simoahava.com\/images\/2020\/09\/container-notifications.jpg#ZgotmplZ\")
<\/p>\n![\"Notifications](\"https:\/\/www.simoahava.com\/images\/2020\/09\/notifications-admin.jpg#ZgotmplZ\")
<\/p>\n![\"Default](\"https:\/\/www.simoahava.com\/images\/2020\/09\/default-container-notifications.jpg#ZgotmplZ\")
<\/p>\n\n
Notification triggers<\/h3>\n
1. A container version is published<\/h4>\n
2. A container version is created<\/h4>\n
3. A workspace is sent for approval<\/h4>\n
\n
4. A workspace is withdrawn<\/h4>\n
\n
5. A workspace is sent back<\/h4>\n
\n
The email<\/h3>\n
![\"Notification](\"https:\/\/www.simoahava.com\/images\/2020\/09\/notification-email.jpg#ZgotmplZ\")
<\/p>\n![\"Approval](\"https:\/\/www.simoahava.com\/images\/2020\/09\/approval-email.jpg#ZgotmplZ\")
<\/p>\nUse Zapier for even more flexibility<\/h2>\n
![\"Zapier](\"https:\/\/www.simoahava.com\/images\/2020\/09\/zapier-test.jpg#ZgotmplZ\")
<\/p>\nVersion<\/code> and published<\/code> from emails sent from the container notification service. When such an email is received, the Zap sends a Slack message with the email subject to the channel.<\/p>\n![\"Zap](\"https:\/\/www.simoahava.com\/images\/2020\/09\/zap-email-configuration.jpg#ZgotmplZ\")
<\/p>\n\n
@mycompany.com<\/code>. The integration is not available for e.g. @gmail.com<\/code> or other commercial addresses.<\/p>\n<\/blockquote>\nSummary<\/h2>\n