Google Ad Manager Reporting and Star Schemas in OBIEE

The CData ODBC Driver for Google Ad Manager is a standard database driver that can integrate real-time access to Google Ad Manager data into your data warehouse or directly into your reporting tool. This article shows how to bypass the data warehouse and import operational Google Ad Manager 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 Google Ad Manager Data as a Remote Oracle Database.

Connect to Google Ad Manager 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.

Google Ads Manager uses the OAuth authentication standard. You can authorize the data provider to access Google Ads Manager as an individual user or with a service account that you create in the Google APIs Console. See the Getting Started section in the 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 Google Ad Manager Metadata

Follow the steps below to use the OBIEE Client Tools to import Google Ad Manager metadata into an OBIEE repository. You can then integrate Google Ad Manager 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 Google Ad Manager tables.