Skip to main content

Google Ads connector limitations

Beta

This feature is in Beta.

Learn about known limitations when using the managed Google Ads connector in Lakeflow Connect.

General limitations​

  • When you run a scheduled pipeline, alerts don't trigger immediately. Instead, they trigger when the next update runs.
  • When a source table is deleted, the destination table is not automatically deleted. You must delete the destination table manually. This behavior is not consistent with Spark Declarative Pipelines on Lakeflow behavior.
  • During source maintenance periods, Databricks might not be able to access your data.
  • If a source table name conflicts with an existing destination table name, the pipeline update fails.
  • Multi-destination pipeline support is API-only.
  • You can optionally rename a table that you ingest. If you rename a table in your pipeline, it becomes an API-only pipeline, and you can no longer edit the pipeline in the UI.
  • If you select a column after a pipeline has already started, the connector does not automatically backfill data for the new column. To ingest historical data, manually run a full refresh on the table.
  • Databricks can't ingest two or more tables with the same name in the same pipeline, even if they come from different source schemas.
  • The source system assumes that the cursor columns are monotonically increasing.
  • The connector ingests raw data without transformations. Use downstream Spark Declarative Pipelines on Lakeflow pipelines for transformations.

Supported tables​

The connector supports the predefined tables listed in Google Ads connector reference, as well as custom report tables that you define using Google Ads resource fields, segments, and metrics.

Incremental ingestion limitations​

  • Resource tables (such as customer, campaign, ad_group, and ad) are fully refreshed on each pipeline update. Only report tables support incremental ingestion.
  • History tracking (SCD type 2) is not supported for any table. Only the current state is stored.
  • The sync_start_date and lookback_window_days options apply only to report tables. A pipeline that sets them on a resource or event table is rejected when you save it.
  • Report dates are in the time zone of the Google Ads account, and each update reads dates through the current date in that time zone.
  • For a custom report segmented by segments.week or segments.month, the sync_start_date and the lookback window are rounded down to the start of the week (Monday) or month, so each update re-reads whole periods.
  • If an update fails partway through a report table, the next update starts from the last period that was fully ingested, minus the lookback window. Dates are not skipped.
  • Event tables (call_view, lead_form_submission, local_services_lead, and local_services_lead_conversation) are fully refreshed on each pipeline update and contain only the rows that Google Ads returns. For example, the Google Ads API returns lead form submissions for only the last 60 days, so older submissions are removed from the destination table on the next update. For details, see About lead form assets in the Google Ads Help Center.

Late data changes and deleted rows limitations​

  • Each pipeline update re-reads only the lookback window of report data. Changes that Google Ads makes to data older than the lookback window are not captured. To capture them, run a full refresh of the table.
  • The Google Ads API omits report rows whose selected metrics are all zero. Report tables do not contain rows for periods with no activity. For details, see Zero metrics in the Google Ads API documentation.
  • The connector does not delete rows from report tables. If Google Ads later restates an ingested row to all-zero metrics, the API stops returning that row, and the destination table keeps its earlier values. To remove these rows, run a full refresh of the table.

Data retention limitations​

  • Google Ads retains hourly-, daily-, and weekly-segmented performance data for 37 months. The connector can't ingest data that Google Ads no longer serves, so a full refresh removes any older history that the destination table holds. A custom report segmented by segments.date or segments.week is rejected if its sync_start_date is more than 37 months ago. For details, see the Google Ads data retention policy announcement. For custom reports that need older data, use segments.month.
  • The click_report table can ingest only the last 88 days of clicks, because Google Ads serves click data for only the last 90 days. An initial sync or a full refresh starts no earlier than 88 days ago, even if sync_start_date is earlier. If the pipeline does not run successfully for more than 88 days, the clicks between the last successful update and 88 days ago are not ingested, because Google Ads no longer serves them.

Table configuration limitations​

  • A custom report's resource, resource_fields, segments, and metrics, and a report table's sync_start_date, can't change on an existing table. After you change one of them, the next update of the table fails and asks for a full refresh, and the table keeps its existing data until you run one. A full refresh re-ingests the table with the new configuration. Reordering fields is not a change. Removing an option is a change, and so is a change to a sync_start_date that the table inherits from its schema or from the first table or schema in the pipeline specification that sets Google Ads connector options.
  • Row filters are not supported on report tables. The lookback window re-reads rows to update their metrics, and a row filter on a metric column can stop an updated row from being ingested, which leaves its earlier values in the table.
  • Overriding sequence_by is not supported on any table, and overriding primary_keys is not supported on report or resource tables. The connector's default keys and sequencing let lookback re-reads update existing rows and keep each resource keyed on its own ID.
  • custom_report_options applies only to the custom_report table.
  • A schema or catalog in the pipeline specification can't set row_filter, primary_keys, sequence_by, or custom_report_options, because these settings would apply to the report tables it contains. A catalog also can't set lookback_window_days or sync_start_date. Set these on a schema or on individual report tables instead.
  • A pipeline that sets any of these unsupported settings is rejected when you create or edit it, and the error lists each object with the settings to remove. A table, schema, or catalog that doesn't set its own table_configuration inherits the pipeline-level table_configuration, so row_filter, primary_keys, and sequence_by can also come from there. Connector options have no pipeline-level setting. A report table that doesn't set lookback_window_days or sync_start_date itself, and whose schema doesn't set it, uses the value from the first table or schema in the pipeline specification that sets Google Ads connector options. To keep each table's values predictable, set them on every report table or schema. custom_report_options always comes from the table itself.
  • Column selection can't remove a table's primary key or cursor columns. Adding columns to include_columns on an existing table requires a full refresh of the table.