Here are some tools to help you identify issues if results aren't showing as you expect.
The logger logs information about your experiments to help you with debugging.
The error handler is called when unknown experiment keys or event keys are referenced. You can provide your own custom error handler logic to standardize across your production environment.
If you notice that events are not showing up in Full Stack, check the following possibilities first:
- UserIds may not be persisting. If a visitor's userID changes over the course of their visit, rebucketing can occur. This can have a direct effect on which events are fired. You will need to test your site end-to-end to ensure that userIDs persist for the entire duration of each user's visit.
- The datafilet may be out of date. If your datafile does not include all the entity keys—i.e., experiment_key, variation_key, etc—implemented in your site's code, this can have an impact on event firing as well. Ensure that your datafile is as fresh as possible.
Use notification listeners to trigger callbacks when certain actions are triggered in the SDK.
Currently, we support two types of listeners:
ACTIVATEtriggers a callback with the experiment, user ID, attributes, variation, and the impression event.
TRACKtriggers a callback with the event key, user ID, attributes, and event tags.
The Optiverse includes:
- Optimizely's Knowledge Base, which has help and support topics in addition to strategy and feature documentation.
- The developer community, where you can ask other developers about Optimizely’s SDKs.
If you need more help with troubleshooting, please contact support.