Updated June 17, 2026 by Sunny Chauhan, Salesforce Platform Developer II.

Salesforce shipped Tableau Next for ISVs to general availability in April 2026 (Salesforce, Summer '26 ISV strategy). The headline: ISVs can now build, package, and embed interactive Tableau views and AI agents directly inside their Managed Packages. The detail most coverage skips: there's a real difference between "you can package it" and "you should package it." For about 70% of the ISV products I see at Appnigma, you shouldn't. Here's the breakdown of what changed, what it costs, and the small set of products where embedded Tableau actually pays off.

Pro Tip

TL;DR Tableau Next for ISVs is GA as of April 2026. Partners can package interactive analytics views and AI agents into their Managed Packages. Customers see Tableau dashboards inside your app without leaving Salesforce. Cost shifts onto the customer through their Tableau Next license. Not every ISV needs this. The right candidates have a story problem analytics solves that their current Salesforce reports can't.

The capability is the right to include Tableau Next assets (views, dashboards, embedded AI agents) as part of a 2GP Managed Package. Before April 2026, Tableau and AppExchange were two separate distribution stories. A customer installed your Managed Package from AppExchange, then installed Tableau separately, then connected the two themselves. Friction at every step.

After April 2026, the analytics ship in the package. The customer installs your Managed Package, the Tableau views come with it, and the embedded experience appears inside your app's UI the same way a custom Lightning Component does.

Three concrete differences for you, the ISV:

1/ Distribution surface: your analytics views live inside your AppExchange (now AgentExchange) listing. They install with your package, not separately.

2/ AI agent integration: Tableau Next's AI agents are first-class Agentforce components. You can pair them with the Agent components you build so a single agent serves both transactional and analytical questions.

3/ Customer licensing: customers need their own Tableau Next license to view your packaged content. You don't bundle that cost; the customer brings it.

This is where the marketing and the operational reality split. Three patterns where packaging Tableau makes sense:

→ Your product generates data Salesforce reports can't model cleanly. Event data, time-series data, multi-source joins. Sales Cloud reporting collapses on the schema; Tableau handles it.

→ Your customers already pay for Tableau and you're losing pull-through because your dashboards live in a separate tool. Bringing them inside Salesforce removes the context switch.

→ You sell to enterprise specifically (mid-market and SMB customers usually don't have Tableau licensed; packaging Tableau strands them).

If none of those three describe your product, packaging Tableau makes your install heavier and your enterprise sale longer without earning anything. Most ISVs I've talked to fall into "none of those three" without realizing it.

The actual packaging step adds two pieces to your existing 2GP workflow.

You build the Tableau views in your development org with Tableau Next enabled. You then declare them as part of your package in sfdx-project.json and bundle them with sf package version create the same way you bundle Apex and LWCs. The CLI handles the metadata serialization.

``bash sf package version create --package "MyAnalyticsPackage" --installation-key-bypass --wait 30 ``

Behind the scenes, Tableau views ship as a metadata type the CLI recognizes once Tableau Next is enabled in the Dev Hub. The component shows up in the customer's org under your namespace prefix the same way Apex classes do.

What I'd recommend testing before you commit:

1/ Install your package version into a scratch org with Tableau Next enabled 2/ Verify the dashboard renders against sample data 3/ Verify the AI agent invocations work end-to-end 4/ Check the install size; Tableau metadata is not lightweight

You can't bundle Tableau licenses with your package. The customer needs their own Tableau Next subscription. Three real consequences:

→ Your AppExchange listing should state the Tableau Next license requirement clearly. Customers who hit "install" without realizing they need Tableau separately will churn the install in week one.

→ For enterprise deals, the Tableau Next license becomes part of the procurement conversation. Some enterprise procurement teams handle this smoothly. Others treat it as a blocker.

→ Your free trial flow has to handle the case where the customer doesn't have Tableau Next yet. Decide upfront whether to gate the trial on a Tableau Next subscription or run a degraded mode without it.

I lean toward gating the trial. Showing a customer the analytics promise then hiding them behind a separate license purchase is a worse trial experience than just being clear about the prerequisite.

A revenue intelligence product (think Avoma, Gong) ships as a Managed Package with custom objects for meetings, calls, and AI summaries. Customer reps see meetings in a custom Lightning tab. Sales managers wanted dashboards showing rep activity, deal velocity, and conversation themes by quarter.

Before April 2026: the ISV either built dashboards in Salesforce Reports (which choked on time-series joins across meetings and opportunities) or directed customers to export data to Tableau separately (which most customers wouldn't do).

After April 2026: the ISV builds three Tableau Next dashboards in their dev org, packages them, and ships them inside the next version of their Managed Package. Customers with Tableau Next see the dashboards inside the ISV's app, with the data already wired. Customers without Tableau Next see a setup prompt with documentation on how to get it.

The result for the ISV: their enterprise customers see the analytics. Mid-market customers (who don't have Tableau) see the prompt and either ignore it or upgrade.

• [ ] At least one of the three "package Tableau" patterns applies to your product → Yes / No

• [ ] 2GP Managed Package (not 1GP) → Yes / No

• [ ] Dev Hub has Tableau Next enabled → Yes / No

• [ ] Tableau views tested in scratch org with sample data → Yes / No

• [ ] AI agent invocations tested end-to-end → Yes / No

• [ ] AppExchange listing copy states Tableau Next license requirement → Yes / No

• [ ] Trial flow handles customers without Tableau Next licenses → Yes / No

• [ ] Install size measured and acceptable for your target customer → Yes / No

Yes. ISVs cannot bundle Tableau Next licenses with their Managed Package. Customers need their own active Tableau Next subscription to view embedded views. Your AppExchange listing should state this prerequisite plainly so customers don't install without realizing.

No. Tableau Next ISV packaging requires 2GP. If you have an existing 1GP package, migrate before adding Tableau components.

The review process is the same. The reviewer checks Tableau metadata for compliance the same way they check Apex and LWCs. The $999 per submission fee for paid apps doesn't change. See our Security Review guide.

No. Salesforce Reports still work for transactional dashboards over standard objects. Tableau Next earns its place when you need cross-source joins, time-series analysis, or AI-driven insights that Reports can't model.

You can ship Tableau views as part of an add-on module that lists separately on AgentExchange. Customers pay for your add-on module plus their own Tableau Next license. The 15% revenue share applies to your module sales.

You can package Tableau views and Agentforce agent components in the same Managed Package. The agent answers transactional questions; the Tableau views show analytics. Customers get both from one install. See Building Agentforce Components for AgentExchange.

Sunny Chauhan is the founder and CEO of Appnigma AI, a no-code platform that generates Salesforce AppExchange-ready Managed Packages from natural-language prompts. He holds Salesforce certifications in Platform Developer II, Platform App Builder, Administrator, Data Cloud Consultant, and AI Associate. Since launching Appnigma in 2024, his team has helped B2B SaaS companies including Warmly, Hyperbound, Pylon, Seam AI, and Avoma ship native Managed Packages.

Originally published June 17, 2026. Last reviewed June 17, 2026. Capability statements verified against the Salesforce Summer '26 ISV strategy blog and the Tableau Next ISV documentation current as of the published date.

• What is Salesforce AgentExchange (AppExchange rebrand)

• Building Agentforce Components for AgentExchange

• How ISVs Can Embed Agentforce 360 in Their Products

• 1GP to 2GP managed package migration

• Salesforce security review

• AgentExchange Builders Initiative ($50M ISV funding)

1/ Salesforce blog, ISV Strategy for the Summer '26 Release 2/ Aquiva Labs, Summer '26 Salesforce Release Highlights 3/ Salesforce, Summer '26 Release Notes 4/ Salesforce Ben, Summer '26 Release coverage

Which of the three "package Tableau" patterns describes your product, and what's the dashboard your customers most often ask for?