Source
Snippet performance & flicker — found from sitemap — GrowthBook
Checked for GrowthBook on 1 Oct 2026
- Page
- https://docs.growthbook.io/lib/edge/other
- Checked
- 1 Oct 2026, 10:33 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:1e0aa37090842bbe8d32bd0cc558433d6db3214adbeaaab8d40d5449552ec2f5
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Edge app beta Report an error
“Use the GrowthBook Edge App pattern on other CDN or edge providers to evaluate flags and rewrite HTML before it reaches the browser. BETA”
-
Edge utils version Report an error
“Edge Utils Resources v0.2.9 edge-utils npm”
-
No flicker visual experiments Report an error
“Automatically run server-side or hybrid Visual Experiments without redraw flicker.”
-
URL redirect no flicker Report an error
“Automatically run server-side or hybrid URL Redirect Experiments without flicker or delay.”
-
Sdk injection Report an error
“Optionally inject the JavaScript SDK with hydrated payload, allowing the front-end to pick up where the edge left off without any extra network requests.”
-
Edge URL redirect default Report an error
“The Edge App defaults to running URL Redirect Experiments in the browser only.”
-
Env run URL redirect Report an error
“You can enable URL Redirects on edge by setting environment variable RUN_URL_REDIRECT_EXPERIMENTS to “edge” or “everywhere”.”
-
Env cross origin redirect Report an error
“Additionally if your redirect is cross-domain (e.g. redirection from “public.mysite.io” to “newsite.io”), you must also set RUN_CROSS_ORIGIN_URL_REDIRECT_EXPERIMENTS.”
-
Required env vars Report an error
“PROXY_TARGET="https://internal.mysite.io" # The non-edge URL to your website GROWTHBOOK_API_HOST="https://cdn.growthbook.io" GROWTHBOOK_CLIENT_KEY="sdk-abc123" GROWTHBOOK_DECRYPTION_KEY="key_abc123" # Only include for encrypted SDK Connections”
-
Env visual editor default Report an error
“RUN_VISUAL_EDITOR_EXPERIMENTS="everywhere"|"edge"|"browser"|"skip" # default: "everywhere"”
-
Env disable injections Report an error
“DISABLE_INJECTIONS="true" # default "false"”
-
Env streaming Report an error
“ENABLE_STREAMING="true" # default "false". Streaming SSE updates on browser.”
-
Env sticky bucketing Report an error
“ENABLE_STICKY_BUCKETING="true" # default "false". Use cookie-based sticky bucketing on edge and browser.”
-
Default tracking frontend Report an error
“Running A/B tests requires a tracking callback. Our turnkey Edge App defaults to using built-in front-end tracking. The tracking call automatically integrates with Segment.io, GA4, and Google Tag Manager”
-
Edge tracking rationale Report an error
“Tracking on an edge or backend environment allows you to ensure the callback is fired before any differentiation across variations, eliminating experimental bias.”
-
Env tracking callback Report an error
“To change the front-end tracking callback, set the GROWTHBOOK_TRACKING_CALLBACK to your custom tracking JS code:”
-
Auto targeting attributes Report an error
“The following targeting attributes are set automatically by the Edge App. id - a long-lived user identifier, stored in a gbuuid cookie (see Cookie Policy and GDPR for how the cookie is written and when to use PERSIST_UUID) url path host query pageTitle deviceType - either mobile or desktop browser - one of chrome, edge, firefox, safari, or unknown utmSource utmMedium utmCampaign utmTerm utmContent”
-
Uuid customization Report an error
“You can customize both the primary identifier name (id) and cookie name (gbuuid) by setting the UUID_KEY and UUID_COOKIE_NAME environment variables respectively.”
-
Routing default Report an error
“By default, the Edge App will process all GET requests with Content-Type: text/html encoding (other HTTP verbs and content types are proxied through without running through our app logic).”
-
Routing routes env Report an error
“You will need to include a JSON encoded string of route rules in your ROUTES environment variable.”
-
Gbuuid cookie Report an error
“The Edge App uses a random unique identifier, stored in a first-party cookie named gbuuid, to provide a consistent user experience to your visitors by preventing them from being re-bucketed into different A/B test variations.”
-
Cookie persist default Report an error
“By default, the Edge App generates a gbuuid for each visitor and exposes it as the id targeting attribute, but it does not write the cookie from the edge server itself. Instead, the cookie is persisted in the browser by the injected front-end SDK once the page loads.”
-
Persist uuid env Report an error
“In these cases, set the environment variable PERSIST_UUID="true". The Edge App will then call your helpers.setCookie implementation to write a gbuuid cookie on the response, ensuring the cookie is stored on the first request.”
-
No auto cookies env Report an error
“If you must delay persisting the gbuuid cookie until a user consents, you can set the environment variable NO_AUTO_COOKIES="true".”
-
Consent persist event Report an error
“All you need to do is fire this custom event from JavaScript on the rendered page: document.dispatchEvent(new CustomEvent("growthbookpersist"));”
-
Sticky bucketing consent Report an error
“Either do not enable Sticky Bucketing on edge (do not use ENABLE_STICKY_BUCKETING) Or only enable Sticky Bucketing per each user via runtime configuration. (only pass config.enableStickyBucketing: true if user has consented — identifiable by checking for presence of the gbuuid cookie).”
-
Manual sdk Report an error
“To use the GrowthBook on edge, simply include our standard JavaScript SDK (@growthbook/growthbook NPM package).”
-
Payload fetch default Report an error
“By default, the Edge App will make a network request to the GrowthBook API on each user request in order to fetch the current feature and experiment values. This is a blocking call that delays page delivery.”
-
Keyval levels Report an error
“You can either completely eliminate the blocking call to the GrowthBook API by implementing a GrowthBook-to-edge-keyval push model via SDK Webhooks. Alternatively, you can eliminate most of these network requests by using an edge key-val store as a just-in-time payload cache.”
-
Sdk webhook config Report an error
“Select HTTP Endpoint as the Webhook Type. Set the Endpoint URL to your key-val provider’s REST API endpoint.”
-
Sdk webhook payload format Report an error
“Set the Payload format to “SDK Payload only”.”
-
Edge tracking callback code Report an error
“context.config.edgeTrackingCallback = (experiment, results) => {”
-
Skip auto attributes Report an error
“You can also skip automatic attribute generation and rely solely on custom attributes by setting the environment variable SKIP_AUTO_ATTRIBUTES="true".”
-
Supported features Report an error
“Supported Features Features Experimentation Case Insensitive Regex Case Insensitive Membership Saved Group References Encrypted Features Streaming v2 Hashing Visual Editor SemVer Targeting Visual Editor (JS) Visual Editor Drag & Drop Prerequisites URL Redirects Sticky Bucketing”
-
Slack Report an error
“Get help on Slack”
Scores citing this record
- The CRO Consultant Consent & visitor tracking
- The CRO Consultant Snippet performance & flicker
- The Data Protection Officer Consent & visitor tracking
- The Data Protection Officer Snippet performance & flicker
- The E-Commerce Manager Experiment types & delivery
- The E-Commerce Manager Consent & visitor tracking
- The E-Commerce Manager Snippet performance & flicker
- The Growth Lead Experiment types & delivery
- The Growth Lead Consent & visitor tracking
- The Growth Lead Snippet performance & flicker
- The Growth Lead Analytics, data export & integrations
- The Product Engineer Experiment types & delivery
- The Product Engineer Consent & visitor tracking
- The Product Engineer Snippet performance & flicker
- The Skeptic Experiment types & delivery
- The Skeptic Consent & visitor tracking
- The Skeptic Snippet performance & flicker