Monitors & alerts

A monitor checks on an hour, day, week, or month grain and notifies on a hit. It does not change collection, and it does not act on the alert for you.

ConsoleAll-platform analyticsOperationsMonitors

Each card shows enabled state, severity, condition, grain, and the last trigger. New monitors are created at warning severity; the dialog does not change it.

Metrics & definitions

Pick a built-in measure or one saved metric, then a condition. The built-in keys on the form are pv, uv, sessions, bounce_rate, avg_duration, error_rate, and errors: pageviews, visitors, sessions, bounce rate, average duration, error rate, and error count.

Condition	Compared with	When it fires
Fixed threshold	The current value and the number you enter	Greater, less, greater or equal, or less or equal
Period change	Percent change versus the previous period	The change crosses your percent; no previous period means no fire
Forecast band	Mean of the last 7 days and the same weekday	Skipped until 14 days of history. Strict is about ±10%, medium ±30%, loose ±50%
Anomaly	Mean and spread of the same weekday over 28 days	Needs about 30 days by default. Confidence 70–99; higher widens the band
Frustration	Rage clicks per 1,000 pageviews	At or above the rate you enter
Collection gap	Minutes with no data	Longer than that gap

A dry run calculates only. It does not send, and it reports how many times the last 30 days would have fired. By default a notification is not repeated for about 60 minutes, and three hits in a row pause the rule. If you do not pick channels, every enabled channel is used. Channels are managed on the settings page described in Scheduled reports.

How to use it

Example: built-in uv, fixed threshold, greater than 100, grain day. Save, then dry-run to see whether the current value would fire. Saved metrics are the ones in Custom metrics.

Access & limits

Anyone who can open the project can view the list. Create, pause, resume, and dry-run need an analyst or above. Delete needs an admin or the owner. The create dialog only offers the six conditions above; segment-size monitors are not available yet.

FAQ

Why does a period-change rule never fire? It stays quiet when the previous period has no data.

Forecast and anomaly rules show nothing. Is that a failure? No. They skip while history is short and start working once enough days have accumulated.

Annotations

ConsoleConfigurationAnnotations

A single-day annotation draws a dashed line with a short label; a date range draws a light band. Hover to see the title, type and author. Show / Hide annotations in the chart legend applies to the current browser only.

Where they appear

Chart	Annotations shown	Add from the chart
Web analytics › Overview	Scope All and Web	Yes
Web analytics › Data report	Scope All and Web	No
App and mini program overview	All plus the current platform	Yes
Trend cards on dashboards	Every scope	No

To add from a chart, click Annotate, drag across a date range, release, and fill in the form.

Fields

Field	Notes
Date	Start date is required. Leave the end date empty for a single day; it cannot be before the start
Type	Campaign, Release, Ads change, Incident, Holiday, Other. The type sets the color
Title	Required, up to 40 characters
Note	Optional, up to 500 characters
Scope	All, Web, App, Mini program. Shown only on that platform's trend charts

Generated annotations

App releases. The first day each app or mini program version appears becomes a Release annotation titled platform vVERSION. Native platforms get scope App; mini programs get scope Mini program. Sync runs at most every 10 minutes when a trend chart loads, or on demand with Sync now on the annotations page. These cannot be edited. You can delete one, but the next sync recreates it.

Public holidays. When on, trend charts also show Chinese public holidays, including adjusted long weekends. Holidays are not stored and cannot be edited or deleted. On by default.

Bulk import

Columns are date_from,date_to,type,title,note,scope. With a header row, column order and case do not matter; without one, columns are read in that order.

date_from,date_to,type,title,note,scope
2026-11-01,2026-11-11,campaign,Singles' Day sale,Main venue + livestream,all
2026-11-20,,release,v2.3.0 release,,app

• type is one of campaign, release, ads, incident, holiday, other; empty means other.
• scope is one of all, web, app, mp; empty means all.
• An empty date_to means a single day.

Up to 500 rows per import; extra rows are ignored. Rows with errors are listed by line number and the rest are imported. Imports are not deduplicated: importing the same file twice creates two copies.

Access & limits

Every project member can see annotations. Creating, editing, deleting, importing, toggling holidays and Sync now require the analyst role or higher.

Holidays currently cover 2026 only. The annotations page lists up to 1,000 entries, newest start date first.

Scheduled reports

Daily is yesterday. Weekly is last Monday through Sunday and sends on Monday; monthly is the previous calendar month and sends on the 1st. It does not replace the metric monitors in Monitors & alerts.

ConsoleConfigurationSettingsNotifications

Find the Scheduled reports block. The same page holds notification channels and five operational alerts: traffic spike, traffic drop, crawl anomaly, error spike, and quota.

What the report shows

Visitors, pageviews, sessions, bounce rate, and average duration with period change, a traffic trend, the fastest-rising pages and sources, sources that are new this period, the AI content ledger, conversions for enabled goals, and a short reading. The reading is written from rules first. If a model is configured, it polishes that draft. It does not run a separate search.

How to configure

The send hour uses the site timezone. The scheduler also tries the following hour so a missed tick can still send. The title template may use ${date} and ${site}. If you select no channels, every enabled channel is used. Channel types are Webhook, WeCom, DingTalk, Feishu, and email. Preview builds the body only. Send now pushes the daily, weekly, or monthly report you are previewing.

Example: an admin turns on the weekly report, sets the hour to 9, selects a group bot, previews, then saves. The log at the bottom of the page shows sent, failed, or skipped.

Access & limits

Saving the subscription and channels needs an admin or the owner. Turning on daily, weekly, or monthly needs a plan that includes scheduled reports. With no channels, TapCub still keeps a send log.

FAQ

I saved an email channel. Why did nothing arrive? Email is delivered only after the platform mail service is configured. Until then, test and real sends are logged as skipped, not as sent.