While not ideal, sometimes in an agency scenario, ...
# experimentation
w
While not ideal, sometimes in an agency scenario, we're limited to working with a single JavaScript file placed in the <head> of our client's website. Similar to how almost any client-side testing tool would work. Has anyone else been in a situation where they need to implement GrowthBook for experimentation this way? If so, could you share some tips or code examples? My plan so far: 1. In the JS file, load GB JS SDK 2. Define all relevant attributes and anonymous ID logic (using cookies) 3. What's the best call to get the experiment-variant decision? Considering targeting rules, traffic split etc are set on the Experiment in GB 4. Anything else to consider?
s
Were you able to figure this out? The GrowthBook JS SDK or script tag should be able to handle these requirements as is. Let me know if you ran into any road blocks.