Skip to content

Event logger #3999

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
araf-statsig wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Event logger #3999

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
0edece4
client event logger
araf-statsig Feb 25, 2026
134caba
edits
araf-statsig Feb 25, 2026
423a878
merge conflict
araf-statsig Feb 25, 2026
497908e
Merge remote-tracking branch 'origin/main' into event_logger
araf-statsig Feb 25, 2026
f1c28ac
update call sites
araf-statsig Feb 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion client/introduction.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ If you have critical fields which define a user uniquely and are not in the `use

- The client SDK's `logEvent` call takes a custom event that you want to record to analyze the impact of the experiment on your end-user experience

- The client SDK automatically flushes all accumulated logged custom events to the Statsig servers every 10 seconds
- The client SDK automatically flushes all accumulated logged custom events to the Statsig servers every 60 seconds. [More Details] (https://docs.statsig.com/messages/clientEventLogger)

- Statsig uses these custom events to compute metrics as part of your experiment **Results**; Statsig automatically updates the **Metrics Lift** panel in the experiment **Results** tab daily around 9am PST

Expand Down
2 changes: 1 addition & 1 deletion sdks/client-vs-server.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ After initialization, both Client and Server SDKs evaluate experiments/gates *wi
|Checking an Experiment| Requires a user object which is evaluated locally (without a network request) against a ruleset persisted in memory | Does not require a user object, uses a dictionary lookup for values fetched during initialize() |
|User Identifiers| Pass any and all useful user identifiers | Pass any useful identifiers, the SDK also generates a "StableID", Statsig's anonymous ID you can use to experiment on a user per-device|
|Logging Events| Requires a user object | Does not require a user object. Note, there is some risk of adblocking log events on client SDKs, which can be minimized by setting up a [Custom Proxy](../custom_proxy)|
|Flushing Events| Batched and flushed by the SDK every 60 seconds | Batched and flushed by the SDK every 10 seconds|
|Flushing Events| Batched and flushed by the SDK every 60 seconds | Batched and flushed by the SDK every 60 seconds [More Details] (https://docs.statsig.com/messages/clientEventLogger)|
|Updating Configurations| Poll Statsig servers for updates every 10 seconds by default (configurable), Streaming possible with some Server SDKs and the [Statsig Forward Proxy](/server/concepts/forward_proxy) | Configuration persists until next `initialize` or `updateUser` call, recommended to call `initialize` at the start of each user session|

## Difference in initialize/update logic:
Expand Down