Bing Ads Reporting and Star Schemas in OBIEE

The CData ODBC Driver for Bing Ads is a standard database driver that can integrate real-time access to Bing Ads data into your data warehouse or directly into your reporting tool. This article shows how to bypass the data warehouse and import operational Bing Ads data into Oracle Business Intelligence Enterprise Edition (OBIEE).

See the knowledge base for ODBC integrations with ETL tools like Informatica PowerCenter. For an ETL solution into Oracle Warehouse Builder, use the driver with the Oracle ODBC Gateway to Access Bing Ads Data as a Remote Oracle Database.

Connect to Bing 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.

The Bing Ads APIs use the OAuth 2 standard. To authenticate, you will need valid Bing Ads OAuth credentials and you will need to obtain a developer token. See the Getting Started section in the Bing Ads data provider help documentation for an authentication guide.

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.

Import Bing Ads Metadata

Follow the steps below to use the OBIEE Client Tools to import Bing Ads metadata into an OBIEE repository. You can then integrate Bing Ads data into your business models.

1. Open the Administration Tool and click File -> New Repository.

2. In the Connection Type menu, select ODBC 3.5 and select the CData DSN.
3. Select the metadata types you want to import under the Relational Sources option and then select Bing Ads tables.