Project

Your Hypertune project contains your:

  • Schema which defines your:

    • Flags, i.e. their names and types

    • Input types for flag targeting logic, e.g. User, Organization, Environment

    • Event types, e.g. SignUpEvent, PurchaseEvent with payload fields, e.g. revenueAmount

  • Logic

    • For flag targeting

  • A/B tests

    • Can be embedded anywhere in your flag targeting logic and reused across multiple flags

  • Machine learning loops

    • Can be embedded anywhere in your flag targeting logic and reused across multiple flags

  • Funnels

    • To see drop-off rates between different event types

    • To compare conversion rates across different arms of an A/B test or machine learning loop

All of these are saved together as a single commit in the Git-style version history for your project.

A new commit is created on your main branch any time you save new changes.

Hypertune uses the latest commit on your main branch when you consume your flags.

You consume your flags via:

PreviousArchitectureNextSchema

Last updated