#GTMTips: Notifications for containers in Google Tag Manager – News Couple
ANALYTICS

#GTMTips: Notifications for containers in Google Tag Manager


A recent update to Google Tag Manager has been introduced container notifications.

By subscribing to container notifications, the Google Tag Manager login email address can be configured to receive email for some of the main Google Tag Manager workflows: publish containers, containers submitted for approval (Tag Manager 360 only), for example .

Be sure to check out the official Help Center article about container notifications.

In this article, I’ll walk you through the feature and share some tips on how to make it even more useful!


X


Simmer . Newsletter

Subscribe to the Simmer newsletter to get the latest news and content from Simo Ahava right in your inbox!

Tip 120: Container Notifications in Google Tag Manager

You will find container notifications for individual container below Supervisor:

Notifications in management

You can also set files hypothetical Notification settings in your User settings.

tap on full list in the upper-right corner of the GTM user interface (the three vertical dot menu) and select User settings. Scroll down to File Default container notifications. Whatever you set here will run by default in all containers you manage.

Default container notifications

when you set Default container notifications, will be applied to all containers that you have access to until you go to each individual container, change the value of the notification setting, and Memorizes He. She.

A bit confusing, the settings for an individual container don’t tell you whether it’s the current settings or not transcend or inherit The default container notification setting.

Notification triggers

To receive an email notification, you can configure the following events to trigger one:

1. A container version has been published

The Always The option sends an email whenever a version is published in it Which environment.

The live environment only The option only sends an email when a version is published in the live environment.

2. Create a container copy

The Always The option sends an email whenever a container version is created (but not published).

3. The workspace is sent for approval

Tag Manager 360 only.

When you submit an approval request for a workspace, you can configure your email address to receive a notification.

The Only when I’m flagged as OK You will do exactly what you say. If you have been designated as the approver of the consent request, you will receive the email.

Always We will send you an email whenever an approval request is submitted.

4. Workspace pulled out

Tag Manager 360 only.

The Only when I’m flagged as OK The option configures your email to receive a notification when the consent request in which you were designated as an approver is withdrawn (ie delete).

Always An email will be sent to you when the approval request is withdrawn.

5. The workspace is returned

Tag Manager 360 only.

The Only for the approvals you requested Option sends you an email when asking for approval You are It is being sent back by an approver because it needs more work.

Always An email will be sent to you when the consent request is sent back by an approver.

E-mail

When you receive an email notification for a container release, it looks like this:

Email notification

In addition to information about what has been added, updated or deleted in the version, there is a direct link to the version information (See version details).

There are also direct links (which are well hidden in the footer) to unsubscribe from this notification category or to go directly to the container notification settings.

Email for approval requests is a little simpler. Here is a sample notification when your consent is requested:

Approval email

Use Zapier for more flexibility

You can connect a launch service like Zapier to create more detailed notifications from container notification emails.

Zapier Slack

Above is an example of what Gmail -> Slack It seems zap. Zap is configured to search for Version And published From emails sent from the container notification service. Upon receiving such an email, Zap sends a Slack message with the email subject to the channel.

Zap . email configuration

Note that Gmail only works with Slack for corporate email addresses @mycompany.com. Integration not available for example @gmail.com or other business addresses.

Zapier has a plethora of apps to integrate into your workflow. Take a look at the presentation here.

summary

Notification feature is welcome. Receiving my notification of changes to the container has been a very popular feature request, and it even prompted me to write a custom Slack integration guide, which instructs me on how to build a simple Google Cloud messaging system.

Having this feature in the Google Tag Manager user interface is great. It does exactly what it should do, but that doesn’t mean it can’t be better.

I’d like to see the option to add other email addresses that have access to the account instead of just the one you’re signed in with. It would also be nice to have more notification triggers, such as deleting workspaces, modifying user permissions, creating new containers, etc. But I’m certainly happy with the feature as it is today.

Let me know in the comments what you think about this UX upgrade to Google Tag Manager!



Source link

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button