How to Set Up Tableau Pulse for Your Team
Last updated Apr 28, 2026

Tableau Pulse changes how teams interact with data. Instead of waiting for someone to open a dashboard, Pulse sends users the metrics they care about, directly in their inbox or Slack channel, with plain-language summaries explaining what changed and why. According to Tableau's own usage data, teams using Pulse see a measurable reduction in ad hoc analytics requests because front-line managers get answers before they need to ask.
This guide covers everything an admin needs to activate Tableau Pulse, configure digests, and turn on AI-powered insight summaries for their organization.
Prerequisites
Tableau Pulse only runs on Tableau Cloud. It is not available in Tableau Desktop or Tableau Server on-premises. Before you begin, confirm:
- You have a Site Administrator role on Tableau Cloud.
- At least one published, live data source is available on the site.
- Users who will receive digests have valid email addresses in their Tableau profiles.
- If you want Slack delivery, a Slack workspace must already be connected to your Tableau Cloud site.
The legacy Metrics feature, which Tableau retired in February 2024, does not migrate to Pulse automatically. If your site had legacy metrics, note the data source, measure, and time dimension for each one and recreate them manually in Pulse.
Step 1: Enable Tableau Pulse on Your Site
The feature is off by default. To turn it on:
- Sign in to Tableau Cloud and go to Settings from the main navigation.
- Under the Tableau Pulse section, find Deployment and select Turn on Tableau Pulse.
- Choose whether to enable it for all users or limit it to a specific group. Limiting to a group is useful for a pilot rollout before a full launch.
- If you select a group, choose it from the dropdown.
- Click Save.
Users outside the enabled group who navigate to a Pulse URL will see an access denied message. Note that the API-level access check does not enforce group restrictions, so users accessing Pulse through an embedded scenario or the REST API will still see it regardless of the group setting.
Step 2: Prepare Your Data Sources
Tableau Pulse builds metrics from published data sources on Tableau Cloud. The data source must meet these requirements:
- It must be published to Tableau Cloud (not just locally extracted).
- It must contain a date or datetime field that Tableau can use as the time dimension.
- Credentials must be embedded, passed via single sign-on, or saved per-user, because Pulse never prompts users to log in to the database directly.
To control who can build metric definitions from a source, use the Create Metric Definitions permission capability on the data source. You can allow users to view metrics based on a source without letting them create new definitions by granting View and Connect but denying Create Metric Definitions.
Row-level security applied at the data source level carries through to Pulse. Each user sees only the data rows their credentials allow.
Step 3: Create a Metric Definition
A metric definition is the template from which individual metrics are generated. Users with a Creator, Site Administrator Explorer, or Explorer (can publish) site role can create them.
- Navigate to Tableau Pulse from the main menu.
- Click New Metric Definition.
- Select the published data source.
- Choose a measure (the number you want to track, for example total revenue or open tickets).
- Choose a time dimension (the date field Pulse will use to build the time series).
- Optionally add dimension filters to scope the metric, for example a specific region or product line.
- Set a name for the definition using human-readable terms. Field names like TOT_REV_FIN_2026 cause problems downstream in AI summaries. Use "Total Revenue" instead.
- Save the definition.
Once saved, the definition becomes the source for any metric a user creates by adjusting the filters. A new metric is generated automatically each time a user applies a new filter combination to an existing metric.
Step 4: Configure Digest Channels and Schedule
Digests are the scheduled summaries Pulse sends to users who follow a metric. By default, both email and Slack delivery are available if Slack is connected.
To restrict channels:
- Go to Settings > Tableau Pulse > Digest.
- Toggle Let users receive email digests and alerts and Let users receive Slack digests and alerts to match your policy.
- Save.
To set the digest schedule:
- Under Digest Schedule, choose a Digest start time. This is when Pulse begins generating digests, not when they arrive in inboxes. Allow at least an hour for generation and delivery.
- Set the Weekly digest day and the Monthly digest day.
- Save.
Aligning the digest start time with your data source refresh schedule ensures users receive summaries based on the latest data. For example, if your warehouse runs a nightly ETL at 2 AM and finishes by 3 AM, setting the digest start time to 4 AM means users get fresh numbers in their morning emails.
Step 5: Turn On AI Insight Summaries
Tableau Pulse AI features are off by default and must be enabled separately from the main Pulse setting.
To activate personalized AI summaries:
- Go to Settings > General.
- Under AI in Tableau, check Tableau Pulse: Summarizes key metric insights.
- Save.
Insight summaries use generative AI to write natural-language explanations of what changed in a metric and why. Tableau states that its AI does not use your site's data for model training, and that prompts and responses are not stored outside of Tableau Cloud. The summaries go through the Einstein Trust Layer when calling OpenAI APIs for semantic matching.
Two additional AI settings are available:
- Better semantic matches for Ask Q&A: Improves the natural-language question interface by sending queries to OpenAI for semantic processing. This setting can be turned on independently and does not require a connected Salesforce org.
- Enhanced Q&A (Discover): Enables a conversational interface for exploring groups of related metrics together. This is a Tableau+ premium feature and requires a connected Salesforce org with Einstein generative AI configured.
Start with insight summaries. The basic AI summarization works well for most teams and requires no Salesforce configuration.
Step 6: Following Metrics as a User
Once Pulse is active, any user on the site can follow metrics by navigating to Tableau Pulse and browsing available metric definitions. Following a metric opts the user into digests at their chosen frequency (daily, weekly, or monthly). Users can also configure their digest preferences, including channel (email or Slack) and frequency, from their Tableau Pulse settings.
Users who want to explore a specific metric further can use the Ask Q&A interface on the metric page to ask questions in plain language. For example: "Sales in the Northeast last month" or "What changed in conversion rate last week?"
Common Setup Mistakes
Several issues come up consistently in Tableau Pulse deployments.
First, teams frequently forget to turn on AI settings after enabling Pulse. The two settings pages are independent, so enabling the main Pulse feature does nothing to activate AI summaries.
Second, embedding credentials is often skipped. Without embedded credentials or SSO, users cannot view metric data in digests. They see the metric card but get an authentication error when trying to load the chart.
Third, groups are removed from Pulse access without first removing those users as metric followers. When a user loses Pulse access but still follows metrics, they receive digest emails with links they cannot open. Remove followers before restricting access to prevent this.
If your team wants to skip the Tableau Cloud dependency entirely and get AI-powered data exploration without a BI setup, VSLZ handles it from a direct file upload with no data source configuration required.
Next Steps
After completing this setup, the practical next step is creating two or three metric definitions around your highest-priority KPIs and enrolling a small pilot group. Measure whether digest engagement is high enough to justify the admin overhead of maintaining metric definitions as your data sources evolve. Tableau Pulse works best when metric definitions are kept to a focused set of KPIs that a specific team actually monitors weekly, rather than a comprehensive library of every metric the organization tracks.
FAQ
Does Tableau Pulse work with Tableau Desktop or Tableau Server?
No. Tableau Pulse is only available on Tableau Cloud. It requires Tableau's hosted infrastructure to run the insight-generation engine, send scheduled digests, and power the AI summarization features. Tableau Server on-premises and Tableau Desktop do not support Pulse.
What site role do users need to create metric definitions in Tableau Pulse?
Users must have a Creator, Site Administrator Explorer, or Explorer (can publish) site role to create or edit metric definitions. There are no site role restrictions for following metrics, viewing metrics, or setting personal goals on a metric. Any licensed user on the site can follow a metric once it exists.
How do I connect Tableau Pulse to Slack?
Slack delivery for Pulse digests requires a site-level Slack integration. A Tableau site administrator connects the Tableau Cloud site to a Slack workspace through Settings > Integrations > Slack. Once connected, individual users can opt into Slack delivery from their Tableau Pulse preferences and choose which Slack channel receives their digest. The admin can also disable Slack delivery site-wide under Settings > Tableau Pulse > Digest.
Is the AI in Tableau Pulse feature available on all Tableau plans?
Basic AI insight summaries and the improved semantic matching for Ask Q&A are available on standard Tableau Cloud plans and do not require a Salesforce org connection. Enhanced Q&A (Discover), the conversational multi-metric exploration interface, is a Tableau+ premium feature and requires both a Tableau+ license and a connected Salesforce org with Einstein generative AI configured.
How often does Tableau Pulse send metric digests?
Users can choose daily, weekly, or monthly digest frequency per metric they follow. Admins set the site-wide digest start time and the specific day for weekly and monthly digests. The start time is when Tableau begins generating digests, not when they are delivered. Generation and delivery typically takes one or more hours after the scheduled start time.


