Skip to content
Open
Changes from all commits
Commits
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
6 changes: 3 additions & 3 deletions docs/guides/first-device-level-experiment.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -45,10 +45,10 @@ You can implement a device-level experiment almost exactly like a traditional us
After setting up your experiment in the Statsig console, the next step is to integrate it into your client application using one of Statsig’s SDKs.

**Important:**
- **`userID`** should **only** should only be set for authenticated, logged-in users.
- For logged-out or anonymous users, use **`stableID`** (Statsig’s auto-generated device ID) or your own custom deviceID to identify the device. See [customID types](/guides/experiment-on-custom-id-types) if you have your own deviceID
- **`userID`** should **only** be set for authenticated, logged-in users.
- For logged-out or anonymous users, use **`stableID`** (Statsig’s auto-generated device ID) or your own custom deviceID to identify the device. See [customID types](/guides/experiment-on-custom-id-types) if you have your own deviceID.
- Always pass all known IDs to the SDK — Statsig will use the correct one for evaluation depending on the experiment or gate’s ID type.
- If you do rely on stableID, it is only generated by Statsig client sdks (javascript, react, mobile, etc) - server sdks are unable to generate this ID for you
- If you do rely on stableID, it is only generated by Statsig client SDKs (javascript, react, mobile, etc) - server SDKs are unable to generate this ID for you.
- **User attributes**: You can pass additional attributes like `appVersion`, and `custom` properties for experiment targeting.

#### Example (JavaScript):
Expand Down
Loading