Google PageSpeed Insights to Databricks SQL Warehouse Integration
AI-first ETL from Google PageSpeed Insights into Databricks SQL Warehouse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Google PageSpeed Insights into Databricks SQL Warehouse
Datrise syncs Google PageSpeed Insights's audits, lab metrics, field metrics, opportunities, page URLs, and performance scores into Databricks SQL Warehouse as a Delta Lake table per source entity. Flexible or custom fields land in VARIANT or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses a Delta MERGE on stable id, with change history available via time travel, so re-runs update only what changed. Delta partitioning by load date with OPTIMIZE/Z-ORDER on query keys. Datrise writes Unity Catalog–governed Delta tables, so lineage and permissions are managed centrally rather than per-notebook.
Ideal for lakehouse analytics and ML feature tables on Databricks.
Endpoints
Google PageSpeed Insights: Page performance and Core Web Vitals audits.
Databricks SQL Warehouse: Lakehouse SQL endpoints over Delta tables.
How Google PageSpeed Insights entities map to Databricks SQL Warehouse
| Google PageSpeed Insights entity | Databricks SQL Warehouse object | Notes |
|---|---|---|
| audits | google_pagespeed_insights_audits | id PK · custom fields → VARIANT or STRUCT columns |
| lab metrics | google_pagespeed_insights_lab_metrics | id PK · linked to google_pagespeed_insights_audits |
| field metrics | google_pagespeed_insights_field_metrics | id PK · linked to google_pagespeed_insights_audits |
| opportunities | google_pagespeed_insights_opportunities | id PK · linked to google_pagespeed_insights_audits |
FAQ
How does Datrise handle Google PageSpeed Insights's custom fields in Databricks SQL Warehouse?
Flexible values are stored as VARIANT or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Databricks SQL Warehouse types.
How does the Google PageSpeed Insights to Databricks SQL Warehouse sync stay up to date?
It runs incrementally — Datrise uses a Delta MERGE on stable id, with change history available via time travel.
Related pipelines
More destinations for Google PageSpeed Insights
- Google PageSpeed Insights → ClickHouse
- Google PageSpeed Insights → DuckDB
- Google PageSpeed Insights → Amazon Athena
- Google PageSpeed Insights → Amazon S3 Data Lake
- Google PageSpeed Insights → Azure Data Lake Storage
- Google PageSpeed Insights → Azure Synapse
- Google PageSpeed Insights → Spreadsheets
- Google PageSpeed Insights → Airtable
- Google PageSpeed Insights → CSV Files
- Google PageSpeed Insights → MongoDB
- Google PageSpeed Insights → Supabase
- Google PageSpeed Insights → Neon
More sources for Databricks SQL Warehouse
- Greenhouse → Databricks SQL Warehouse
- Gridly → Databricks SQL Warehouse
- Harness → Databricks SQL Warehouse
- Harvest Forecast → Databricks SQL Warehouse
- Heap → Databricks SQL Warehouse
- Hellobaton → Databricks SQL Warehouse
- Heroku → Databricks SQL Warehouse
- PostgreSQL → Databricks SQL Warehouse
- Hubplanner → Databricks SQL Warehouse
- Impact → Databricks SQL Warehouse
- Import API → Databricks SQL Warehouse
- Instagram → Databricks SQL Warehouse
Early access
Connect Google PageSpeed Insights to Databricks SQL Warehouse the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.