What is Reporting Health? 

The Reporting Health pane shows whether any metrics in your dashboard are experiencing data inconsistencies from the source channel's API — such as a platform temporarily returning incorrect values for a post's lifetime engagement. 

When a metric is flagged, it means Sprinklr has detected unusual fluctuations in the data being received from the channel. It does not necessarily mean the numbers you see on your dashboard are wrong.

What does Sprinklr do when it detects a fluctuation? 

Sprinklr's trend calculation system is designed to absorb API inconsistencies and display the most reliable value possible, rather than reflecting every raw fluctuation directly. 

When a metric value drops unexpectedly: 

• Sprinklr holds the display at the last confirmed value rather than showing the lower number. 

• The metric stays at this value until the channel either confirms the drop as sustained, or the value recovers. 

When a metric value spikes unexpectedly: 

• Sprinklr shows the higher value, but treats it as unconfirmed. 

• If the value reverts within a short window, the spike is smoothed out and the trend is redistributed evenly across that period. 

• If the higher value persists, it is accepted as the new confirmed baseline. 

This means that when a metric is flagged in the Reporting Health pane, Sprinklr is already managing it — the value shown in your dashboard reflects the best available number, not the raw fluctuating API value. 

How does Sprinklr respond to these issues? 

Detected fluctuations are raised as alerts in Sprinklr's backend monitoring system. Where a pattern of instability is identified, Sprinklr proactively raises this with the respective channel on behalf of customers — so issues are flagged and tracked without requiring any action from your team. 

When should I be concerned? 

The Reporting Health flag is informational. It tells you that a channel is sending inconsistent data for some of your posts, and gives you visibility into which metrics and what proportion of content is affected. 

If the issue persists, it typically indicates an upstream problem with the channel's API that Sprinklr is actively monitoring and escalating with the platform.