Skip to main content

Building pipelines with Google Ads Reader

You can read from Google Ads using the Google Ads Reader and write to any target supported by Striim. Typically, you will set up pipelines in two phases—initial load, followed by continuous incremental replication—as explained in Pipelines.

  • For initial load, use Google Ads Reader in Initial Load mode to create a point-in-time copy of selected objects at the target.

  • After initial load has completed, start continuous replication by reading new or changed records created in the same objects after the initial load began, then writing those changes to the target. For real-time continuous replication of new source data, use the Google Ads Reader in Incremental mode.

You can use automated pipeline wizards to build Google Ads pipelines that Striim manages end-to-end, or you can manually create separate applications for initial load and continuous incremental replication and manage the lifecycle yourself. Since the Google Ads Reader supports both initial load and continuous replication, you can handle both with a single application.

Using an automated pipeline wizard: if you want to build near-real-time pipelines from Google Ads and write to a supported target, we recommend using an automated pipeline wizard with a Google Ads Reader source. These wizards perform the following steps automatically:

  • Create two applications: one for initial load and the other for continuous incremental replication (polling).

  • Create a schema and tables in the target that match the objects to be synced from Google Ads.

  • Run the initial-load application to copy existing data from Google Ads to the target.

  • When initial load completes, run the incremental application to replicate new or changed records using the configured watermark field and polling interval.

Not using an automated pipeline wizard: if your use case or policies do not allow using an automated pipeline, create separate applications for initial load and continuous replication:

  • Before performing initial load, identify a stable, monotonically increasing watermark field for each object (for Google Ads this is typically the Date field).

  • Create a schema and tables in the target and perform initial load: use a wizard with a Google Ads Reader source. (Alternatively, you may pre-create target tables using native or third-party utilities.)

  • Perform an initial load when the schema and tables already exist in the target: use a wizard with a Google Ads Reader source configured for full export.

  • Switch from initial load to continuous replication: Provide the last successful watermark value from the initial load as the starting offset.

  • Replicate new data: use a wizard with a Google Ads Reader source configured for incremental polling (set the watermark field and polling interval). Configure the target for upsert semantics using appropriate key columns.

Alternatively, instead of using wizards, you can create applications using Flow Designer, TQL, or Striim’s REST API.

Pre-requisite - The initial setup and configuration you do in Google Ads are described in the Initial setup section.

Create a Google Ads Reader application using the Flow Designer

This procedure outlines how to use Striim’s Flow Designer to build and configure data pipelines. Flow Designer enables you to visually create applications with minimal or no coding.

  1. Go to the Apps page in the Striim UI and click Start from scratch.

  2. Provide the Name and Namespace for your app. The namespace helps organize related apps.

  3. In the component section, expand Sources, and enter a keyword such as Google Ads Reader in the search field to filter available sources.

  4. Select the desired source (Google Ads).

  5. In the properties panel, provide the properties for the reader (for example: Mode, Polling interval, Tables, Incremental load marker = Date, and any required OAuth credentials or connection profile).

  6. Click Save to complete the properties configuration.

  7. You can drag and drop processors, enrichers, and targets to complete your pipeline logic.

  8. Once done, deploy and start the application to begin data flow.

Create a Google Ads Reader application using TQL

The following sample TQL uses Striim’s Google Ads Reader to read selected resources.

CREATE APPLICATION GoogleAds_App;

CREATE SOURCE gads_src USING Global.GoogleAdsReader (
  Mode: 'Automated',
  pollingInterval: '1d',
  tables: 'Resources;CampaignStatsReport',
  IncrementalLoadMarker: 'Date',
  syncMode: 'LASTPOSITION',
  clientId: '<CLIENT_ID>',
  clientSecret_encrypted: 'true',
  clientSecret: '<CLIENT_SECRET>',
  refreshToken_encrypted: 'true',
  refreshToken: '<REFRESH_TOKEN>',
  clientCustomerId: '<CLIENT_CUSTOMER_ID>',
  ManagerId: '<MANAGER_ID>',
  autoTokenRenewal: true,
  ConnectionPoolSize: '20',
  migrateSchema: true,
  threadPoolCount: '10'
)
OUTPUT TO gads_out;

END APPLICATION GoogleAds_App;