Skip to main content
Last updated on

Google Search Console connector FAQ

Beta

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Google Search Console from the Previews page. See Manage Databricks previews.

This page answers frequently asked questions about the managed Google Search Console ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.

Which tables does the connector support?​

The connector supports 15 source tables: sites, sitemaps, search_analytics_all_fields, search_analytics_by_country, search_analytics_by_date, search_analytics_by_device, search_analytics_by_page, search_analytics_by_query, search_analytics_page_report, search_analytics_site_report_by_page, search_analytics_site_report_by_site, hourly_search_analytics_page_report, hourly_search_analytics_site_report_by_page, hourly_search_analytics_site_report_by_site, and custom_report. The custom_report table runs a daily report with the dimensions, search types, and aggregation type that you select.

For full schema details, see Destination table schemas.

Can I ingest a report with my own dimensions and search types?​

Yes. Use the custom_report table, and set the dimensions and search_types connector options. Optionally, set aggregation_type and data_state. The report includes the date dimension even if you don't list it. See Custom reports.

How far back can the connector ingest data?​

For incremental tables, the first sync ingests records from the previous 500 days, and each later sync ingests records after the last run. The sites and sitemaps tables reingest all available records on every run.

To limit the initial lookback window, set the start_date connector option in your pipeline definition. See Connector options.

Which authentication methods does the connector support?​

The connector supports OAuth 2.0 user-to-machine (U2M) and Service Account (OAuth 2.0 machine-to-machine, or M2M) authentication. Basic authentication (username/password or API key) is not supported.

Use Service Account authentication for automated, unattended pipelines or for Google Workspace environments that use domain-wide delegation to impersonate a specific user. Use OAuth U2M to authenticate as your own Google identity interactively.

For setup instructions, see Configure authentication to Google Search Console.

Can the connector ingest data from multiple site URLs in one pipeline?​

Yes. Specify multiple values in the site_urls connector option. The connector creates a partition for each site URL and ingests all tables for each property. All destination tables include a site_url column to identify the source property.

Which search types does the connector ingest?​

The search types ingested depend on the table:

  • Daily search_analytics_all_fields and search_analytics_by_query tables: web, news, image, video.
  • Daily search_analytics_by_country, search_analytics_by_date, search_analytics_by_page, and search_analytics_site_report_by_site tables: web, news, image, video, discover, googleNews.
  • Daily search_analytics_by_device, search_analytics_page_report, and search_analytics_site_report_by_page tables: web, news, image, video, googleNews.
  • Hourly tables: data is available for web and googleNews search types only.
  • custom_report table: the search types that you list in the search_types connector option.

Why does the connector not ingest data for recent dates?​

Google Search Console Search Analytics data has an approximate delay of two to four days. Clicks, impressions, click-through rate (CTR), and position metrics for recent dates appear in the API after this delay. The connector ingests data as it becomes available in subsequent pipeline runs.

On this page