Category: AB Testing
This integration is only available for Web projects
What to expect
This integration will allow you to segment and compare users and pages based on Webtrends campaigns and variations.
What we collect
Dynamic Variables
Key | Value | Data Type |
AB_WT_{campaignName} | {variationName} | Text |
Implementation
Implementation Steps
Please go to the section How to request an integration to see the instructions to enable this integration. You can then return here once completed.
If you have already completed the step above then continue below.
In order to utilize the Contentsquare Webtrends Optimize integration, you will need to first enable the Optimize Build Framework and then add it to the campaign they wish to monitor.
In order to do so, please follow these steps:
In the navigation, go to Manage -> Integrations.
Click New Integration
Choose Optimize Build Integration
Click Install Integration
Set Integration Status to On and choose a tag to apply it to
Press Save
Once done you should see it enabled for your WTO account
Next you’ll need to add an Optimize Build Platform framework to your campaign.
In your project wizard (when you edit or create a new project), in the first Details step, enable the check box Include Optimize Build Framework?.
Continue to the Variations step and backup the JS content of the variations (it may get overwritten once OBF is enabled).
Continue to the Scripts step. You’ll be prompted to enter a unique number (of your choice) and a page load confirmation selector (if there’s no indicator for page load, you can just put in body)
Once saved it should populate the default script fields
Return to the Variations step (you can do so using the tab). And edit the variations' JS
You should see a new line of code allowing you to set the variation's friendly name for integrations
You can change the second variable sent to any variation name you'd like to see in the integration. By default they should be "F1L1", "F1L2" and so on… If there was code there before that was overwritten, paste it back in.
Verifying it works
You can use the chrome extension to check the results are sent to CS