Skip to main content
Sitecore Documentation
  • Learn
  • Downloads
  • Changelog
  • Roadmap
PersonalizeCloud Portal
Sitecore Personalize
        • Getting started
        • Create a triggered experiment
        • Compose a webhook
        • Create a trigger
        • Apply a condition
        • Apply a segment
        • Using traffic allocation and variant traffic assignment
        • Use a decision model
        • Testing via Request Bin
        • Automatic goal tracking for triggered experiments
    • SitecoreAI experiments
    • Using the experiment list
    • Manage experiment details
    • Set automated post-test actions
    • Set up email notifications
    • Duplicate, delete, and view details
  • Using client-side JavaScript
  • Glossary
  1. Introduction to experiments in Sitecore Personalize
  1. Sitecore Personalize
  2. Introduction to experiments in Sitecore Personalize
  3. Introduction to triggered experiments in Sitecore Personalize

Automatic goal tracking for triggered experiments

Triggered experiments run when a specific event occurs, such as cart abandonment, a form submission, or a lifecycle interaction. After an experiment runs, Sitecore Personalize tracks customer actions within an attribution window. If a qualifying action occurs during this period, the action is attributed to the variant that triggered the experiment.

These attributed actions are used to calculate the experiment goals.

Automatically tracked metrics

Sitecore Personalize automatically tracks the following goals for triggered experiments:

  • Revenue - the total revenue generated by customers who receive the experiment.

  • Conversions - the total number of converted sessions (completed a desired action) after receiving the experiment.

  • Average order value (AOV) - the average value of transactions attributed to each experiment variant.

These goals allow you to compare the performance of experiment variants.

Attribution windows

Goal tracking for triggered experiments relies on attribution windows.

An attribution window defines the period of time after a triggered experiment runs during which customer actions can be attributed to that experiment.

Sitecore Personalize evaluates goals across multiple attribution windows to measure how quickly customers respond to triggered experiments. The system calculates goals for the following time frames: 1 hour, 3 hours, 1 day, 3 days, and 7 days.

If a customer completes a qualifying action, such as a purchase, within one of these windows, the action is attributed to the variant that triggered the experiment.

Attribution windows are configured at the system or organization level and apply consistently across all triggered experiment.

Example: Cart abandonment

A retailer runs a triggered experiment that sends reminder emails to customers who abandon their shopping carts.

  • Variant A sends an email offering free shipping.

  • Variant B sends an email offering a 10% discount.

If a customer returns and completes a purchase within the attribution window, the purchase is attributed to the variant that triggered the email. The purchase contributes to the automatically tracked goals: revenue, conversion rate, and average order value.

You can view these goals for triggered experiments in the Goals dashboard.

If you have suggestions for improving this article, let us know!

© Copyright 2026, Sitecore A/S or a Sitecore affiliated company.
All rights reserved.

Privacy policySitecore Trust CenterTerms of use