Most Tableau users check dashboards reactively — they remember to look, or someone asks. Alerts and subscriptions invert that model: the analytics finds you when something matters. This guide covers how to configure both effectively, their limitations, and the patterns that make automated analytics delivery actually useful.
Dashboard consumption is typically reactive: a user remembers to check a dashboard, or a manager asks for an update in a meeting. The analytics is available but passive. Alerts and subscriptions change that dynamic — they push analytical insights to the right person at the right time, based on data conditions rather than human memory.
Tableau provides two distinct mechanisms for automated analytics delivery: data-driven alerts that trigger on threshold conditions, and subscriptions that deliver scheduled snapshots. They solve different problems and have different limitations.
Data-Driven Alerts
A data-driven alert monitors a single mark on a view and sends a notification when a threshold condition is met. The condition is evaluated each time the view's data refreshes — on extract refresh for extract-based data sources, continuously for live connections.
**What alerts can monitor**: A single continuous measure on a view. The condition is one of: greater than, greater than or equal to, less than, less than or equal to, equal to a specified value. The measure must be a visible mark in the view — alerts cannot be defined on hidden calculations or summary-level aggregations unless they appear as a mark.
**Alert delivery**: Email notification only (no Slack, no webhook, no in-app push in standard Tableau). The notification includes a link to the relevant view and optionally a snapshot image. Recipients can be the alert creator plus any licensed Tableau users on the same site.
**Alert limitations that matter in practice**:
- One condition per alert. You cannot define compound conditions (revenue below threshold AND margin below threshold).
- Alert suppression: once an alert fires, it will not fire again until the condition resolves and re-triggers. If revenue drops below $100K on Monday, alerts on Tuesday when it is still below $100K.
- No alert-specific calculation. The threshold is compared against the mark value as displayed, which means aggregation and calculation choices at the view level determine what is actually being compared.
- Alerts are per-user: each recipient who wants the alert must configure it themselves, or an administrator can configure alerts on behalf of users using the Tableau REST API.
**When alerts work well**: Single KPI thresholds that require immediate attention when crossed — SLA breach indicators, inventory levels, budget overrun indicators. The simplicity of the mechanism is a feature: the alert is unambiguous and tied directly to a visible mark.
**Configuring alerts via REST API**: The Tableau REST API exposes alert management endpoints. Organisations with large user bases or complex alert requirements can manage alert configurations programmatically — creating, updating, and deleting alerts across many users without manual configuration per user. This is significantly more scalable than expecting users to configure their own alerts.
Subscriptions
A subscription delivers a rendered snapshot of a view or workbook to email recipients on a defined schedule. Unlike alerts, subscriptions are time-triggered rather than condition-triggered — they send on the schedule regardless of whether the data has changed.
**What subscriptions deliver**: A rendered image of the view embedded in the email, with a link to the live dashboard. For workbooks with multiple sheets, the subscription can deliver all sheets as a multi-image email. The rendered image reflects whatever filters are applied to the view at subscription time — personalised views work, but each subscriber sees the same filter state unless customised.
**Subscription scheduling**: Subscriptions can be scheduled on Tableau Server/Cloud schedules — hourly, daily, weekly, monthly — or on a custom schedule in some versions. The subscription runs on the schedule; if the extract has not refreshed, subscribers receive the last available data.
**Subscription limitations**:
- Email only. Subscriptions cannot deliver to Slack, Teams, or other channels natively without third-party integration or custom scripting.
- Static delivery: subscribers receive the same view. Subscriptions do not support conditional content (send this section only if condition X) or personalised data (each recipient sees only their data) without custom development.
- Rendering failure: subscriptions can fail silently if the view times out during rendering. Large, complex dashboards with slow underlying queries fail subscription rendering consistently. Monitor subscription failures in the Tableau Admin views.
- Filter state: the subscription captures the view's default filter state. If users have saved custom views, subscription delivery may not reflect their preferred filter configuration.
**Using subscriptions effectively**: Subscriptions work best for regular operational reporting that a defined audience receives on a reliable cadence — weekly executive summary, daily operational dashboard, end-of-month metrics. The audience knows when to expect the delivery and uses it as a prompt to review and respond.
Combining Alerts and Subscriptions
The most effective automated delivery strategy uses both mechanisms for their appropriate roles:
- Subscriptions for regular cadence: weekly/monthly operational reports delivered on schedule to defined audiences, regardless of whether anything notable happened
- Alerts for condition-triggered notification: critical threshold breaches that require immediate attention, where the timing of the notification matters
A common antipattern is using subscriptions as a replacement for alerts: scheduling hourly subscriptions to check whether something changed, which overwhelms recipients and trains them to ignore the emails. Subscriptions should have meaningful delivery cadence; alerts should handle real-time threshold monitoring.
Limitations and Alternatives
Both mechanisms have the same fundamental limitation: email delivery to Tableau-licensed users only. For organisations that want analytics delivered to Slack, to non-Tableau users, or through channels other than email, custom solutions are necessary.
The Tableau REST API exposes the data behind views through the Query View Data endpoint. Custom notification systems can query Tableau for view data, evaluate conditions, and deliver notifications through any channel — Slack, PagerDuty, Teams webhooks, SMS. This requires development investment but provides full flexibility in delivery channel, condition logic, and recipient list.
Tableau Pulse, available in Tableau Cloud, provides a different model: AI-generated insights delivered in a conversational format rather than rendered dashboard images. Pulse detects anomalies and trends automatically without manual alert configuration.
Our managed BI services include subscription and alert configuration management as part of the ongoing service — contact us if your organisation needs a systematic approach to analytics delivery.
A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.
Book a Call →