Datapipe
Latest field data
A Chrome UX Report report of latest field data.
Live
Chrome UX Report for agencies and in-house teams
SEO and site owners use Chrome UX Report in Datapipe to see real-user LCP, INP, CLS, FCP, and TTFB at p75, with good, needs-improvement, and poor, for an origin or a URL, including history trends.
What connects
No user OAuth. The server calls the Chrome UX Report API with the same GOOGLE_API_KEY. A domain loads the origin record. A page address also loads that URL record. History uses queryHistoryRecord.
What you can report on
- Address (dimension). The origin, such as https://example.com, or the exact URL.
- Scope (dimension). origin or url, matching the CrUX record key.
- Device (dimension). PHONE is shown as mobile. DESKTOP is shown as desktop. Tablet is not requested.
- Date (dimension). Today for the latest 28-day window, or the collection period end for history.
- View (dimension). latest for queryRecord, history for queryHistoryRecord.
- LCP p75 (metric). largest_contentful_paint percentiles.p75, milliseconds.
- INP p75 (metric). interaction_to_next_paint percentiles.p75, milliseconds.
- CLS p75 (metric). cumulative_layout_shift percentiles.p75.
- FCP p75 (metric). first_contentful_paint percentiles.p75, milliseconds.
- TTFB p75 (metric). experimental_time_to_first_byte percentiles.p75, milliseconds.
- Good, needs improvement, poor (metric). The three histogram densities for each metric, stored as shares.
What you set up
- The owner enables the Chrome UX Report API. GOOGLE_API_KEY is shared with PageSpeed.
- Add domains for origin data, or full page URLs for URL data.
- Create the Core Web Vitals report. It is sent to Google Sheets. History rows keep collection periods inside the report's date window.
Limitations
Chrome omits a record when a URL does not have enough visits. That call returns 404 and is skipped. If every call is empty, the report says Chrome does not have enough visits yet. Form factors are phone and desktop only. The quota is 150 queries per minute. Calls are paced at 120 and cached for 12 hours.
Last reviewed 2026-10-29. Owner: Datapipe.
Connection
Live
Live with the Chrome UX Report API and History API. The same GOOGLE_API_KEY is used. You enter domains for origin data and pages for URL data. No user OAuth. The Core Web Vitals sheet shows p75 and the good, needs-improvement, and poor split.
Fields
Chrome UX Report queryRecord and queryHistoryRecord. Origin and URL field data. The key is GOOGLE_API_KEY. Source: https://developer.chrome.com/docs/crux/api. Read on 2026-10-29. 14 fields.
Synced today
- Date
date - Address
key.url - Scope
scope - Device
formFactor - View
view - LCP p75 (ms)
metrics.largest_contentful_paint.percentiles.p75 - LCP good
metrics.largest_contentful_paint.histogram.0.density - LCP needs improvement
metrics.largest_contentful_paint.histogram.1.density - LCP poor
metrics.largest_contentful_paint.histogram.2.density - INP p75 (ms)
metrics.interaction_to_next_paint.percentiles.p75 - INP good
metrics.interaction_to_next_paint.histogram.0.density - INP needs improvement
metrics.interaction_to_next_paint.histogram.1.density - INP poor
metrics.interaction_to_next_paint.histogram.2.density - CLS p75
metrics.cumulative_layout_shift.percentiles.p75 - CLS good
metrics.cumulative_layout_shift.histogram.0.density - CLS needs improvement
metrics.cumulative_layout_shift.histogram.1.density - CLS poor
metrics.cumulative_layout_shift.histogram.2.density - FCP p75 (ms)
metrics.first_contentful_paint.percentiles.p75 - FCP good
metrics.first_contentful_paint.histogram.0.density - FCP needs improvement
metrics.first_contentful_paint.histogram.1.density - FCP poor
metrics.first_contentful_paint.histogram.2.density - TTFB p75 (ms)
metrics.experimental_time_to_first_byte.percentiles.p75 - TTFB good
metrics.experimental_time_to_first_byte.histogram.0.density - TTFB needs improvement
metrics.experimental_time_to_first_byte.histogram.1.density - TTFB poor
metrics.experimental_time_to_first_byte.histogram.2.density - Date
collectionPeriods.lastDate - Address
key.url - Scope
scope - Device
formFactor - View
view - LCP p75 (ms)
metrics.largest_contentful_paint.percentilesTimeseries.p75s - LCP good
metrics.largest_contentful_paint.histogramTimeseries.0.densities - LCP needs improvement
metrics.largest_contentful_paint.histogramTimeseries.1.densities - LCP poor
metrics.largest_contentful_paint.histogramTimeseries.2.densities - INP p75 (ms)
metrics.interaction_to_next_paint.percentilesTimeseries.p75s - INP good
metrics.interaction_to_next_paint.histogramTimeseries.0.densities - INP needs improvement
metrics.interaction_to_next_paint.histogramTimeseries.1.densities - INP poor
metrics.interaction_to_next_paint.histogramTimeseries.2.densities - CLS p75
metrics.cumulative_layout_shift.percentilesTimeseries.p75s - CLS good
metrics.cumulative_layout_shift.histogramTimeseries.0.densities - CLS needs improvement
metrics.cumulative_layout_shift.histogramTimeseries.1.densities - CLS poor
metrics.cumulative_layout_shift.histogramTimeseries.2.densities - FCP p75 (ms)
metrics.first_contentful_paint.percentilesTimeseries.p75s - FCP good
metrics.first_contentful_paint.histogramTimeseries.0.densities - FCP needs improvement
metrics.first_contentful_paint.histogramTimeseries.1.densities - FCP poor
metrics.first_contentful_paint.histogramTimeseries.2.densities - TTFB p75 (ms)
metrics.experimental_time_to_first_byte.percentilesTimeseries.p75s - TTFB good
metrics.experimental_time_to_first_byte.histogramTimeseries.0.densities - TTFB needs improvement
metrics.experimental_time_to_first_byte.histogramTimeseries.1.densities - TTFB poor
metrics.experimental_time_to_first_byte.histogramTimeseries.2.densities
Core Web Vitals
| Name | API field | Description | Type | Group | Cross-channel |
|---|---|---|---|---|---|
| LCP p75 · Synced today | metrics.largest_contentful_paint.percentiles.p75 | Largest contentful paint, 75th percentile, in milliseconds. | metric · integer | Core Web Vitals | |
| LCP good · Synced today | metrics.largest_contentful_paint.histogram.0.density | Share of visits with good LCP. | metric · number | Core Web Vitals | |
| LCP needs improvement · Synced today | metrics.largest_contentful_paint.histogram.1.density | Share of visits whose LCP needs improvement. | metric · number | Core Web Vitals | |
| LCP poor · Synced today | metrics.largest_contentful_paint.histogram.2.density | Share of visits with poor LCP. | metric · number | Core Web Vitals | |
| INP p75 · Synced today | metrics.interaction_to_next_paint.percentiles.p75 | Interaction to next paint, 75th percentile, in milliseconds. | metric · integer | Core Web Vitals | |
| INP good · Synced today | metrics.interaction_to_next_paint.histogram.0.density | Share of visits with good INP. | metric · number | Core Web Vitals | |
| CLS p75 · Synced today | metrics.cumulative_layout_shift.percentiles.p75 | Cumulative layout shift, 75th percentile. | metric · number | Core Web Vitals | |
| CLS good · Synced today | metrics.cumulative_layout_shift.histogram.0.density | Share of visits with good CLS. | metric · number | Core Web Vitals | |
| FCP p75 · Synced today | metrics.first_contentful_paint.percentiles.p75 | First contentful paint, 75th percentile, in milliseconds. | metric · integer | Core Web Vitals | |
| TTFB p75 · Synced today | metrics.experimental_time_to_first_byte.percentiles.p75 | Time to first byte, 75th percentile, in milliseconds. | metric · integer | Core Web Vitals |
Dimensions
| Name | API field | Description | Type | Group | Cross-channel |
|---|---|---|---|---|---|
| Address · Synced today | key.url | The origin or URL the record describes. | dimension · string | Dimensions | |
| Device · Synced today | formFactor | PHONE or DESKTOP. | dimension · string | Dimensions | |
| Period end · Synced today | collectionPeriods.lastDate | Last day of a History API collection period. | dimension · date | Dimensions |
History
| Name | API field | Description | Type | Group | Cross-channel |
|---|---|---|---|---|---|
| LCP p75 history · Synced today | metrics.largest_contentful_paint.percentilesTimeseries.p75s | History API p75 series for LCP. | metric · integer | History |
Cross-channel metrics
Spend, Impressions, Clicks, Conversions, and Revenue roll up on All channels when a field maps to them. ROAS is revenue divided by spend. CPA is spend divided by conversions. The Cross-channel column above shows the match.
Example reports
History trends
A Chrome UX Report report of history trends.
Destinations
Chrome UX Report to Google Sheets
A sheet you can open, share, and refresh.
Included on every plan.
Chrome UX Report to Looker Studio
Charts that read the Google Sheet this integration keeps up to date.
Included on every plan. Looker reads the sheet. There is no separate Looker install.
Chrome UX Report to BigQuery
A warehouse table for the same columns.
Pro and Agency plans.
Chrome UX Report to AI and MCP
Ask a question in plain English, or let another tool read the report through MCP.
Included on every plan. An AI key is optional.
Chrome UX Report to the API
Download the rows as CSV or JSON from the report.
Included on every plan.
Chrome UX Report to Google Drive
CSV, Excel, and an optional JSON file in a Drive folder you pick. Each client gets a Datapipe folder. The file can overwrite itself or keep the date in the name.
Included on every plan. Drive API v3 with the drive.file scope only. Enable the Google Drive API in the GCP project. Hourly, daily, or weekly.
How to connect
- Create a free account.
- The owner sets GOOGLE_API_KEY and enables the PageSpeed Insights API and the Chrome UX Report API. You don't paste a key and you don't sign in.
- Open Connections, add domains or pages, and click any Search Console site that is suggested.
- Create the Core Web Vitals report. It lands in Google Sheets and refreshes on the schedule.
Refresh by plan
| Plan | Refresh | BigQuery | Price |
|---|---|---|---|
| Free | Daily | No | $0/mo |
| Starter | Daily | No | $15/mo |
| Pro | Hourly | Yes | $49/mo |
| Agency | 15 minutes | Yes | $149/mo |
FAQ
Is the Chrome UX Report connection live?
Live with the Chrome UX Report API and History API. The same GOOGLE_API_KEY is used. You enter domains for origin data and pages for URL data. No user OAuth. The Core Web Vitals sheet shows p75 and the good, needs-improvement, and poor split.
Do I have to talk to sales?
No. Create an account, connect the source, and the first report is on Home. Sample numbers stay available when a key is missing.
How often do the numbers refresh?
Free and Starter refresh daily. Pro refreshes hourly. Agency refreshes every 15 minutes on up to 50 accounts and hourly on the rest. We keep the history for you: 90 days on Free, and for as long as you subscribe on paid plans. No warehouse to set up.
Which fields are synced today?
The list marks Synced today on the fields the current connector pulls. The rest of the list is what the platform publishes, so you can see it before you sign up.