Analytics Alerts into Slack

November 21, 2025
  • First Published: November 21, 2025
  • Last Modified: November 21, 2025

It’s the first of the month, you sit down to compile a client report, and your stomach drops.

You notice a massive flatline in the data from three weeks ago.

Maybe a developer accidentally removed the Google Tag Manager (GTM) container.

Maybe a site update broke the checkout process. Maybe there a manual action against the site.

Whatever the cause, the tracking has been off for weeks, and you are only just seeing it now.

Explaining to a client why you didn’t spot a critical failure for 20 days is a conversation nobody wants to have.

The challenge for agencies and freelancers isn’t a lack of data; it’s where that data lives.

I’ve seen it where agencies have a shared inbox for getting access to GA4 and GTM. But a problem shared is a problem ignored.

Alerts that go into that inbox are ignored against a sea of unread emails.

We need to move those alerts out of the inbox and into the daily workflow.

Table of Contents

Moving from Email to Visibility

 

The concept here is simple (credit to digital marketing expert Dana Di Tomaso for sparking this specific approach).

We want to take the critical alerts from Google’s ecosystem and push them into a visible arena, like a dedicated Slack channel. Or even a Teams channel. I use Slack so this example will be using Slack.

The goal is simple: If traffic creates a floor, or a GTM container is published unexpectedly, the whole team sees it immediately.

You can message the client to say, “We’ve spotted this and we’re on it,” rather than apologising weeks later.

Here is how to set up this automated alert system.

Insights in Slack

Step 1: Configure Your GA4 Custom Insights

First, we need to tell GA4 what constitutes an “emergency” for your specific client.

This could be different for each and every client, or, if you’re a digital marketing agency you can choose to focus on specific metrics.

Go into your GA4 property. You want to set up Custom Insights. These act as your triggers. You shouldn’t rely solely on Google’s automated anomaly detection; you want specific thresholds.

Consider setting up alerts for:

  • A sudden drop in Key Events (Conversions): If these drop to zero or fall by 50% week-on-week.

  • Session dips: A significant reduction in daily users.

  • Channel-specific drops: If you are an SEO agency, create a segment for “Organic Search” and alert if traffic dips below a certain benchmark.

The important thing here is that you ensure you mark it for email notifications.

This will send an email (to the account you are using) when the custom insight is met.

Step 2: Set Up Tag Manager Notifications

You also want to know if someone is messing with the tracking code.

In Google Tag Manager, adjust your notification settings so that any time a container is Published, an email is sent.

To do this – head to Admin > Container Notifications from within your Google Tag Manager container.

This is vital for spotting unauthorised changes or accidental publications by other agencies working on the same site. 

Step 3: Get Your Slack Email Address

 

This is the bridge between the two platforms. Slack allows you to send emails directly to a specific channel.

  1. Create a new channel in Slack (e.g., #client-alerts or #analytics-watch).

  2. Click the channel name at the top of the window to open the details.

  3. Click on the Integrations tab.

  4. Select Send emails to this channel.

Slack will generate a unique email address for that channel. Copy it to your clipboard.

Alerts in Slack

Step 4: Create the Email Filter 

 

Now, we need to connect the dots. You don’t want every email going to Slack, only the alerts.

I use Gmail, but most email providers have similar filtering rules.

  1. Go to your email settings and create a new Filter.

  2. Set the criteria to match your GA4 and GTM alerts. You can filter by Sender (e.g., noreply@google.com) or by Subject Line (e.g., containing “Insight” or “Container Published”).

  3. In the action settings for the filter, choose Forward it to.

  4. Paste the unique Slack email address you generated in Step 3.

Note: When you first add a forwarding address in Gmail, it will send a confirmation code to that address. This code will pop up in your Slack channel. Just grab it, verify it in Gmail, and you are good to go.

Why This Matters

 

Once this is live, any new insight—whether it’s a spike in traffic you should celebrate or a drop in users you need to investigate—appears in Slack.

It helps illuminate some issues… if somebody removed the tag manager container or there’s been a big downturn in traffic, it’s much better if you’re able to say to a client, ‘Hey we’ve caught this’.”

It turns a passive monitoring task into an active team discussion. It keeps the workspace uncluttered while ensuring that when things break, the right people know about it instantly.

It’s a smarter way to work, and it saves you from those awkward first-of-the-month conversations.

Kyle

Author

Hello, I'm Kyle Rushton McGregor!

I’m an experienced GA4 Specialist with a demonstrated history of working with Google Tag Manager and Looker Studio. I’m an international speaker who has trained 1000s of people on all things analytics.

Find out more About me
Scroll to Top