Salesforce replaced fragmented, per-team telemetry pipelines with a standardized Product Data Platform (PDP) that processes 45 billion rows of data daily across 19,000 distinct events and 2,000+ product features. Before PDP, roughly 80% of product teams wanted the same basic adoption metrics but built custom solutions independently, causing silos and duplicated work. PDP introduced a mandatory-plus-optional schema on Monitoring Cloud infrastructure, automated downstream metric generation, and cut time to insight from ~one month to daily refreshes — a 97% reduction. An AI-powered MCP tool now recommends correct instrumentation automatically, and developer onboarding surveys consistently score ~9/10 CSAT. The standardized data foundation also enables AI-powered analytics and MCP integrations across Salesforce products like Agentforce and Tableau.
Questions this post answers
What concrete results did Salesforce see after standardizing product telemetry with their Product Data Platform?
Standardizing telemetry reduced time to insight by approximately 97% — dashboards that previously took about a month to reflect new instrumentation now refresh daily. The platform processes 45 billion rows of data every day across 19,000 distinct events covering more than 2,000 product features. Developer onboarding surveys consistently report approximately 9/10 CSAT, and teams that previously needed multiple engineers for manual telemetry work now spend only a few hours on standardized instrumentation. Teams shipping internal platforms track adoption metric wins like these on daily.dev.
How did Salesforce handle the tension between standardizing telemetry and allowing product-specific flexibility in their schema design?
Salesforce built a standardized custom schema on Monitoring Cloud infrastructure with two tiers: mandatory fields required for consistent cross-product metrics, and carefully governed optional attributes that give individual teams flexibility without breaking standardization. The schema continues evolving as new cross-product use cases emerge, and close collaboration with subject matter experts from products like Agentforce and Tableau shaped the balance between uniformity and product-specific needs. Engineers designing shared data schemas find real-world trade-off discussions like this on daily.dev.