Data Integration Metrics
Data Integration Metrics in Salesforce is the Setup page that surfaces operational telemetry on the org's data integration activity: Bulk API job volume and success rates, REST API request counts, External Object query throughput, Salesforce Connect virtualization performance, Change Data Capture event volume, and Platform Events publication and delivery.
Definition
Data Integration Metrics in Salesforce is the Setup page that surfaces operational telemetry on the org's data integration activity: Bulk API job volume and success rates, REST API request counts, External Object query throughput, Salesforce Connect virtualization performance, Change Data Capture event volume, and Platform Events publication and delivery. The page aggregates per-integration-type metrics so admins can spot trending issues (rising error rates, throttling, latency creep) before they become production incidents.
Data Integration Metrics exists because integration health is otherwise invisible. A nightly Bulk API job that started failing on 5 percent of records last week stays unnoticed until downstream reports look wrong; a Connected App with rising token errors stays unnoticed until users complain about authentication failures. The Metrics page is the operational dashboard for integrations; treating it as routine ops furniture rather than as something to check only during incidents is the discipline that separates orgs with healthy integrations from orgs with constant integration surprises.
Why Data Integration Metrics is the integration-health cockpit most orgs underuse
Where Data Integration Metrics lives and what it shows
Setup, Integrations, Data Integration Metrics (or Setup, Environments, Integrations depending on edition). The page surfaces metrics across integration types: Bulk API throughput and error rates, REST API request volume against the 24-hour rolling limit, SOAP API request volume, Streaming API event delivery success, Change Data Capture event volume, Platform Events publish and delivery rates, Salesforce Connect external object query latency. Each metric is shown over a rolling window (24 hours, 7 days, 30 days) with trend visualization.
API request limits and the throttling early-warning
Every org has a 24-hour API request limit per edition (Enterprise typically 1 million daily). Data Integration Metrics shows current request count against the limit with a trending line. Approaching 80 percent of the limit triggers a procurement signal (buy more API capacity) or an optimization signal (reduce per-request waste). Most orgs do not check the limit until they exceed it and integrations start failing with API throttle errors; the Metrics page is the early warning that prevents the emergency.
Bulk API metrics and the integration failure surface
Bulk API jobs surface per-job in the Bulk Data Load Jobs page; the aggregate trends surface in Data Integration Metrics. Rising failure rate week-over-week is the signal that an integration is degrading; constant high failure rate is the signal that one integration is poorly built. Both deserve investigation. The metrics page does not name the failing integration; combine with the Bulk Data Load Jobs page to identify which job is the source of the trend.
Change Data Capture and Platform Events delivery
Change Data Capture (CDC) publishes change events for subscribed external systems. Platform Events let custom code publish events for any subscriber. Both have publication and delivery metrics on the Data Integration Metrics page. The delivery success rate is the key health signal; a subscriber that goes down causes the delivery rate to drop, and Salesforce queues events until the subscriber recovers or the queue overflows. The metrics page surfaces the trend; combined with the subscriber side, it tells you whether the issue is on Salesforce or on the consumer.
Salesforce Connect external object latency
Salesforce Connect virtualizes external data as Salesforce External Objects; queries against External Objects translate to live calls against the external system. The latency of these calls shows on Data Integration Metrics. Rising latency is the signal that the external system is slowing down or that the queries Salesforce is generating are not well-tuned. The metrics page is the early warning before users complain about slow record loads on External Object pages.
Connected App and OAuth metrics
The Data Integration Metrics page surfaces some OAuth-level telemetry that complements Connected Apps OAuth Usage. Token refresh failure rates, authorization errors, session expiration patterns. Rising error rates are signals of expired client credentials, IP restriction changes, or scope mismatches. The integration-health view catches these signals before they become user-facing authentication outages.
Building the operational discipline
The Metrics page is one piece of a broader integration ops discipline. The full pattern: weekly review of Data Integration Metrics for trending issues, monthly review of Bulk Data Load Jobs for specific failure investigation, monthly review of Connected Apps OAuth Usage for stale authorizations, alerts on the most critical metrics (API limit threshold, Bulk failure rate, CDC delivery rate) so degradations trigger immediate attention rather than wait for the weekly cycle. The combination produces integrations that stay healthy; without the discipline, integration outages are surprises.
How to use Data Integration Metrics as routine ops
The pattern: weekly review of the page, monthly investigation of trends, alerts on critical metrics. The discipline is the difference between integrations that stay healthy and integrations that surprise the team during incidents.
- Open Data Integration Metrics weekly
Setup, Integrations, Data Integration Metrics. Scan the trends. Note any metric trending in the wrong direction over the past week.
- Check API request volume against the daily limit
Approaching 80 percent of the 24-hour limit is the procurement or optimization trigger. Catch it weeks before exhaustion.
- Investigate trending Bulk API failure rates
Cross-reference with Bulk Data Load Jobs to identify the specific failing job. Fix the underlying integration; do not let the failure rate normalize.
- Monitor CDC and Platform Events delivery rates
Delivery rate below 95 percent signals a subscriber issue. Coordinate with the subscriber team; events queue but the queue overflows eventually.
- Watch Salesforce Connect external object latency
Rising latency signals external system degradation. Coordinate with the external system owner before users complain.
- Build alerts on the critical metrics
API limit at 80 percent, Bulk failure rate above threshold, CDC delivery rate below threshold. Alerts catch degradations between weekly reviews.
- Document the weekly review as ongoing ops
The page only matters if someone reviews it. Calendar entry, named owner, weekly review of 15 minutes. The discipline produces healthy integrations.
Weekly for most orgs; daily for high-volume integration-heavy orgs.
Custom Flow or report-driven alerts on critical metrics (API limit, failure rates).
Bulk API, REST/SOAP API, Streaming, CDC, Platform Events, Salesforce Connect. Pick the relevant subset per org.
24-hour, 7-day, 30-day views. Pick based on the metric's signal cadence.
Documented list of expected integrations with owner and purpose. Required for trend investigation.
- The page does not name specific integrations. Combine with Bulk Data Load Jobs and Connected Apps OAuth Usage to identify the source of trends.
- API limit exhaustion produces immediate integration failures with no recovery until midnight UTC. Catch the trend weeks before; do not wait for exhaustion.
- CDC and Platform Events queue events when delivery fails but the queue is bounded. Subscriber outages beyond the queue lifetime lose events permanently.
- Salesforce Connect latency depends on external systems Salesforce does not control. Coordinate root cause with external owners; do not blame Salesforce when the external is slow.
- Without integration ownership, trend investigation stalls. Maintain an integration inventory with owner per integration; trends without owners become orphans.
Trust & references
Cross-checked against the following references.
- Data Integration Metrics referenceSalesforce
- Salesforce APIs overviewSalesforce
Straight from the source - Salesforce's reference material on Data Integration Metrics.
- Monitor Data IntegrationsSalesforce Help
- API Request LimitsSalesforce Help
- Platform EventsSalesforce Help
Hands-on resources to go deeper on Data Integration Metrics.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Why is understanding Data Integration Metrics important for Salesforce admins?
Q2. In which area of Salesforce would you typically find Data Integration Metrics?
Q3. What is the primary benefit of Data Integration Metrics for Salesforce administrators?
Discussion
Loading discussion…