📗
UpGrade Platform - Documentation
6.0
6.0
  • UpGrade Overview
  • Creating an Experiment
    • Unit of Assignment
    • Simple Experiment
    • Factorial Experiment
    • Inclusion and Exclusion
    • Schedule and Post-Rule
    • Exporting Experiment Data and Design
  • Creating a Feature Flag
  • How UpGrade Works
  • Researcher Guide
  • Developer Guide
    • ⚡Quick Start: Running UpGrade Locally with Docker
    • ⚡Quick Start: Running locally w/o Docker
    • UpGrade + AdapComp (Mooclet) in Docker
    • 🚶‍♀️Walkthroughs
      • Your Application and UpGrade
      • Example 1: A Quiz Web App
      • Example 2: An Online Math Game
    • 📚Reference
      • API
      • Client Libraries
        • TypeScript / JS
          • Class: UpgradeClient
          • Class: Assignment
          • SDK Interfaces
            • Interface: IMetric
            • Interface: IExperimentUser
            • Interface: IExperimentUserAliases
            • Interface: ILog
            • Interface: IMarkExperimentPoint
            • Interface: IMetric
            • Interface: IRequestOptions
            • Interface: IResponse
            • Interface: IUser
            • Interface: IUserGroup
      • Environment Variables
        • Frontend Environment
        • Backend Environment
      • Context Metadata
      • Metrics
      • Setting up Google-Auth
      • API Authorization
      • Data Architecture
    • 👨‍💻Contributing Code
      • Branching Workflow (Git-Flow)
      • Pull Request Expectations
    • 😅Troubleshooting
      • Relation ‘experiment_condition’ already exists
      • User not found. Authorization error
      • Token is not present in the request header
      • nodemon exits without explanation
      • Unable to find New Relic module configuration
      • No email received for export data
      • Opening a new tab in UpGrade prompts for re-authorization
      • Error: Cannot find module 'upgrade_types' (or a type from 'upgrade_types' does not exist)
  • Glossary
Powered by GitBook
On this page
  1. Creating an Experiment

Schedule and Post-Rule

PreviousInclusion and ExclusionNextExporting Experiment Data and Design

You can choose to start the experiment at the time of its creation or schedule it to start any time in the future. You can end the experiment based on a condition too.

At the end, you can set the rules for what will happen when the experiment will end. You can either continue to give users the same condition they were in during the experiment, or change their final conditions to a default non-experiment condition.