Pingdom logo

Analytics integration

Pingdom reporting & analytics

Turn daily uptime, downtime, and response-time monitoring by check into 34 governed metrics for dashboards, agent answers, and cross-channel reporting.

What you can do with Pingdom in Maven

Maven models Pingdom into 34 governed metrics from the semantic layer. Track Downtime Seconds, Unmonitored Seconds, Uptime Percentage, Uptime Seconds and Web Accessibility Score, break results down by Signal Type, Account, Target and Strategy, and report Pingdom alongside Google Ads, Facebook Ads and Google Search Console without rebuilding exports or metric logic for every report.

What you can measure

34 Pingdom metrics you can use consistently

Maven keeps Pingdom numbers consistent across dashboards, reports, and answers so the team is not debating which spreadsheet is right.

Downtime Seconds

Total monitored seconds in a down state across selected checks and dates

Unmonitored Seconds

Total seconds without monitoring coverage across selected checks and dates

Uptime Percentage

Monitored uptime seconds divided by uptime plus downtime seconds as a percentage

Uptime Seconds

Total monitored seconds in an up state across selected checks and dates

Web Accessibility Score

Average provider-native accessibility score across represented page checks

Web Best Practices Score

Average provider-native best-practices score across represented page checks

Web Cumulative Layout Shift

Cumulative Layout Shift score.

Web First Contentful Paint Ms

First Contentful Paint in milliseconds.

Web Largest Contentful Paint Ms

Largest Contentful Paint in milliseconds.

Show all 34 metrics

Web Ops Metric Value

Numeric value reported by the provider. Interpret with metric_name and stream.

Web Performance Score

Average provider-native web performance score across represented page checks

Web SEO Score

Average provider-native SEO score across represented page checks

Web Speed Index Ms

Speed Index in milliseconds.

Web Total Blocking Time Ms

Total Blocking Time in milliseconds.

Average Active Time (s)

Average active (interacting) time per recorded session in seconds (Clarity EngagementTime activeTime), weighted by recorded sessions. Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Average Recorded Session Time (s)

Average total time per recorded session in seconds (Clarity EngagementTime totalTime), weighted by recorded sessions. Differs from avg_session_duration_seconds (web analytics sessions). Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Average Response Time (ms)

Average uptime-check response time in milliseconds. Unweighted mean of the provider's daily average per check (Pingdom and compatible uptime monitors); not request-weighted.

Average Scroll Depth

Average percent of the page scrolled per recorded session (Clarity ScrollDepth averageScrollDepth), weighted by recorded sessions. Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Dead Click Session Rate

Share of recorded sessions with at least one of the clicks on page elements that produced no response (0-1): sessions with the signal (Clarity DeadClickCount sessionsCount x sessionsWithMetricPercentage) divided by sessions evaluated, re-weighted across dates and dimension values. Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Dead Clicks

Occurrences of clicks on page elements that produced no response in recorded sessions (Clarity DeadClickCount subTotal). Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Error Click Session Rate

Share of recorded sessions with at least one of the clicks followed by a JavaScript error (0-1): sessions with the signal (Clarity ErrorClickCount sessionsCount x sessionsWithMetricPercentage) divided by sessions evaluated, re-weighted across dates and dimension values. Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Error Clicks

Occurrences of clicks followed by a JavaScript error in recorded sessions (Clarity ErrorClickCount subTotal). Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Excessive Scroll Session Rate

Share of recorded sessions with at least one of the scrolling through a page more than expected (0-1): sessions with the signal (Clarity ExcessiveScroll sessionsCount x sessionsWithMetricPercentage) divided by sessions evaluated, re-weighted across dates and dimension values. Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Excessive Scrolls

Occurrences of scrolling through a page more than expected in recorded sessions (Clarity ExcessiveScroll subTotal). Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Quickback Click Session Rate

Share of recorded sessions with at least one of the navigating to a page and quickly returning to the previous one (0-1): sessions with the signal (Clarity QuickbackClick sessionsCount x sessionsWithMetricPercentage) divided by sessions evaluated, re-weighted across dates and dimension values. Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Quickback Clicks

Occurrences of navigating to a page and quickly returning to the previous one in recorded sessions (Clarity QuickbackClick subTotal). Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Rage Click Session Rate

Share of recorded sessions with at least one of the rapid repeated clicks in one spot (0-1): sessions with the signal (Clarity RageClickCount sessionsCount x sessionsWithMetricPercentage) divided by sessions evaluated, re-weighted across dates and dimension values. Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Rage Clicks

Occurrences of rapid repeated clicks in one spot in recorded sessions (Clarity RageClickCount subTotal). Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Recorded Bot Sessions

Recorded sessions classified as bots (Clarity Traffic totalBotSessionCount). Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Recorded Distinct Users

Distinct users across recorded sessions (Clarity Traffic distinctUserCount). Non-additive: a sum over dates or dimension values over-counts returning users. Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Recorded Sessions

Sessions recorded by the session-recording tool (Clarity Traffic totalSessionCount, bot sessions included). Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Script Error Session Rate

Share of recorded sessions with at least one of the JavaScript errors (0-1): sessions with the signal (Clarity ScriptErrorCount sessionsCount x sessionsWithMetricPercentage) divided by sessions evaluated, re-weighted across dates and dimension values. Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Script Errors

Occurrences of JavaScript errors in recorded sessions (Clarity ScriptErrorCount subTotal). Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Recorded Pages per Session

Average pages per recorded session: page views behind Clarity's pagesPerSessionPercentage divided by recorded sessions, so it re-weights across dates and dimension values. Session-recording measure from the behavior rows of obt_web_ops (Microsoft Clarity live insights), not GA4/web-analytics sessions. Daily snapshot of the trailing 24 hours before the sync; group by device_category, browser or country (device/browser/country call) or page_location (URL call) for the breakdown rows.

Connection and sync

What Maven pulls from Pingdom

You connect Pingdom with API credentials from the Pingdom account. Maven stores them encrypted. The first Pingdom sync pulls the most recent 30 days so the workspace fills quickly. A follow-up backfill then adds older history, up to 12 months in total. After that, each scheduled sync re-reads the last 30 days, so late changes are picked up.

Performance

Daily uptime and response-time observations for Pingdom checks.

Fields: check name, check type, hostname, avg response time ms, uptime seconds, downtime seconds, unmonitored seconds

How it works

Connect Pingdom to a client’s workspace

No SQL or warehouse setup. Connect the source, then build the client’s report by asking Claude or ChatGPT.

Step 1

Connect Pingdom

In the client’s workspace, open Sources, add Pingdom and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.

Step 2

Maven syncs and models the data

Maven pulls the client’s Pingdom data (1 objects) and models it into documented tables. No SQL, warehouse or pipeline setup.

Step 3

Report, ask and automate

Build the client’s report or deck by asking Claude or ChatGPT through the MCP, set alerts on what matters, and publish to the client’s portal once you approve it.

Works well with

Report Pingdom alongside the rest of your stack

FAQ

Pingdom reporting questions

What Pingdom metrics can I report on in Maven?

Maven exposes 34 governed Pingdom metrics, including Downtime Seconds, Unmonitored Seconds, Uptime Percentage, Uptime Seconds, Web Accessibility Score and Web Best Practices Score — each defined once so it means the same thing in every report.

What can I break Pingdom performance down by?

You can break Pingdom metrics down by Signal Type, Account, Target, Strategy, Performance Score, Accessibility Score, Best Practices Score and Seo Score, and more.

Can I combine Pingdom with other data sources?

Yes. Pingdom sits in the same client workspace as sources like Google Ads, Facebook Ads, Google Search Console, Shopify and HubSpot, so one report or question can use them together.

What Pingdom data does Maven sync?

Maven syncs daily uptime observations from Pingdom.

How often does Pingdom data sync to Maven?

Maven refreshes Pingdom on a schedule after the source is connected, and shows each source’s last sync time in the client’s workspace, so you can check the data is current before a report goes out.

Is my Pingdom data secure with Maven?

Yes. Maven encrypts integration credentials and tokens, scopes access to the workspace, and uses the connection only to sync the reporting data needed for governed analytics.

Start your 14-day trial

Set up your first client, build their report by asking Claude or ChatGPT, and publish it to their portal.

  • Free for 14 days, no credit card
  • Your first client workspace and portal
  • Every report template, ready to clone
Start a 14-day trial

Nothing is charged unless you subscribe.

Prefer a walkthrough? Book a demo on one of your own clients.