Skip to main content
Skip to article
  • Qualtrics Platform
    Qualtrics Platform
  • Customer Journey Optimizer
    Customer Journey Optimizer
  • XM Discover
    XM Discover
  • Qualtrics Social Connect
    Qualtrics Social Connect

iQ Anomaly Event

Was this helpful?


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

The feedback you submit here is used only to help improve this page.

That’s great! Thank you for your feedback!

Thank you for your feedback!

About iQ Anomaly Events

iQ anomaly events allow you to begin a workflow triggered by unexpected spikes or drops in the response count of your surveys and distributions. Instead of seeing unexpected response counts after your study is completed, iQ anomaly events can be used to notify your survey builder in real-time whenever the response count changes atypically.

Qtip: An anomaly is measured based on 90 days of historical trends.

Setting up an iQ Anomaly Event

  1. Click the navigation menu in the top left hand corner. on the global workflows page, clicking create a workflow and started by an event
  2. Select Workflows.
  3. Click Create a workflow.
  4. Select Started when an event is received.
  5. Choose the iQ anomaly event.
    Shows the IQ anomaly event in the events library.
  6. Select iQ anomaly event.
    Shows IQ anomaly event within the iq anomaly event page.
  7. Click Finish. Shows the finish button within the iQ anomaly event.
  8. You can add conditions to your workflow by clicking the plus sign ( + ). Conditions determine when a workflow runs. See the Workflows Overview for more information. You can build conditions based on the following values:
    • Anomaly type: The type of detected anomaly, either a spike or a drop.
    • Lower bound of expected range value: The minimum expected response count for your survey. This figure should be entered as a decimal.
    • Upper bound of expected range value: The maximum expected response count. This figure should be entered as a decimal.
      Qtip: Use lower and upper bound range values to indicate what you would expect to see. This could be helpful in setting up notifications that flag events that are outside of this range. For example, if your expected response count is within the range of 100-200 and you receive a response count of 50.
    • Survey ID: ID of the survey for which the anomaly has been detected.
    • Survey name: Name of the survey for which the anomaly has been detected.
    • Time of detection: The time when the anomaly has been detected.
    • Value that caused the anomaly: The anomalous value.
    Example: Let’s say you want to send an email to your data team every time an anomaly is detected in one specific survey. You can create a condition for “Survey ID equals (your survey ID)”. This way, your data team will only receive notifications for anomalies detected in that survey.
    Shows an example of a condition set up to evaluate surveyID for iQ anomaly events.
  9. You can define the tasks for your workflow by clicking the plus sign ( + ). Tasks are the result of the workflow, see Workflows Overview for more information.