<< Back

5 Things to Know about the Tableau 9.1 Web Data Connector

1. What is it?

Tableau Web Data Connector Screen

The Tableau Web Data Connector (WDC) is essentially the Extract API embedded directly into Tableau Desktop with javascript used as the wrapper to send data to it. This means that connector authors around the community can easily build Tableau connectors for any data source accessible via javascript but not currently listed in the native Tableau connections.

When you think javascript you may think that these are going to be connections to websites, web services, APIs, etc. and you’d be right, however javascript is able to work with local files too meaning WDCs could parse local XML & JSON files for example.

2. So I need to learn javascript?

WDC List

In order to make use of a WDC you need no programming experience what so ever. If you’re aware of a WDC you want to make use, of all you need to know is the URL to access it at. Simply select ‘Web Data Connector’ from the connection list, enter or paste the URL of the WDC into the appropriate window and follow instructions presented by the WDC. Each WDC is unique and its interface depends on how the author has designed it.

If you wish to create your own WDC you will need to know some javascript, although that in no way means you need to be an expert before you get started. If you have even just a small amount of programming experience you’ll find it relatively straight forward to apply it to Javascript. Indeed one of the most popular programming techniques is the ‘Google programmer’, somebody who solves problems and learns methods by simply searching Google. Finally if you want to get into WDC programming but are totally lost and you’ll be at the Tableau Conference 2015 in Vegas in October be sure to go to my session The New Tableau Web Data Connector: APIs, JSON & Javascript for Dummies.

3. So how is the data stored? Is it live?

While the connector may be pointed at what feels like a live database (via a web service API for instance) the data is always stored locally as a Tableau Data Extract and so is only ‘live’ at the point of connection. That doesn’t mean that the data can’t be refreshed either manually or scheduled on a Tableau Server (version 9.1 or greater), as long as the connector author has stored the relevant authentication credentials as required to continually access the resource.

4. Availability?

The Tableau Web Data Connector is expected to be released with Tableau 9.1 and as I type is currently available for testing by end users through the beta program (to get access to the beta program as a Tableau customer contact your account manager or email beta@tableau.com). While presence in the beta program doesn’t guarantee release in 9.1 it is a good sign. Really it depends on user feedback and unexpected instability from working with other people’s code.

5. Are there any prebuilt connectors I can play with?

Sure there are! If there’s anything the Tableau community is known for it’s adopting new versions fast (even betas) and making the most of new features.

From around the community you’ll find:

Quandl – http://www.theinformationlab.co.uk/data/quandl.html
Boris Bikes – http://jdunkerleytableau.azurewebsites.net/Bikes
Import.IO – http://connectors.poc.interworks.com/importio
Mapbox Directions (car, bike & walking) – http://www.theinformationlab.co.uk/data/directions.html
Fitbit – http://www.theinformationlab.co.uk/data/fitbit.html
Moves – http://www.theinformationlab.co.uk/data/moves.html
Strava – http://www.theinformationlab.co.uk/data/strava.html

To make use of one of these connectors fire up your latest beta copy of Tableau 9.1, select Web Data Connector from the connections menu, copy and paste one of the above URLs into the connector screen and follow instructions.

(If you’re a WDC author and I’ve missed you off drop the link in a comment below and I’ll add your handywork to the list)

As the beta progresses you’ll also find WDCs posted for testing to the beta community group (email beta@tableau.com for access).

Craig Bloodworth

York, UK

12 thoughts on “5 Things to Know about the Tableau 9.1 Web Data Connector

  1. Great article, Craig!

    We focus on the data that drives storytelling through reports, dashboards or visualizations. Tools like Tableau’s Web Data Connectors (WDC) will go a long way to help with storytelling. We are interested in hearing from people what data sources they are interested in generally and specifically what WDC they would want. Feel free to reach out at tableau@openbridge.com.

    Best,
    Thomas Spicer
    CEO at http://www.openbridge.com

  2. Hi Craig,

    I’m trying to use the fitbit connector to log in all of my colleagues as separate data sources then join to produce a team viz. First extract works fine, but then second one always hangs on extract…is this specifically disallowed by either FitBit or Tableau?

  3. Really like the prebuilt connectors!

    Does anyone how to connect Google sheets with Tableau on a Mac?

    Thanks
    Johan

  4. I came across your blog as I was searching for WDC examples and your name was all over the ones listed in community. It looks like I missed out on your awesome seminar that discussed this. Is there any way to access a recording, perhaps? Or do you know of any written primers? I have deep knowledge in the API I’m looking to connect, but know virtually nothing about how Tableau or the WDC works. Don’t really know much about javascript either, for that matter.

  5. Hey,

    When I use the Informationlab web connector for Quandl I am limited to 50 calls/day as an anonymous user. Is there a way to use the web connector through my Quandl account, thus upgrading to 50,000/day?

    Thanks

  6. Hie,
    Is there any limitation of how many observations of data that we can get into tableau by WDC..???

    Please respond.

  7. I have a problem with creating formula fields on a Web Connector to Survey Monkey. I get an error saying that the functions like SUM() are not recognised. Is this a problem with Tableau or Survey Monkey?

Leave a Reply

Your email address will not be published. Required fields are marked *