---
schema_version: "1"
id: b302abbfec067af8bc790caee898d5b02e4687b28496a01a2338886bbf1fdf48
title: Preparing Your Data for Pulse
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/tableau_pulse_prepare_data.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.tableau_pulse_prepare_data.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 6885b05cfbc3abfd91fba1272bcd50ccbbfe37fd2393d8f49b29d7b8309b0bb0
description: Once you know the critical KPIs you’d like to build in Pulse, the next step is to locate where the supporting data resides.
products:
  - Tableau
release: "264"
---
# Preparing Your Data for Pulse

Once you know the critical KPIs you’d like to build in Pulse, the next step is to locate where the supporting data resides.

It's important to determine if these data sources are published (_required_), certified, and if they require any transformation. We recommend using the [Data Source Manager for Tableau Cloud](https://exchange.tableau.com/products/1022) Accelerator ahead of creating any Pulse metrics to better explore, improve, and validate the data sources you have in Tableau, so that you can more comfortably scale self-service and AI-driven solutions to your users.

The best Pulse use cases involve tracking a metric’s current value compared to the past (ex, “How do we compare YoY from a year ago…”) or future (“Are we trending towards hitting our quota?...”). Work with your data teams to identify any gaps in your available data and define the data requirements for your Pulse use case. As such, keep in mind the data best practices for Pulse:

- Outline how data will move from sources to Tableau Pulse, ensuring seamless integration between systems
    - Optimize joins in the [physical data source](https://help.tableau.com/current/online/en-us/datasource_datamodel.htm)
- Data is current and changes regularly
    - Implement data cleaning, validation, and enrichment processes to ensure the data is accurate, consistent, and reliable for use in Tableau Pulse
- Data is granular, without pre-aggregations
    - Pre-build computations in the physical data source
- Data contains key dimensions and clean, contextual, and human-readable field names (as these will be visible in Pulse)
    - Hide or isolate unneeded attributes
    - Assign clear business names to attributes
    - Use title-style capitalization rather than all caps
    - Use spaces rather than hyphens or underscores to separate words
    - Don’t use special characters
    - Don’t use Boolean fields that appear as true or false
    - Don’t use dimensions that consist of indecipherable strings (e.g. IDs)

Finally, identify if the data is available as a live connection or if it's an extract. If it's an extract, ensure the [data refresh schedule](https://help.tableau.com/current/server/en-us/publish.htm) aligns with the frequency of your reporting needs to maintain up-to-date insights.

Use this [Pulse Metric Project Plan Template](https://docs.google.com/spreadsheets/d/10pZHpMaCDivJ3JLK2l4jfr383IphUGsUQESsRNKmr8k/edit?gid=1181145025#gid=1181145025) to help document and plan out the necessary components of building out data requirements and Pulse metrics.