Budget/Pacing Anomaly Detection

Updated 

Budget Anomaly Detection provides real-time alerts through email and platform notifications when anomalies in  budget/end date or pacing is detected. It automatically detects issues like budget deviations, pacing deviations or changes in end dates that could lead to overspending and notifies users to take proactive actions. This feature supports paid initiatives and ad sets created in both Sprinklr and those auto-imported from native channels.

Budget Anomaly detection is enabled by default for all campaigns/ad sets that have a budget assigned. The default deviation threshold is set to 10%, so any change—whether from a budget adjustment or a modification to the end date. Any campaign/ad set exceeding this threshold will trigger a notification, which will be sent by default to the campaign owner for Sprinklr-created entities and to the account owner for auto-imported entities. Additionally, users can customize alert settings by specifying deviation thresholds and recipients for notifications.

Enablement Note: This feature is enabled by default. If you want to disable it, contact your Success Manager to disable the DP: PAID_ADS_ANOMALY_TYPES_DISABLED.

To Customize Anomaly Detection Alert Settings

  1. Open a new tab and navigate to Sprinklr Marketing > Advertising > Ads Manager.

  2. Locate the required ad campaign and click the view and edit icon next to the campaign.

  3. Select the Strategy & Anomaly tab on the right. The Enable Anomaly Detection toggle is switched on by default. If the toggle is disabled, hover over it to view the reason why the feature is disabled.

    Note:

    • Anomaly Detection feature is applicable only for active/paused Ad Entities.

    • The Enable Anomaly Detection toggle will be disabled for campaigns without an assigned budget.

    • This feature will appear at the level where budget is assigned. For example, if the budget is set only at the ad set level, Anomaly Detection will also show only at the ad set level.

    • If a strategy group with pacing control is applied to any entity, Anomaly Detection will be disabled. To enable Anomaly Detection, remove the strategy group.

  4. Adjust the percentage in the Budget Alerts and Pacing & Spend Alerts sections as needed.

    1. Budget/End date Deviation: It identifies anomalies caused by changes in budget or end date using defined percentage deviation.

    2. Pacing Deviation: Identifies anomalies caused by changes in pacing using the defined percentage deviation.

    3. Spend Deviation: It identifies anomalies due to changes in spending compared to the previous day's spend, 3-day average, and 7-day average using defined percentage deviation.

      ​​

    Enable Pausing: To automatically pause campaigns/ad sets based on budget, pacing and spend anomalies, select the Enable Pausing option.

    Once enabled, the system monitors percentage deviations based on your defined thresholds. If a deviation meets or exceeds the threshold, the campaign is automatically paused, and all selected users and user groups receive platform and email notifications.

    Selecting Enable Pausing will trigger the following actions for budget, pacing and spend anomalies -

    • Budget/End Date Anomalies:

      • Sprinklr pauses the Paid Initiative (PI) or Ad Set when it detects anomalies related to budget or end date.

      • You can manually correct the budget or end date and then choose to reactivate the PI or ad set.

      • Sprinklr will never automatically reactivate a PI or ad set paused due to a budget or end date anomaly.

      Note: PI/ad set will be paused only if the budget is increased and exceeds the threshold. If the budget/expected per day budget is reduced, the PI/ad set will not be paused.

    • Pacing Anomalies:

      • When Sprinklr detects an over-pacing anomaly, it pauses the PI or ad set.

      • If conditions return to normal, the system automatically reactivates the PI/ad set the next day—only if it was originally paused due to a pacing anomaly.

      • Sprinklr only pauses for over-pacing scenarios; under-pacing does not trigger any action.

    • Spend Anomalies:

      • When a spend anomaly is detected, Sprinklr pauses the PI/ad set.

      • The system automatically reactivates it the following day, but only if it was paused due to the spend anomaly.

    Note:

    • The system does not pause Reach and Frequency (RnF) campaigns due to anomalies.

    • Pausing due to anomalies is not supported for X campaigns with Prepoll Views as the ad objective.

  5. Add the user(s) or user group(s) who will receive notifications in the Users/User Groups field. Users specified in this field will receive a platform notification whenever the budget exceeds the deviation threshold.

  6. Enter the email addresses of any external users in the External User Emails field. The email addresses added here will receive email notifications for anomaly detection.

  7. Click Review Changes to review all the updates made to the campaign.

  8. Click Apply Changes to save your changes in the platform.

Once the anomaly detection settings are applied, a warning message will appear if you attempt to update the lifetime budget above the specified threshold. Another warning message will be displayed in the Review tab.

Note:For entities where changes (budget or end date) are made in the channel, users will be notified via platform and email alerts when an anomaly is detected for these entities.

Sample Warning Message​

Anomaly Detection Threshold Changes Review Screen

Anomaly Detection also monitors pacing in ad campaigns. It automatically applies a default pacing control to all entities with a specified budget start and end date to track pacing. You will receive notifications if the pacing deviates (either underpacing or overpacing) beyond the threshold defined within the Strategy & Anomaly tab.

Bulk Update Anomaly Detection Settings Using Macros

You can bulk update the Enable Anomaly Detection toggle and the Budget/Pacing Deviation percentage in Ads Manager using either Macros or the View & Edit option.

To update Anomaly Detection settings in bulk using Macros

  1. Select the required campaigns in the Ads Manager screen.

  2. Click Macros in the menu bar at the bottom.

  3. Search for and select an existing macro or create a new one by clicking the Build New Macro option. While creating a new macro select the Detect Anomaly and Anomaly Config Budget Threshold field options.

    Build New Macro

    Macro Pop-up

Anomaly Detection Limitations

  • Anomaly Detection does not work for Reach and Frequency campaigns.

  • No notifications are sent if the budget is changed through Smart Budget allocation or the Rule Engine.

FAQs

No, the system will not send Anomaly Detection notifications if the budget is changed through Rule Engine or Smart Budget Allocation.

Yes, Anomaly Detection calculates pacing based on the entity's timezone and currency.

No, only pacing alerts apply to reporting-only channels such as DV360, Google Ads and so on.

No, you will have to manually reactivate the PI/ad set if it was paused due to the budget/end date anomaly.

Yes, for PI/ad sets that were paused due to over-pacing or a spend anomaly, Sprinklr will re-activate them the following day. However, if the PI/ad set was paused due to budget/end date anomaly the Sprinklr will not re-activate it.

Anomaly Detection takes precedence over the Rule Engine. For example, if Anomaly Detection pauses an entity and a rule attempts to re-enable it (a rare edge case), the system prioritizes the anomaly action. This is because rules are typically applied across multiple entities, whereas anomalies are handled at the individual entity level for accuracy and control.

When Startegy Group with pacing is applied to a PI/ad set, Sprinklr prioritizes this pacing method. As a result, the Anomaly Detection feature will only monitor and alert for Budget/End Date anomalies. It will not generate alerts for pacing anomalies in such cases.