Ready to get started?

Learn more about the CData JDBC Driver for DoubleClick (DFP) or download a free trial:

Download Now

ETL Google Ad Manager in Oracle Data Integrator

This article shows how to transfer Google Ad Manager data into a data warehouse using Oracle Data Integrator.

Leverage existing skills by using the JDBC standard to read and write to Google Ad Manager: Through drop-in integration into ETL tools like Oracle Data Integrator (ODI), the CData JDBC Driver for Google Ad Manager connects real-time Google Ad Manager data to your data warehouse, business intelligence, and Big Data technologies.

JDBC connectivity enables you to work with Google Ad Manager just as you would any other database in ODI. As with an RDBMS, you can use the driver to connect directly to the Google Ad Manager APIs in real time instead of working with flat files.

This article walks through a JDBC-based ETL -- Google Ad Manager to Oracle. After reverse engineering a data model of Google Ad Manager entities, you will create a mapping and select a data loading strategy -- since the driver supports SQL-92, this last step can easily be accomplished by selecting the built-in SQL to SQL Loading Knowledge Module.

Install the Driver

To install the driver, copy the driver JAR and .lic file, located in the installation folder, into the ODI userlib directory:

On Unix: ~/.odi/oracledi/userlib On Windows: %APPDATA%\Roaming\odi\oracledi\userlib

Restart ODI to complete the installation.

Reverse Engineer a Model

Reverse engineering the model retrieves metadata about the driver's relational view of Google Ad Manager data. After reverse engineering, you can query real-time Google Ad Manager data and create mappings based on Google Ad Manager tables.

  1. In ODI, connect to your repository and click New -> Model and Topology Objects.
  2. On the Model screen of the resulting dialog, enter the following information:
    • Name: Enter GoogleAdsManager.
    • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
    • Logical Schema: Enter GoogleAdsManager.
    • Context: Select Global.
  3. On the Data Server screen of the resulting dialog, enter the following information:
    • Name: Enter GoogleAdsManager.
    • Driver List: Select Oracle JDBC Driver.
    • Driver: Enter cdata.jdbc.googleadsmanager.GoogleAdsManagerDriver
    • URL: Enter the JDBC URL containing the connection string.

      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.

      Built-in Connection String Designer

      For assistance in constructing the JDBC URL, use the connection string designer built into the Google Ad Manager JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

      java -jar cdata.jdbc.googleadsmanager.jar

      Fill in the connection properties and copy the connection string to the clipboard.

      Below is a typical connection string:

      jdbc:googleadsmanager:InitiateOAuth=GETANDREFRESH
  4. On the Physical Schema screen, enter the following information:
    • Schema (Schema): Enter GoogleAdsManager.
    • Schema (Work Schema): Enter GoogleAdsManager.
  5. In the opened model click Reverse Engineer to retrieve the metadata for Google Ad Manager tables.

Edit and Save Google Ad Manager Data

After reverse engineering you can now work with Google Ad Manager data in ODI. To edit and save Google Ad Manager data, expand the Models accordion in the Designer navigator, right-click a table, and click Data. Click Refresh to pick up any changes to the data. Click Save Changes when you are finished making changes.

Create an ETL Project

Follow the steps below to create an ETL from Google Ad Manager. You will load Orders entities into the sample data warehouse included in the ODI Getting Started VM.

  1. Open SQL Developer and connect to your Oracle database. Right-click the node for your database in the Connections pane and click new SQL Worksheet.

    Alternatively you can use SQLPlus. From a command prompt enter the following:

    sqlplus / as sysdba
  2. Enter the following query to create a new target table in the sample data warehouse, which is in the ODI_DEMO schema. The following query defines a few columns that match the Orders table in Google Ad Manager: CREATE TABLE ODI_DEMO.TRG_ORDERS (NAME NUMBER(20,0),Id VARCHAR2(255));
  3. In ODI expand the Models accordion in the Designer navigator and double-click the Sales Administration node in the ODI_DEMO folder. The model is opened in the Model Editor.
  4. Click Reverse Engineer. The TRG_ORDERS table is added to the model.
  5. Right-click the Mappings node in your project and click New Mapping. Enter a name for the mapping and clear the Create Empty Dataset option. The Mapping Editor is displayed.
  6. Drag the TRG_ORDERS table from the Sales Administration model onto the mapping.
  7. Drag the Orders table from the Google Ad Manager model onto the mapping.
  8. Click the source connector point and drag to the target connector point. The Attribute Matching dialog is displayed. For this example, use the default options. The target expressions are then displayed in the properties for the target columns.
  9. Open the Physical tab of the Mapping Editor and click ORDERS_AP in TARGET_GROUP.
  10. In the ORDERS_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab.

You can then run the mapping to load Google Ad Manager data into Oracle.