From 70e8b5c4926f336525809b539dae894cbd298dbf Mon Sep 17 00:00:00 2001 From: Danny-Driscoll Date: Thu, 24 Feb 2022 21:44:04 -0800 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7fea029..db8466e 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ The Optimizely starter kit for Fastly's Compute@Edge embeds and extends our [Jav This starter kit overrides the standard Optimizely Javascript SDK's external calls to use Compute@Edge's fetch against registered backend endpoints. This backend setup also provides performant caching for the [Optimizely Datafile](https://docs.developers.optimizely.com/full-stack/v4.0/docs/manage-config-datafile). ### Identity Management -Out of the box, Optimizely's Full Stack SDKs require a user-provided identifier to be passed in at runtime to drive experiment and feature flag decisions. This starter kit does not implement a persistent user identifier. Common approaches would include reading a unique visitor ID from a cookie-based header, or other existing unique identifier available within your application. +Out of the box, Optimizely's Full Stack SDKs require that an user identifier be passed in at runtime to drive persistent experiment and feature flag decisions. This starter kit does not implement a persistent user identifier. Common approaches would include reading a unique visitor ID from a cookie-based header, or other existing unique identifier available within your application. ### Bucketing For more information on how Optimizely Full Stack SDKs bucket visitors, see [here](https://docs.developers.optimizely.com/full-stack/v4.0/docs/how-bucketing-works)