Stream Google Ad Manager Data into Apache Kafka Topics

Apache Kafka is an open-source stream processing platform that is primarily used for building real-time data pipelines and event-driven applications. When paired with the CData JDBC Driver for DoubleClick (DFP), Kafka can work with live Google Ad Manager data. This article describes how to connect, access and stream Google Ad Manager data into Apache Kafka Topics and to start Confluent Control Center to help users secure, manage, and monitor the Google Ad Manager data received using Kafka infrastructure in the Confluent Platform.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live Google Ad Manager data. When you issue complex SQL queries to Google Ad Manager, the driver pushes supported SQL operations, like filters and aggregations, directly to Google Ad Manager and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying allows you to work with and analyze Google Ad Manager data using native data types.

Prerequisites

Before connecting the CData JDBC Driver for streaming Google Ad Manager data in Apache Kafka Topics, install and configure the following in the client Linux-based system.

1. Confluent Platform for Apache Kafka
2. Confluent Hub CLI Installation
3. Self-Managed Kafka JDBC Source Connector for Confluent Platform

Define a New JDBC Connection to Google Ad Manager data

1. Download CData JDBC Driver for DoubleClick (DFP) on a Linux-based system
2. Follow the given instructions to create a new directory extract all the driver contents into it:
   1. Create a new directory named Google Ad Manager mkdir GoogleAdsManager
   2. Move the downloaded driver file (.zip) into this new directory mv GoogleAdsManagerJDBCDriver.zip GoogleAdsManager/
   3. Unzip the CData GoogleAdsManagerJDBCDriver contents into this new directory unzip GoogleAdsManagerJDBCDriver.zip
3. Open the Google Ad Manager directory and navigate to the lib folder ls cd lib/
4. Copy the contents of the lib folder of Google Ad Manager into the lib folder of Kafka Connect JDBC. Check the Kafka Connect JDBC folder contents to confirm that the cdata.jdbc.googleadsmanager.jar file is successfully copied into the lib folder cp * ../../confluent-7.5.0/share/confluent-hub-components/confluentinc-kafka-connect-jdbc/lib/ cd ../../confluent-7.5.0/share/confluent-hub-components/confluentinc-kafka-connect-jdbc/lib/
5. Install the CData Google Ad Manager JDBC driver license using the given command, followed by your Name and Email ID java -jar cdata.jdbc.googleadsmanager.jar -l
6. Enter the product key or "TRIAL" (In the scenarios of license expiry, please contact our CData Support team)
7. Start the Confluent local services using the command: confluent local services start

   This starts all the Confluent Services like Zookeeper, Kafka, Schema Registry, Kafka REST, Kafka CONNECT, ksqlDB and Control Center. You are now ready to use the CData JDBC driver for Google Ad Manager to stream messages using Kafka Connect Driver into Kafka Topics on ksqlDB.

8. Create the Kafka topics manually using a POST HTTP API Request: curl --location 'server_address:8083/connectors' --header 'Content-Type: application/json' --data '{ "name": "jdbc_source_cdata_googleadsmanager_01", "config": { "connector.class": "io.confluent.connect.jdbc.JdbcSourceConnector", "connection.url": "jdbc:googleadsmanager:; InitiateOAuth=GETANDREFRESH", "topic.prefix": "googleadsmanager-01-", "mode": "bulk" } }'

   Let us understand the fields used in the HTTP POST body (shown above):

   • connector.class: Specifies the Java class of the Kafka Connect connector to be used.
   • connection.url: The JDBC connection URL to connect with Google Ad Manager data.

     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.

     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.

   • topic.prefix: A prefix that will be added to the Kafka topics created by the connector. It's set to "googleadsmanager-01-".
   • mode: Specifies the mode in which the connector operates. In this case, it's set to "bulk", which suggests that the connector is configured to perform bulk data transfer.

   This request adds all the tables/contents from Google Ad Manager as Kafka Topics.

   Note: The IP Address (server) to POST the request (shown above) is the Linux Network IP Address.

9. Run ksqlDB and list the topics. Use the commands: ksql list topics;
10. To view the data inside the topics, type the SQL Statement: PRINT topic FROM BEGINNING;

Connecting with the Confluent Control Center

To access the Confluent Control Center user interface, ensure to run the "confluent local services" as described in the above section and type http://<server address>:9021/clusters/ on your local browser.

Get Started Today

Download a free, 30-day trial of the CData JDBC Driver for DoubleClick (DFP) and start streaming Google Ad Manager data into Apache Kafka. Reach out to our Support Team if you have any questions.