-
Instead of passing data through a custom dimension like X Web, we use GA events. Specifically, we populate eventCategory, eventAction, and eventLabel with data specific to your Optimizely experiments. Here's some output from the GA Debugger Chrome Extension that is logged when the Optimizely Experiment activation event is fired.
-
In GA, you can now filter your users by those who have fired an event with the Action, Category, and/or Labels above. The label is (experimentId: variationId) and we'll send an event for each active experiment on a given page.
-
You can find the IDs for each of your experiments and variations by looking at the API Names in the Optimizely App.
Note: The integration could be modified to include readable names if you are willing to un-mask descriptive names.
In projectjs.js, there are areas that will need to be configured per site.
Line # | Configuration |
---|---|
18 | {YOUR_DOMAIN} |
82 | var prefix = '{custom_tracker}' + '.'; // Assign to ‘’ if no custom tracker |
87 | // Needs to be customized for specific websites. Defines how we identify if GA is available |