Last updated
Was this helpful?
Flag events in Reflag are generated automatically in some cases and sent by the client in others. Reflag uses these events to track flag access and collect data that helps debug rule and context issues.
This event is generated automatically on the Reflag side when the client uses server-side flag evaluation, for example with @reflag/browser-sdk or @reflag/react-sdk. It is generated on the client side when local evaluation is used, for example with local mode in @reflag/node-sdk.
This event contains the following information:
The actual context that was used to evaluate the flag access,
Some details of the flag whose access rules were evaluated,
The result of the access evaluation, including missing fields that were expected in the targeting rules.
This event is generated by all Reflag SDKs whenever client code checks whether a flag is enabled for a given context.
This event contains the following information:
The actual context that was used to evaluate the flag access,
Some details of the flag,
The result of the access check.
Reflag SDKs rate-limit these events to avoid unnecessary traffic. Unknown flag evaluations and checks are still sent to Reflag to help with debugging.
Learn about targeting rules,
Learn how to set up flag access rules within Reflag UI.
Last updated
Was this helpful?
Was this helpful?