Tool for Optimizely experiment callback - I included my github link so you can use it too
I've created a little tool to help developers achieve experiment callback.
It's really helpful when you need to know which experiment is being called right after Optimizely has loaded the state object.
Hope it helps more people.
Thanks for sharing this! This is great. Would you mind sharing a few of the use cases that you created this for?
I can see this to be very useful when pulling information out of the state object and passing it to an analytics platform.
This is a really great tool. I gave it a whirl and I was easily able to see exactly what variation was running for any experiment ID. This looks like a superb way to make QA easier on pages where multiple experiments are running at once. Were there some other QA scenarios you had envisioned?
I also had a couple other questions:
- What's your reasoning behind loading Optimizely asynchronously?
- Had you thought about modifying this code to accept multiple experiment IDs in one call?
Solutions Architect | Optimizely, Inc.
hi @Harrison_Krat, sorry I couldn't answer you earlier.
We're using this solution on a portal that has billions of requests per day and we tend to shave every millisecond of the page first paint, loading this script synchronously to every user, could impact us.
And imagine if the optimizely server got unavailable, then the user would have to wait for the script timeout.
It's really easy to change the code to support multiple experiments.
@Junan We're currently using this to have a better control of our tests and avoiding impact on the page load time and first paint.
This way, you can control on your side what to do when the tests load.