Google Ads connector

Important

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.

The managed Google Ads connector in Lakeflow Connect allows you to ingest data from Google Ads into Azure Databricks.

What to know before you start

Topic	Why it matters
Azure Databricks user persona	The workflow depends on your Azure Databricks user persona: Single-user: An admin user creates a Unity Catalog connection and an ingestion pipeline. Multi-user: An admin user creates a connection for non-admin users to create pipelines with.
Authentication method	The steps to create a connection depend on the authentication method you choose. For supported methods, see Authentication methods.
Interface	The steps to create a pipeline depend on the interface.
Ingestion frequency	The pipeline schedule depends on your latency and cost requirements.
Common patterns	Depending on your ingestion needs, the pipeline might use configurations like history tracking, column selection, and row filtering. Supported configurations vary by connector. See Feature availability.

The following table provides an overview of the end-to-end Google Ads ingestion flow, based on user type:

User	Steps
Admin	Configure Google Ads to enable authentication from Azure Databricks. See Configure OAuth for Google Ads ingestion. Use Catalog Explorer to create a connection to Google Ads so that non-admins can create pipelines. See Google Ads.
Non-admin	Use any supported interface to create a pipeline from an existing connection. See Ingest data from Google Ads.

Was this page helpful?