Thanks for your interest in submitting a connector for Tableau Exchange. This document describes the steps and assets required to submit your connector to Tableau Exchange. While this is a self-service process, feel free to contact us if you need assistance.
Best regards – The Tableau Team
In this section
These are the steps you’ll take to prepare your connector and get it added to the Tableau Exchange:
Building a connector generally takes two to six weeks, depending on complexity. Then, before it can be published to the Tableau Exchange, you’ll submit it for approval. The approval process typically takes another two to six weeks.
Joining the Tableau Developer Program isn’t required, but it does give you access to a free personal development sandbox with the latest pre-release version of Tableau Online.
Use the information in the Connector SDK documentation to build your connector. If you have issues with the SDK or need help, submit an issue through our GitHub issues page and include the required artifacts with the issue.
Be sure to test your connector with the TDVT suite to ensure that your connector meets our guidelines for connector functionality.
Note: The Tableau Exchange no longer accepts submissions of ODBC connectors. Only JDBC connectors are accepted.
Join the Technology Track on our Tableau Partner Network (TPN) after you’ve built your integration and are passing 90% of TDVT results (all tests marked as required should pass or should be acknowledged as not supported or a known bug for the underlying data source). By joining the TPN, you allow us to discuss confidential information with you and enable us to promote your products through our marketing channels, like the Tableau Exchange.
In order to be approved to submit your connector to the Tableau Exchange, complete the following tasks with the TPN.
Sign in to the Partner Portal, then click on Partner Solutions to submit your connector for review. At this stage, you’ll need to provide a description, a brief demo, and a data sheet showing how your connector works with Tableau. You’ll later provide more materials and details about your connector to add it to the Tableau Exchange.
All technical partners who want to add connectors to the Tableau Exchange must join the Tableau Partner Technical Support Alliance Network (TSANet). TSANet provides a platform that allows Tableau to address customer issues in collaboration with our partners.
After the TPN has reviewed your connector, we will send you a copy of the Tableau Exchange Agreement.
All Tableau Exchange Agreements are processed through Service Now. A copy of the Tableau Exchange agreement should be reviewed and approved by the person who will process the agreement on your side. To process the agreement, we will need:
Share your GitHub username or email with your TPN account manager, and we will create a GitHub repository for you to share your source code and test artifacts.
Provide the unzipped source files for your connector so we can review each file.
The TDVT suite produces a number of important files required for a review. Provide the following files.
TDVT tests can be skipped for extract-only connectors.
In most cases, TDVT should be passing more than 90% of test cases to be accepted. All tests marked as required should pass or should be acknowledged as not supported or a known bug for the underlying data source.
Provide the following artifacts to show that your connector has passed manual QA tests.
List of all vendor-defined fields (vendor1 , vendor2, and vendor3 in a .tcd file, or fields with a “v-” prefix in connection fields) in PDF, DOC, or DOCX format. Define what the fields are, give sample input, and confirm that they can never contain personally identifiable information (PII).
Include a screenshot or text file of the full output of the command
jarsigner -verify path_to_taco -verbose -certs -strict to show that your connector is signed by a trusted certificate authority. For more information, see Get your connector signed.
As part of the connector review we will perform a security review of your connector. Read the Security Considerations to make sure that your connector will be accepted. Connectors with security vulnerabilities will not be approved for the Tableau Exchange until a fix is provided, and connectors already posted to the Tableau Exchange that are found to have security vulnerabilities will be pulled until a fix is provided.
All of the following materials are required for submission of a connector to the Tableau Exchange unless stated otherwise. Submitting these materials and signing the Tableau Exchange Agreement does not guarantee the addition of a connector to the Tableau Exchange.
Listing name: Include the name for your application/database to which the connector connects.
Icon: Submit an icon representing your application or database. This should be easily recognizable as a representation of your application or database. Must be 280x280 pixels and in PNG, JPEG, GIF, or SVG format.
Short description: Briefly describe details about your connector that are most relevant for customers. This description displays on the main Connectors page of the Tableau Exchange. Maximum 116 characters. Plain text only.
Example: This connector provides a smooth and easy way to connect to Google Big Query. By using this connector, customers can leverage Google’s internal storage and extract APIs, which offer up to 10x performance increases when extracting large amounts of data. This connector also allows users to use custom OAuth, which is not currently supported natively with an Other JDBC connection.
Markdown for this field is supported. We encourage you to submit a robust long description so that customers understand why they should download your connector.
To make things easy, we created templates for your custom installation instructions. These templates, linked below, are markdown friendly. If you have additional installation instructions, append them below the Tableau installation instructions.
TACO file: Upload the TACO file for your connector. Information in this file should match the information submitted on the form. TACO files must be signed by a certificate authority to be accepted. The certificate must be signed with a timestamp that will be valid for the next 5 years.
Terms of service:Include an agreement between you and the users of your connector. Includes regulations on how your connector can be used, usage restrictions, availability, liability provisions, and so on. The same terms of service can be used across multiple listings on the Tableau Exchange. PDF or URL.
Support URL: Include a link to a website or email address where users can get help troubleshooting issues. Preferably a page where users can file a support ticket or the email address of your support team. This should not be the home page of your website.
Driver download: Include either a link to download the driver or brief instructions on how to get the driver.
Beta status: Select the Beta checkbox if you want to display a “Beta” badge on your connector. There is no official beta program for connectors. It’s up to you to decide when your connector is ready to go from beta to general availability.
Supported languages: Select English.
Pricing model: Select Free. All connectors are free at this time.
Localization options: By default, the information you submit about your connector will be localized, with the exception of the connector name. To opt out of localization, select Do not localize any fields. To localize your connector name, select Localize listing name.
Partners are welcome to publish blog posts and press releases announcing the availability of their connector on the Tableau Exchange. Marketing materials should specify the joint-value proposition of the offering and tell the story of how your Tableau integration is uniquely suited to solve customer challenges.
Once customers are benefitting from your Tableau integration, we’ve found public customer case studies to be the most impactful method for promoting joint-solutions. The best performing customer case studies are evergreen and applicable to a broad number of customers by demonstrating how your integration solves for pain points commonly experienced across your industry. Typically, case studies are hosted on our partner’s sites.
Once your connector is approved, you will receive an email notification. You can now publish your Tableau-approved go-to-market materials to let your customers know that the connector is available.
If you need to update your connector, you will need to update your GitHub repo with the changes and then publish the updated connector on the Exchange listing. Any changes you make will require updated artifacts and approval before they are published.
If your connector is a beta release, be sure to update the connector when you are ready to move it from beta to general availability.
Here is a list of review materials needed for connector updates depending on the extent of the changes.
Note: The review materials are additive. A connector with changes on both list B and C require TDVT and manual test results, for example.
Forbidden Changes The following changes are forbidden, and will never be approved:
Certain cosmetic or light changes do not trigger any additional required materials.
The following changes will require a new round of TDVT tests and a review from a Tableau dev:
The following changes will require a new set of manual test results and a review from a Tableau dev to ensure no breaking change:
The above lists are guidelines and Tableau reserves the right to request more review materials if needed.
Once your updates have been uproved, you need to publish the updated connector on the Exchange.