Every professional in our network passes rigorous vetting assessments and only the top 0.5% make the cut. From full-stack developers to growth marketers and accountants, you’ll only meet the best of the best on South.
.svg){kind=logo}
Tableau is a visual analytics and business intelligence platform used to connect to data, analyze it, create visualizations, and publish interactive analytics experiences.
Teams can connect Tableau with sources such as:
Users can then build:
Tableau is designed around visual analysis.
Instead of writing a query for every business question and returning a static table, users can interact with dimensions, measures, filters, parameters, and visualizations to investigate the data from different perspectives.
The strongest Tableau implementations combine that flexibility with trusted data definitions and disciplined dashboard architecture.
Tableau can support analytics across many departments and business models.
Leadership teams can use Tableau to monitor high-level metrics such as:
An executive dashboard should prioritize the information needed for decisions rather than trying to display every available metric.
Sales teams may use Tableau to analyze:
Tableau can combine CRM information with finance, product, or marketing data when the underlying data architecture supports it.
Marketing dashboards may cover:
A well-structured data model helps teams analyze campaigns consistently across channels.
Finance teams may create dashboards around:
Accuracy becomes especially important when Tableau outputs support financial planning or management reporting.
Customer teams may track:
These dashboards often combine CRM, billing, product, and support information.
Tableau can visualize product data around:
For very high-volume event analytics, much of the heavy transformation work may happen upstream before Tableau queries the resulting data.
Operations teams may monitor:
Operational dashboards often require frequent data refreshes and clear exception-focused design.
People teams may analyze:
Security becomes particularly important when dashboards contain sensitive employee information.
Organizations can publish governed data sources that allow business users to explore information independently.
The goal is to provide flexibility while maintaining trusted definitions and appropriate permissions.
Tableau includes several products and capabilities for authoring, preparing, publishing, and consuming analytics.
Tableau Desktop is the traditional authoring environment used to:
It remains a core tool for deeper Tableau development.
Tableau Cloud provides a hosted environment for publishing and consuming Tableau analytics.
Organizations can use it to manage:
Tableau manages more of the infrastructure compared with a self-hosted Tableau Server deployment.
Tableau Server provides a self-managed deployment model.
Organizations may choose Server when they need greater control over their:
Cloud and Server administration require different operational responsibilities.
Tableau Prep helps teams clean, reshape, combine, and prepare information before analysis.
It can support:
For complex enterprise transformation pipelines, tools such as dbt or dedicated data-engineering platforms may handle more of the transformation layer.
Tableau Pulse provides a metric-centered analytics experience.
Users can follow selected metrics and receive information about:
Pulse can deliver information through channels such as email and Slack, helping users monitor important metrics without opening a traditional dashboard every time.
Tableau Next represents a newer generation of Tableau analytics experiences integrated more deeply into Salesforce's platform and AI ecosystem.
Its emergence adds capabilities around:
Companies already running Tableau Desktop, Cloud, or Server shouldn't treat Tableau Next as a simple version-number upgrade.
The appropriate Tableau architecture depends on the organization's current deployment, Salesforce ecosystem, analytics needs, and migration strategy.
Tableau can connect with many types of data platforms.
Common examples include:
Strong Tableau work begins with understanding where the information comes from.
Tableau can query relational databases directly.
Developers should understand:
Strong SQL knowledge becomes particularly useful when Tableau performance depends on how the underlying database is queried.
Modern Tableau environments frequently sit downstream from data platforms such as:
The warehouse may contain cleaned business models created by a data or analytics engineering team.
Tableau then becomes the visualization and consumption layer.
Tableau data sources can model information across several related tables.
Understanding the distinction between relationships and joins is critical.
Relationships connect logical tables while preserving each table's original level of detail.
For example:
Customers
↕
Orders
↕
Products
Tableau determines how the related tables need to be queried according to the fields used in a specific visualization.
Relationships can be particularly useful when tables exist at different grains.
The logical layer contains tables connected through relationships.
Each logical table preserves its own context.
This allows Tableau to generate appropriate queries for different visualizations.
Inside a logical table, physical tables can be combined through:
This gives developers more explicit control over how information is combined.
Joins merge tables according to a defined condition.
Common join types include:
Joins can be useful when developers intentionally need a flattened data structure.
They can also create duplicated values when tables exist at different levels of detail.
Relationships are generally a useful starting point for modern Tableau data modeling because they preserve table grain and defer join behavior until Tableau knows what the visualization needs.
Joins remain valuable when developers need explicit physical combinations.
Understanding both approaches matters.
A union combines rows from similarly structured tables.
For example:
January orders
February orders
March orders
could be unioned into one larger dataset.
Data blending can combine information from separate Tableau data sources.
It follows a different model from relationships or joins and remains relevant in selected existing workbooks and specialized scenarios.
Grain describes what one row represents.
Examples include:
A model connecting tables at different grains needs careful design.
For example:
Customers → one row per customer
Orders → one row per order
Order Items → one row per line item
Flattening all three incorrectly can cause customer or order values to be duplicated.
Strong Tableau developers understand grain before building calculations.
Tableau classifies fields broadly as dimensions and measures.
Dimensions commonly describe categories or attributes.
Examples include:
They often determine how data is grouped in a view.
Measures commonly represent quantitative information.
Examples include:
Measures are often aggregated.
Discrete fields create separate headers or categories in a view.
Continuous fields create an axis across a range of values.
Understanding discrete versus continuous behavior helps developers control how Tableau constructs a visualization.
Calculated fields create new values from existing data.
Calculations can support:
Tableau has several major calculation types.
Basic expressions can operate at row level or aggregate level.
Examples include:
Profit margin
Customer classification
Days between events
Row-level calculations operate on individual records.
Aggregate calculations operate on summarized values.
Understanding where a calculation occurs is important when several calculations interact.
Level of Detail, or LOD, expressions allow calculations to operate at a granularity that differs from the visible visualization.
This is one of Tableau's most important advanced analytical capabilities.
A FIXED expression calculates at a specified dimensional level independently of many dimensions in the current view.
For example:
Customer lifetime revenue
could be calculated at the customer level even while the visualization displays information by region.
INCLUDE adds dimensions to the calculation's level of detail.
This can calculate at a finer grain than the visualization.
EXCLUDE removes dimensions from the calculation's level of detail.
This can calculate at a broader grain than the visualization.
Table-scoped expressions can calculate across the complete table scope without explicitly declaring a FIXED, INCLUDE, or EXCLUDE keyword.
LOD expressions interact with Tableau's order of operations.
A FIXED expression can behave differently from an INCLUDE or EXCLUDE expression when filters are applied.
Developers building sophisticated dashboards need to understand when each calculation occurs, rather than repeatedly adding filters until the number happens to look correct.
Table calculations operate on the values already present in the visualization's result set.
They can support analytical calculations such as:
Table calculations depend heavily on which dimensions they compute across and where calculation partitions restart.
A calculation can be mathematically correct while producing the wrong business result because its addressing is configured incorrectly.
Both can solve advanced analytical problems, but they operate differently.
LOD expressions influence the query sent to the data source.
Table calculations operate over results returned to Tableau.
The choice affects:
Parameters allow users or calculations to supply configurable values.
A parameter might let someone choose:
Developers can combine parameters with calculated fields to build flexible analytical experiences.
Parameters can also update based on information available in the connected data.
This can reduce manual maintenance for changing business values.
Sets define custom subsets of data.
Examples include:
Sets can be static or respond dynamically to conditions.
They become particularly powerful when combined with:
Groups combine dimension members into larger categories.
For example:
Individual product categories
could be combined into:
Hardware
Software
Services.
For more durable business logic, upstream data modeling may be preferable to manually maintained workbook groups.
Date logic appears constantly in Tableau.
Common analytical requirements include:
Developers need to understand how:
interact with visualization grain.
Tableau doesn't evaluate every filter and calculation simultaneously.
Its internal order of operations affects how:
interact.
This becomes especially important when dashboards use FIXED LOD expressions.
Understanding the order of operations is often the difference between intentionally solving a calculation problem and accidentally making a dashboard appear correct.
Strong Tableau development involves choosing visual forms according to the question.
Useful for comparing categories.
Useful for trends over time.
Useful for understanding relationships between measures.
Useful when geography is analytically meaningful.
Useful for displaying patterns across two dimensions.
Useful when a small number of metrics need immediate attention.
Tables remain useful when users need precise values.
A dashboard doesn't improve simply because every table has been converted into a colorful chart.
A dashboard combines several analytical elements into one experience.
Strong dashboard design considers:
Before building charts, determine what the user needs to understand or decide.
An executive may need:
An analyst may need deeper exploration.
Those audiences should receive different interfaces.
The most important information should receive the strongest visual emphasis.
Supporting context should remain available without competing with the primary message.
More charts don't automatically create more insight.
Dense dashboards can make users work harder to determine what matters.
Consistent:
make dashboards easier to interpret.
Actions create interactive behavior between views.
Selecting one view can filter another.
For example:
Select a region
→ update sales, customers, and product views.
Highlight actions emphasize related marks while preserving surrounding context.
URL actions can send users from Tableau into:
Dashboard interactions can update parameter values.
This enables more sophisticated interactive analytical experiences.
Users can dynamically change membership in a set through interaction with a visualization.
Set actions can support comparative or exploratory workflows.
Tooltips provide additional information when users interact with a mark.
They can reduce dashboard clutter by keeping supporting detail available on demand.
Tooltips should explain information rather than merely repeat labels already visible in the chart.
Tableau Prep provides a visual environment for data preparation.
Developers can use Prep to:
A Prep workflow is represented as a flow.
A simplified flow might look like:
CRM export
↓
Clean fields
↓
Join customer data
↓
Aggregate
↓
Publish output
Prep supports calculations for transforming information before it reaches the visualization layer.
Some advanced capabilities include:
Prep can work well for transformation workflows closely connected with Tableau.
Larger data organizations may move reusable enterprise transformations upstream into:
This can prevent important business logic from becoming locked inside one BI platform.
Tableau can work with live data or extracts.
With a live connection, Tableau queries the underlying data source as users interact with the visualization.
This can be useful when:
Performance depends heavily on the source system.
Tableau extracts store optimized copies of data for analytical use.
Extracts can improve performance and reduce repeated pressure on operational databases.
They can also support scenarios where the original data source isn't continuously available.
Tableau's Hyper engine powers extracts and analytical query processing.
Developers working with extract-heavy environments should understand:
The decision depends on:
A dashboard that refreshes once per day rarely needs the same architecture as an operational dashboard used to monitor activity every few minutes.
A dashboard can be visually attractive and analytically correct while still being too slow to use.
Performance can be affected by several layers.
Slow source queries can make every visualization slower.
Developers may need to investigate:
Unnecessary joins, overly complicated custom SQL, or poorly designed relationships can increase query complexity.
Visualizations containing extremely large numbers of marks require more processing and rendering.
Aggregation can often provide a clearer view while reducing work.
Large numbers of expensive filters can increase query time.
Complex LOD expressions or table calculations can affect performance.
The appropriate solution depends on whether the expensive work should occur:
A dashboard containing many independent worksheets may trigger many queries.
Reducing unnecessary views can improve both usability and speed.
Tableau performance tools can help developers understand where workbook time is being spent.
Optimization should follow evidence.
Strong SQL skills complement Tableau.
Developers may use SQL to:
Tableau can connect through custom SQL.
This can solve selected problems while also making data sources harder to maintain if large amounts of transformation logic are embedded directly in workbook connections.
Reusable transformations may belong farther upstream.
dbt can create trusted analytical models upstream from Tableau.
For example:
Raw CRM + billing + product data
↓
dbt
↓
Trusted customer and revenue models
↓
Tableau
This gives Tableau cleaner business-ready datasets.
Tableau can then focus on:
instead of recreating the full transformation layer inside every workbook.
Completed workbooks can be published to Tableau Cloud or Tableau Server.
Publishing can make analytics available to:
according to their permissions.
Projects help organize Tableau content.
Organizations may structure projects around:
A thoughtful project structure makes permissions and content discovery easier to manage.
Published data sources can provide reusable, governed access to data.
Instead of every workbook independently defining:
Revenue
Customer
Product
teams can publish trusted sources with standardized:
This can improve consistency across the organization.
Tableau permissions determine which users can perform actions on content.
Access can be managed across resources such as:
Developers and administrators need to understand how permissions inherit and interact.
Row-level security restricts which data individual users can access.
For example:
Regional Sales Manager → only their region
Account Manager → only assigned accounts
Executive → all regions
Implementation options can involve:
Security should be designed as part of the architecture rather than added after dashboards are already distributed.
As Tableau usage grows, organizations need governance around:
Governance should help people find trusted data while still allowing appropriate self-service exploration.
Every important dashboard should have an owner.
Ownership helps answer:
Without ownership, Tableau environments can accumulate hundreds of abandoned workbooks.
A mature Tableau environment often needs periodic cleanup.
Teams may find:
Consolidation can improve:
Tableau developers should validate outputs against trusted sources.
For example:
Tableau revenue total
should reconcile with:
Trusted warehouse revenue total.
Visualizations should never become the sole place where a business definition exists.
Analytics experiences should remain usable by as many people as possible.
Developers should consider:
Color should enhance meaning rather than become the only way information is communicated.
Tableau supports extensions that add capabilities beyond standard dashboard and visualization functionality.
Dashboard extensions can place web applications inside dashboard zones and interact with the workbook.
Potential uses include:
Viz extensions can introduce custom visualization types directly within Tableau worksheets.
Organizations should review extension security and governance before allowing third-party code access to analytical environments.
Tableau can also connect with external analytical environments.
Examples include:
This can support:
These integrations should solve analytical requirements that genuinely need capabilities beyond Tableau's built-in calculation engine.
Tableau Pulse provides a different consumption model from traditional dashboards.
Instead of navigating through a workbook, users can follow defined metrics and receive automated insights.
A Pulse metric may provide:
Metrics can then reach users in environments such as:
Pulse can be especially useful when someone needs to monitor a few important metrics more frequently than they need full exploratory dashboards.
AI is becoming increasingly integrated into the Tableau ecosystem.
Current experiences can help users:
AI can make analytical interfaces easier to access.
The quality of the answer still depends heavily on:
A conversational interface sitting on top of inconsistent data will reproduce those inconsistencies faster.
Tableau Next expands Tableau's analytics experience inside Salesforce's newer data and agent ecosystem.
It's particularly relevant to organizations evaluating deeper combinations of:
Existing Tableau Desktop, Cloud, and Server expertise remains highly relevant across current Tableau environments.
A modern Tableau workflow might look like this:
Tableau becomes the analytics layer connecting governed data with the people making business decisions.
A Tableau Developer specializes in designing, building, optimizing, and maintaining Tableau dashboards and analytics environments.
A BI Developer works more broadly across business intelligence technologies and may use Tableau alongside other BI platforms.
A Data Analyst may use Tableau to explore information and communicate analytical findings.
An Analytics Engineer usually works farther upstream, creating trusted analytical models that Tableau dashboards consume.
A SQL Developer may work with Tableau teams on database queries, data models, and performance.
A Data Engineer builds the pipelines and data infrastructure supplying information to Tableau.
Tableau and Power BI are business intelligence platforms used to create analytics and dashboards.
Tableau has deep capabilities around:
Power BI integrates particularly closely with Microsoft's ecosystem around:
Companies should usually prioritize expertise in the BI environment already central to their reporting stack.
If you need the Microsoft-specific role, explore Power BI Developers.
SQL queries and transforms data.
Tableau provides visual analytics on top of that information.
A Tableau Developer may use SQL to create or validate a dataset and Tableau to build the interface through which the business explores it.
Strong Tableau development often benefits from both skills.
dbt focuses primarily on analytical transformation and modeling.
Tableau focuses primarily on analysis and visualization.
A modern architecture might use:
dbt → trusted transformation layer
Tableau → visual analytics layer.
Separating those responsibilities can keep major business logic reusable across dashboards and other downstream systems.
Excel provides flexible spreadsheet analysis.
Tableau specializes in scalable interactive visual analytics connected with managed data sources.
Excel can work well for:
Tableau becomes more useful when organizations need:
Many companies use both.
Tableau centers strongly on visual analytics and interactive dashboard development.
Looker has historically emphasized a centralized semantic modeling layer and governed exploration.
The best fit depends on:
Tableau is a visual analytics and business intelligence platform used to connect with data, perform analysis, create dashboards, and publish interactive analytics experiences.
Important skills include data modeling, relationships, calculated fields, LOD expressions, table calculations, parameters, dashboard design, Tableau Prep, SQL, performance optimization, security, governance, and publishing.
Level of Detail expressions allow developers to calculate values at a different granularity from the visible visualization.
The primary types are FIXED, INCLUDE, and EXCLUDE.
LOD expressions influence calculations performed as part of querying the underlying data.
Table calculations operate on values already returned to the Tableau visualization.
That difference affects filters, behavior, and performance.
Relationships connect logical tables while preserving their individual level of detail.
Joins physically combine table rows according to a predefined join condition.
Relationships are generally a useful starting point for modern multi-table Tableau data sources.
Tableau Prep is Tableau's data-preparation environment for cleaning, combining, reshaping, and transforming data before analysis.
A live connection queries the underlying source as users interact with Tableau.
An extract stores an optimized analytical copy of the data.
The best choice depends on freshness, performance, volume, and source-system requirements.
Tableau Pulse allows users to follow defined business metrics and receive insights about changes and trends through Tableau Cloud and supported communication channels.
Tableau Next is part of Salesforce's newer generation of Tableau analytics experiences, with deeper connections to Salesforce's data and AI ecosystem.
Tableau Developers, BI Developers, Data Analysts, Analytics Engineers, SQL Developers, and Data Engineers can all work with different parts of the Tableau ecosystem.
Understanding Tableau helps you identify whether your analytics environment needs stronger data modeling, advanced calculations, dashboard design, Prep workflows, performance, governance, security, or publishing expertise.
If you need someone dedicated to building and maintaining Tableau analytics experiences, South can help you hire Tableau Developers in Latin America.
Schedule a free call and find remote data and analytics talent in Latin America with South.
