Analytics
Verified by Toolspoke

Traffic anomaly alert

By Toolspoke

Checks yesterday's Google Analytics traffic against the same weekday over four weeks and tells Slack only when something moved.

Needs a Toolspoke account. You choose which project it installs into.

An illustration with made-up examples. It is not a recording.
Google Analytics + Slack
Required integrations
Runs on a schedule
Every day at 9am by default
Post only if something was flagged
What its last step does
Some actions can delete
1 of 32 actions in its tools
On this page
  1. The short version
  2. What it will never do
  3. What Traffic anomaly alert does
  4. How it works
  5. What an alert looks like
  6. Who uses Traffic anomaly alert
  7. What it connects to
  8. When it runs
  9. How to set it up
  10. Make Traffic anomaly alert fit your site
  11. Compared with other options
  12. Questions
  13. Related agents

The short version

What it is
A ready-made Toolspoke agent that watches your Google Analytics traffic and tells Slack when it moves.
What it reads
Yesterday's sessions by channel and views of your top pages, and the same weekday in each of the four weeks before.
What it finds
Channels and pages that dropped or jumped past your threshold, with enough traffic behind them to matter.
What you get
One Slack message on a day something moved, and nothing on a day it did not.
How often
Every day at 9 AM once you switch it on.
What it never does
Change your GA4 property, or say why traffic moved.
What you need
A Toolspoke account, a Google account that can read the GA4 property, and a Slack workspace.

What Traffic anomaly alert will never do

Traffic anomaly alert is told never to post on a quiet day, never to say why traffic moved, and never to flag a change with too little traffic behind it. It watches and reports.

Traffic anomaly alert will never

  • Post on a day the data was read and nothing crossed the threshold, or post more than one message a run.
  • Say why traffic moved.
  • Flag a channel or page below the minimum, however large the percentage.
  • Edit or delete a Slack message.

Why it stays quiet

An alert that fires every morning trains people to ignore it. The agent posts only when something crossed the threshold, or when it could not read GA4 at all.

Why it will not guess a cause

A drop in organic search might be a ranking change, a tag that stopped firing, a holiday or yesterday's data still processing. The agent says what moved and leaves the why to a person.

What a careless tool might writeGoogle penalised the site. Organic traffic is collapsing.
What this agent writes insteadOrganic Search: 3,180 sessions against an average of 4,920 (down 35%).

Why it ignores small numbers

A page with twenty views a day can double on one visitor. Below the minimum, the agent does not flag it, however large the percentage.

These are written into Traffic anomaly alert's instructions. They guide the agent, but they are not a permission. What it is allowed to touch is set by the access you grant.

Traffic anomaly alert reads GA4 and speaks up when something moved. Finding out why, and fixing it, stays with your team.

What Traffic anomaly alert does

Traffic anomaly alert is an AI agent that checks yesterday's traffic on one Google Analytics property every morning, against the same weekday over the four weeks before. When a channel or a top page moves past your threshold, it posts one Slack message saying what moved and by how much.

Traffic problems are usually found late. A tracking tag stops firing, a page drops out of search, a campaign link breaks, and nobody notices until the monthly report.

Comparing yesterday with the day before does not help much, because a Monday never looks like a Sunday. The fair comparison is the same weekday in recent weeks, and that is slow to do by hand every morning.

Traffic anomaly alert does that comparison each day, by channel and for your top pages. It ignores anything too small to matter, and when nothing moved it stays quiet, so the channel is worth reading on the days it speaks.

In practice, on a day something moves, you have:

  • Yesterday's total against the four-week average for that weekday
  • Each channel that dropped or jumped past the threshold
  • Top pages that moved, including one that fell out of the list
  • A warning when the whole site fell at once and the data may still be processing

How it works

Traffic anomaly alert works in four steps each morning: it reads the channels, reads the top pages, compares with the baseline and posts only if something moved. All of it comes from the agent's written instructions, which you can read and edit after you install it.

  1. Step 1: Read the channels

    Sessions, users and key events by channel, for five days.

  2. Step 2: Read the top pages

    Views of yesterday's and the baseline's top 20 pages.

  3. Step 3: Compare with the baseline

    Yesterday against the same weekday, averaged over four weeks.

  4. Step 4: Post if it moved

    One message with drops first, or nothing at all.

Drawn from this agent's own tools and instructions. It is not a recording of a run.

It compares the same weekday

Yesterday is compared with the same weekday one, two, three and four weeks earlier, averaged. A quiet Sunday is measured against other Sundays, not against a busy Friday.

It uses your time zone

The agent reads the property's time zone with get_property, so yesterday means yesterday where your business is, not in UTC.

It needs enough traffic

By default a change counts at 30% in either direction, and only for a channel averaging 200 sessions a day or a page averaging 100 views. Below that, a swing is noise and the agent ignores it.

It stays quiet when nothing moved

On a normal day it posts nothing, and the run log in Toolspoke shows the check ran. If GA4 cannot be read, it does post, so a broken check never looks like a quiet day. The limits are listed under what it will never do.

What an alert looks like

On a day something moved, Traffic anomaly alert posts one message to Slack: the site total first, then drops, then spikes, largest change first.

Northwind

Channels

  • general
  • marketing
  • web-traffic
  • engineering

web-traffic

Traffic alertAPP9:00 AM

Tuesday 27 October: 9,410 sessions against a four-Tuesday average of 10,620 (down 11%).

Drops (2)

  • Organic Search: 3,180 sessions against an average of 4,920 (down 35%).
  • /pricing: 610 views against an average of 1,040 (down 41%). Its channel mix held steady, so this is the page, not a channel.

Spikes (1)

  • Referral: 960 sessions against an average of 410 (up 134%).

Steady

Direct, Paid Search, Email and Paid Social within 30% of their averages.

One run. The company, pages and numbers are made up.
Drops

Channels and pages that fell past the threshold, with yesterday's number, the four-week average and the change.

Spikes

Channels and pages that rose past the threshold. A spike can be good news or a bot, so it is reported the same way as a drop.

Steady

What was checked and did not move, in one line, so you know the alert covered it.

When nothing moved

If no channel or page crossed the threshold, the agent posts nothing. An alert channel that speaks every day stops being read.

If every channel fell by a similar share at once, the message says yesterday's data may still be processing in GA4. If the property cannot be read, it says so once, so a missed alert never looks like a quiet day.

Who uses Traffic anomaly alert

Traffic anomaly alert suits a team whose website matters to the business and who would rather hear about a traffic problem the next morning than at the end of the month. The examples use made-up names.

An SEO lead watching search

Ines Duarte hears about the organic drop the morning after, and checks Search Console before the week is out.

In their alertNeeds youOrganic Search: 3,180 sessions against an average of 4,920 (down 35%).

A marketer running campaigns

Daniel Kim launched a partner newsletter on Monday. The referral spike confirms the link works.

In their alertWorth knowingReferral: 960 sessions against an average of 410 (up 134%).

A developer after a release

Ruth Mensah shipped a new pricing page. The alert flags the page while its channels held, and she finds the analytics tag missing.

In their alertNeeds you/pricing: 610 views against an average of 1,040 (down 41%).

A founder who never opens GA4

Lars Nilsson hears nothing most days. That silence is the point.

In their alertEverything elseNo post on a day nothing moved.

What Traffic anomaly alert connects to

Traffic anomaly alert connects to two tools: it reads Google Analytics and posts to Slack. You connect each one yourself, and Toolspoke stores the connection encrypted, so the agent never sees the credential.

What Traffic anomaly alert does and cannot do in each connected tool
ToolWhat Traffic anomaly alert doesWhat it cannot do
Google AnalyticsReads the property's time zone and runs reports by channel and page (get_property, run_report, top_pages, list_dimensions_and_metrics).Change the property, its settings or its data. The sign-in asks Google for read-only Analytics access, and every action the connector has is a read.
SlackPosts one message to the channel you chose, on a day something moved (send_message).Delete messages: the connector has no delete action. It can edit its own messages and schedule messages, and the agent is told to do neither.

That the agent cannot change your GA4 property is a property of the connection, which is read-only. That it posts only when something moved, and once a run, is an instruction to the agent, not a lock. If you want a lock, a project can switch individual actions off. The access control guide explains how.

The agent reads totals by channel and page. GA4 reports hold no names or email addresses, and the alert carries none.

When Traffic anomaly alert runs

Traffic anomaly alert runs every day at 9 AM, but only after you switch its schedule on. It arrives switched off, so nothing runs and nothing is charged until you decide.

  • Each run compares yesterday with the same weekday over the four weeks before.
  • It posts one message only when a channel or page moved past the threshold.
  • It posts nothing on a quiet day, and the run log shows the check ran.
  • If GA4 cannot be read, it says so in Slack.

Each run uses model credit from your workspace balance, so it makes one run a day. The reports count against your GA4 property's API quota in the usual way. The Toolspoke tool calls themselves are free.

Your copy is an ordinary agent in your project. You can pause its schedule there, run it once on demand, change the time and edit its instructions. The agent's page lists recent runs and their cost.

How to set up Traffic anomaly alert

To start watching your traffic, add Traffic anomaly alert to a Toolspoke project, sign in to Google and Slack, choose the property and switch on the schedule. It takes a few minutes, and nothing runs until the last step.

  1. Step 1: Create a Toolspoke account or sign in

    Choose Use this agent. If you are new, you will be asked to sign up first, and you come straight back to this agent afterwards.

  2. Step 2: Add it to a project

    Pick the project it should live in. You get your own editable copy, and you can see the two tools it brings before anything connects.

  3. Step 3: Sign in to Google

    Use a Google account that can view the GA4 property. Toolspoke asks for read-only Analytics access.

  4. Step 4: Choose the property and threshold

    Pick the GA4 property to watch. Keep the default 30% threshold, or set your own.

  5. Step 5: Connect Slack

    Sign in to Slack and invite the bot to the channel alerts should go to.

  6. Step 6: Switch on the schedule

    The schedule arrives switched off. Run it once, check the numbers against GA4, then switch it on.

Make Traffic anomaly alert fit your site

Traffic anomaly alert's instructions are plain English and you can edit them after you install it. Installing copies the agent, so your edits stay with your copy. Open the agent in Toolspoke and tell the builder what to change, and it rewrites the instructions.

Paste any sentence below into the builder chat, or say the same thing in your own words.

Tighten the threshold
Flag a change at 20% instead of 30%.
Watch conversions
Also flag a channel whose key events moved past the threshold, even if its sessions held.
Watch by country
Also compare sessions by country, for countries averaging 300 sessions a day or more.
Send a weekly all-clear
On Mondays, if nothing was flagged in the past week, post one line saying the week was steady.
Check twice a day
Also run at 3 PM, comparing this morning with the same hours over four weeks.

This changes when the agent wakes up, so the builder edits its schedule as well as the instructions.

None of these edits needs more access or touches the Never rules. They change what Traffic anomaly alert is told, not what the connections allow.

How it compares to other options

Traffic anomaly alert beats the alternatives when you want to hear about a traffic problem the next morning without anyone checking a dashboard, and loses to them when you need real-time alerts or a full investigation.

Traffic anomaly alert compared with GA4 insights, A weekly report, Uptime monitoring
Compared onTraffic anomaly alertGA4 insightsA weekly reportUptime monitoring
Checks every dayYesYesNo, weeklyEvery minute
Compares the same weekdayFour-week averageIts own modelWeek on weekNo
Covers channels and top pagesYesSomeYesNo
Posts to SlackYesEmail onlyIf set upYes
Catches a tag that stopped firingNext morningSometimesA week laterNo
Says why traffic movedNo, it reportsSometimesIf writtenNo

Uptime monitoring is the better choice when the question is whether the site is up right now. Traffic anomaly alert answers a different question: whether the people who usually arrive did arrive.

GA4's own insights can flag unusual changes too, by email and on its own model. Traffic anomaly alert uses a comparison you can read and change, covers the channels and pages you care about, and posts where your team already works.

Frequently asked questions

Can Traffic anomaly alert change my Google Analytics?

No. The sign-in asks Google for read-only Analytics access, and every action the connector has is a read.

Why does it not post every day?

Because a daily all-clear trains people to stop reading the channel. It posts when something moved, or when it could not read GA4. The run log in Toolspoke shows every check.

Is yesterday's GA4 data complete at 9 AM?

Usually, but not always. GA4 can still be processing the previous day. When every channel falls by a similar share at once, the alert says the data may still be processing rather than calling a collapse.

Will it tell me why traffic dropped?

No. It says which channel or page moved and by how much. Finding out why is a person's job, and the alert gets you there a day sooner.

Can it watch more than one property?

One per copy as shipped. Install it again for a second property, or ask the builder to loop over a list.

Is Traffic anomaly alert free?

It has no price of its own, and every Toolspoke plan includes agents. Tool calls cost nothing, but each run draws on your usage balance. Pricing has the details.

Hear about a traffic drop the next morning

Sign in to Google, choose your property and switch on the schedule. The first alert lands the morning something moves.