Every metric & dimension
Pull the full Core Web Vitals field set - sessions, events, dimensions, and breakdowns - not just a fixed preset, so your reports and models are never missing a metric.
Core Web Vitals
Core Web Vitals
AnalyticsDataddo extracts the full Core Web Vitals metric and dimension set - sessions, events, rankings, behavior - and delivers it wherever your team needs it: into AI tools and agents, your warehouse like Snowflake and BigQuery, BI dashboards, and your marketing and CRM tools. Blend it with every other data source, backfill full history, and keep it fresh on your schedule - all fully managed, with the data plane running where you choose. No pipelines to build, no lock-in.
YOUR ANALYTICS SOURCE OF TRUTH
Turn Core Web Vitals into reporting your whole team trusts
Analytics data is only useful when it's complete, clean, and current. Dataddo extracts the full Core Web Vitals data model, governs it, and serves it to every warehouse, dashboard, AI tool, and downstream system - continuously and without manual exports.
Blend across every source
Combine Core Web Vitals with your marketing, product, and CRM data so cross-channel and full-funnel analytics live in one place.
Backfill full history
Load historical Core Web Vitals data beyond the platform's retention window, so trend, cohort, and year-over-year analysis holds up.
Model & clean before load
Normalize naming, time zones, and units, and let the Data Quality Firewall stop bad rows before Core Web Vitals data reaches your reports.
Fresh on your schedule
Incremental, scheduled syncs keep Core Web Vitals data current - as often as hourly - without manual exports or full reloads.
Governed & monitored
Delivery alerts and quality checks catch gaps in Core Web Vitals data early, so dashboards and models never silently break.
DATASETS
What you can pull from Core Web Vitals
The Core Web Vitals connector provides a list of curated datasets - ready-made sets of records, fields, and metrics you can extract on a schedule. Need something specific? Any dataset can be forked and customized, or built from scratch, with our Universal Connector.
List of curated datasets
record_key_urlrecord_key_url
string
originalUrloriginalUrl
string
normalizedUrlnormalizedUrl
string
Period_lastDate_dayPeriod_lastDate_day
integer
Period_lastDate_yearPeriod_lastDate_year
integer
Period_firstDate_dayPeriod_firstDate_day
integer
Period_firstDate_yearPeriod_firstDate_year
integer
Period_firstDate_monthPeriod_firstDate_month
integer
Period_lastDate_monthPeriod_lastDate_month
integer
experimental_time_to_first_byte_percentiles_p75experimental_time_to_first_byte_percentiles_p75
float
first_contentful_paint_histogram_densityfirst_contentful_paint_histogram_density
float
largest_contentful_paint_histogram_startlargest_contentful_paint_histogram_start
float
navigation_types_fractions_restorenavigation_types_fractions_restore
float
cumulative_layout_shift_histogram_endcumulative_layout_shift_histogram_end
float
experimental_time_to_first_byte_histogram_startexperimental_time_to_first_byte_histogram_start
float
first_input_delay_histogram_endfirst_input_delay_histogram_end
float
first_input_delay_percentiles_p75first_input_delay_percentiles_p75
float
interaction_to_next_paint_histogram_endinteraction_to_next_paint_histogram_end
float
first_contentful_paint_percentiles_p75first_contentful_paint_percentiles_p75
float
experimental_time_to_first_byte_histogram_densityexperimental_time_to_first_byte_histogram_density
float
interaction_to_next_paint_histogram_densityinteraction_to_next_paint_histogram_density
float
interaction_to_next_paint_histogram_startinteraction_to_next_paint_histogram_start
float
largest_contentful_paint_histogram_densitylargest_contentful_paint_histogram_density
float
navigation_types_fractions_navigate_cachenavigation_types_fractions_navigate_cache
float
cumulative_layout_shift_histogram_startcumulative_layout_shift_histogram_start
float
cumulative_layout_shift_percentiles_p75cumulative_layout_shift_percentiles_p75
float
first_input_delay_histogram_densityfirst_input_delay_histogram_density
float
form_factors_fractions_phoneform_factors_fractions_phone
float
form_factors_fractions_desktopform_factors_fractions_desktop
float
largest_contentful_paint_histogram_endlargest_contentful_paint_histogram_end
float
navigation_types_fractions_back_forward_cachenavigation_types_fractions_back_forward_cache
float
first_input_delay_histogram_startfirst_input_delay_histogram_start
float
largest_contentful_paint_percentiles_p75largest_contentful_paint_percentiles_p75
float
navigation_types_fractions_navigatenavigation_types_fractions_navigate
float
navigation_types_fractions_reloadnavigation_types_fractions_reload
float
cumulative_layout_shift_histogram_densitycumulative_layout_shift_histogram_density
float
experimental_time_to_first_byte_histogram_endexperimental_time_to_first_byte_histogram_end
float
form_factors_fractions_tabletform_factors_fractions_tablet
float
first_contentful_paint_histogram_startfirst_contentful_paint_histogram_start
float
first_contentful_paint_histogram_endfirst_contentful_paint_histogram_end
float
interaction_to_next_paint_percentiles_p75interaction_to_next_paint_percentiles_p75
float
navigation_types_fractions_back_forwardnavigation_types_fractions_back_forward
float
navigation_types_fractions_prerendernavigation_types_fractions_prerender
float
Need a dataset, metric, or attribute you don't see?
Tell us what's missing and we'll add it to the connector.
WITH VS. WITHOUT
Who carries the load when things change
Keep Core Web Vitals data flowing to every warehouse, dashboard, and tool - and see who owns it when an API or schema changes:
| Without Dataddo |
With Dataddo
|
Outcome for you | |
|---|---|---|---|
| API or auth change | You discover the breakage and scramble to fix it. | We update the connector and restore the pipeline - often before you notice. | Syncs from Core Web Vitals keep flowing |
| Schema drift | Columns change and pipelines break or corrupt data silently. | Detected automatically and handled by configurable rules. | Only clean Core Web Vitals data lands in reports |
| Endpoint deprecated | You re-engineer the integration. | We own the update - the data contract holds. | Your Core Web Vitals reporting keeps working |
| Missing connector | You build and maintain a custom integration. | We build it and maintain it, under a ~4-week SLA. | Any Core Web Vitals data you need, on request |
| Silent degradation | You find out when a report or model run fails. | Proactive monitoring catches anomalies and delays first. | Gaps caught before dashboards break |
| Debugging | You dig through logs across disconnected tools. | Run histories, payload inspection, and end-to-end lineage in one place. | Faster root-cause, fewer reporting gaps |
Data residency by design
Choose where Core Web Vitals data is processed - same cloud, region, or sovereign
Core Web Vitals is a cloud API, so the question isn't on-prem vs cloud - it's which region your data flows through. With Dataddo you run the data plane in the region you choose, so Core Web Vitals payloads move straight to your destinations without transiting a third-party SaaS. Pin it to an EU or US region for compliance, or self-host when a downstream target lives inside your own network.
| Data Plane location | Typical data sensitivity | Why this setup |
|---|---|---|
|
Public cloud 
AWS
Microsoft Azure
Google Cloud
|
Low to moderate - general business, marketing, and product data; sources that are already cloud-native. | Fastest to stand up and scales elastically. Best when the data has no residency restriction and often already lives in the same public cloud. |
|
Regional & EU sovereign clouds
EU sovereign clouds
Regional providers
Private cloud
|
Regulated / residency-bound - PII, financial, and health data governed by GDPR or local law. | Keeps processing inside a specific jurisdiction to meet data-residency and sovereignty rules, while still running as managed infrastructure. |
|
On-premises 
Kubernetes
Red Hat OpenShift
VMware Tanzu
|
Highly sensitive / restricted - data that contractually or legally cannot leave the corporate perimeter. | Data never leaves your network. Required for air-gapped, classified, or locked-down environments; the Control Plane still manages it via metadata only. |
DATA DELIVERY
Every way to deliver Core Web Vitals data
Analytics data rarely has one home. Dataddo feeds Core Web Vitals into AI and agents, loads it into your warehouse for unified analytics, activates insights back into marketing and CRM tools, and delivers files to storage - all governed the same way.
| Transport type | What it does | Typical destinations | Typical business use cases |
|---|---|---|---|
| Data to AI & Agents | Feed Core Web Vitals data into vector databases, LLMs, and AI agents so copilots can reason over your analytics. | Load Core Web Vitals metrics into vector stores for retrieval-augmented analytics assistants, Give AI agents and copilots governed access to live Core Web Vitals data | |
| ETL / ELT to your warehouse | Load Core Web Vitals metrics and dimensions into your warehouse for unified, cross-source analytics. | Centralize Core Web Vitals alongside every other source in Snowflake, BigQuery, or Redshift, Backfill Core Web Vitals history for trend and cohort analysis | |
| Activate insights | Push segments and modeled metrics built from Core Web Vitals data back into ad and CRM platforms. | Sync modeled audiences and scores from Core Web Vitals to ad and CRM tools, Return insights to optimize campaigns and targeting | |
| Files to storage & partners | Deliver raw or modeled Core Web Vitals extracts to object storage and partners. | Archive raw Core Web Vitals exports to S3, GCS, or Azure storage, Send scheduled Core Web Vitals extracts to partners over SFTP |
Claude
OpenAI
Gemini
Mistral AI
Snowflake
BigQuery
Amazon Redshift
PostgreSQL
Google Ads
Meta
HubSpot
Salesforce
Google Cloud Storage
Azure Blob Storage
SFTP
Case Studies
See what data teams build with Dataddo
65,000 Social Media Accounts. One Platform. Zero Manual Authorizations.
Beauty & Consumer Goods
How Livesport Activates Data, Saves Engineering Resources with BigQuery and Dataddo
Entertainment
How ID&T Group Activates Data from 1M+ Festival Fans and Dozens of Social Accounts
Entertainment
How Sensire Accelerated Migration of a Proprietary On-Premise Data Infrastructure to the Cloud with Dataddo
Healthcare
How Ringside.ai Builds a Data Product Better and Faster Using Dataddo
Marketing
How Publicis Groupe Brasil Uses Dataddo's API to Scale a Data Product
Advertising
FAQ
Core Web Vitals as a source + Dataddo, answered
Where can I send Core Web Vitals data?
To any of Dataddo's 150+ destinations - warehouses like Snowflake and BigQuery, BI dashboards, CRMs and marketing tools, object storage, and AI or vector stores - plus custom destinations on request.
Do I have to maintain the pipeline?
No. Dataddo is fully managed: we maintain the Core Web Vitals connector, adapt to API and schema changes, and alert you if anything needs attention. There is no pipeline code for you to write or fix.
Can I combine Core Web Vitals with my other analytics tools?
Yes. Dataddo loads Core Web Vitals into Snowflake, BigQuery, or Redshift alongside your other analytics, marketing, and product sources, so you can build one unified view instead of stitching exports together.
What if Core Web Vitals changes their API?
That's on us, not you. Dataddo's team proactively tracks Core Web Vitals API and schema changes and updates the connector before they break your pipeline. Continuous monitoring watches every sync, and if anything needs attention you get an alert - so your Core Web Vitals data keeps flowing without you touching a thing.
Which Core Web Vitals metrics and dimensions are available?
The full Core Web Vitals API surface - every metric, dimension, and breakdown, not a fixed subset. If a field you need isn't exposed yet, we add it on request, usually at no extra cost.
How is my data secured?
Dataddo is SOC 2 Type II and ISO 27001 certified. Data is encrypted in transit and at rest, PII can be masked or hashed, and EU or US data residency is available. Self-host the data plane and payload data never leaves your network.
Will API rate limits be a problem?
Dataddo handles Core Web Vitals pagination, rate limits, and retries for you, and pulls incrementally on a schedule so you stay within API quotas without impacting your source.
Am I locked in?
No. Pipelines are source- and destination-agnostic - you can add or switch destinations without rebuilding, and data lands in native formats you own.