Ship it to ten percent before everyone
Turn a feature on for a share of your visitors, watch what happens, and turn it off in one click if it goes wrong — no deploy, no rollback.
new-checkout25 %dark-mode100 %beta-editor10 %A new flag is always created off
Born off, always
A new flag is created disabled whatever its percentage. Creating and exposing in one gesture removes the second when you reread the key before anyone sees it.
A percentage that means something
At 25%, the same quarter of your visitors keeps the feature: the share is a hash of the flag key and the person, not a coin flip on every page.
Off means off, immediately
Flags are evaluated on each page load, so switching one off stops the feature without a deploy and without waiting for a cache.
How it works
Create the flag
A key for your code, a name for your team. It stays off until you decide otherwise.
Ask the tracker
Read the flag in your code to decide what to render for this visitor.
Open it progressively
10%, then 50%, then everyone — or back to zero if something breaks. Archive the flag once the feature is permanent.
Frequently asked
Can I rename a flag key?+
No. The key is written in your code, and renaming it here would silently turn the feature off. Names and descriptions can be changed freely.
Are flags evaluated before the page renders?+
Flags are fetched with the page's first measurement call, so a feature can flash if you render before reading it. For anything visible, read the flag before painting or hide the block until the answer arrives.
What happens if PulseTrack is unreachable?+
Your code keeps the value it already had, and a flag that was never answered stays off. The tracker never blocks your page.
Can I target specific accounts?+
Not yet. Today a flag is a percentage of visitors; targeting by account or by identified user is on the roadmap.