From 4018e10b40d72ce0c29d48ecdd92a40ca6f3c960 Mon Sep 17 00:00:00 2001 From: Brock Lumbard Date: Mon, 23 Dec 2024 19:36:13 -0600 Subject: [PATCH] typo --- docs/faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq.mdx b/docs/faq.mdx index ce80e3827..dc5af2dcb 100644 --- a/docs/faq.mdx +++ b/docs/faq.mdx @@ -73,7 +73,7 @@ If none of our current SDKs meet your needs, please let us know via our [Slack c If you're interested in historical exposures, the console's [users tab](https://console.statsig.com/users) may server your needs. -If you need all hypothetical assigments, you can consider using the `getClientInitializeResponse` server sdk method. Statsig's SDKs should ideally be invoked at the time you're serving an experiment treatment, so that an exposure can be logged. If that's not possible in your case (perhaps you need to pass assignment information to other applications, or to use assignment information as cache-keys for the CDN + edge), this approach could work. +If you need all hypothetical assignments, you can consider using the `getClientInitializeResponse` server sdk method. Statsig's SDKs should ideally be invoked at the time you're serving an experiment treatment, so that an exposure can be logged. If that's not possible in your case (perhaps you need to pass assignment information to other applications, or to use assignment information as cache-keys for the CDN + edge), this approach could work. #### Example of capturing all assignments in Node