Connect to and Query Twitter Ads Data in QlikView over ODBC

Ready to get started?

Download for a free trial:

Download Now

Learn more:

Twitter Ads ODBC Driver

The Twitter Ads ODBC Driver is a powerful tool that allows you to connect with live data from Twitter Ads, directly from any applications that support ODBC connectivity.

Access Twitter Ads data like you would a database - read, write, and update Twitter Ads Accounts, Campaigns, Stats, Tweets, etc. through a standard ODBC Driver interface.



Create data visualizations with Twitter Ads data in QlikView.

The CData ODBC drivers expand your ability to work with data from more than 200 data sources. QlikView is a business discovery platform that provides self-service BI for all business users in an organization. This article outlines simple steps to connect to Twitter Ads data using the CData ODBC driver and create data visualizations in QlikView.

The CData ODBC drivers offer unmatched performance for interacting with live Twitter Ads data in QlikView due to optimized data processing built into the driver. When you issue complex SQL queries from QlikView to Twitter Ads, the driver pushes supported SQL operations, like filters and aggregations, directly to Twitter Ads and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze Twitter Ads data using native QlikView data types.

Connect to Twitter Ads as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

All tables require authentication. You must use OAuth to authenticate with Twitter. OAuth requires the authenticating user to interact with Twitter using the browser. For more information, refer to the OAuth section in the Help documentation.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Populate a Chart with Twitter Ads Data

The steps below supply the results of an SQL query to a visualization in QlikView. In this article, you will create a bar chart with the query below:

SELECT EntityId, Entity FROM AdStats WHERE Entity = 'ORGANIC_TWEET'
  1. Click File -> Edit Script (or click the Edit Script button in the Toolbar).
  2. On the Data tab, select ODBC in the Database menu and click Connect.
  3. Select the DSN (CData TwitterAds Sys) in the resulting dialog. A command like the following is generated: ODBC CONNECT TO [CData TwitterAds Sys];
  4. Enter the SQL query directly into the script with the SQL command (or click Select to build the query in the SELECT statement wizard). SQL SELECT EntityId, Entity FROM AdStats WHERE Entity = 'ORGANIC_TWEET';

    Where possible, the SQL operations in the query, like filters and aggregations, will be pushed down to Twitter Ads, while any unsupported operations (which can include SQL functions and JOIN operations) will be managed client-side by the CData SQL engine embedded in the driver.

  5. Close the script editor and reload the document to execute the script.
  6. Click Tools -> Quick Chart Wizard. In the wizard, select the chart type. This example uses a bar chart. When building the chart, you have access to the fields from Twitter Ads, typed appropriately for QlikView, thanks to built-in dynamic metadata querying.
  7. When defining Dimensions, select EntityId in the First Dimension menu.
  8. When defining Expressions, click the summary function you want and select Entity in the menu.
  9. Finish the wizard to generate the chart. The CData ODBC Driver for Twitter Ads connects to live Twitter Ads data, so the chart can be refreshed to see real-time changes. Live connections are possible and effective, thanks to the high-performance data processing native to CData ODBC Drivers.