Projects are mentioned in various parts of the Optimize platform, but are a unique concept to Optimize. So... what are they exactly?
Project = folder of experiences
Your account can have many projects. Projects have some properties - a name, a linked location, a % throttle, and they contain experiences like Experiments, Baselines and Targets.
Project delivery
There are two key aspects to understand:
Multiple projects per page can be delivered.
One experience per project will be delivered.
So in Project 1, if you had:
Test 1: Mobile users
Test 2: PPC traffic
Test 3: London users
There is a cross-section of mobile users in london coming from PPC, who would be eligible for all 3 experiments but will only be served the first one. This creates a natural mechanism of mutual exclusion.
If you want users to be served all three of your Mobile, PPC and London tests at the same time, they should be built in separate projects despite being on the same page.
Understanding throttle
Webtrends Optimize allows traffic splits to be controlled by the “projects” mechanism as well as in-test and per-variant throttling for full flexibility.
This example shows how multiple projects are served in parallel, each test within a project can have its own % share (even or custom), and each variation within a test can have its own % share (even or custom). If the test receives an effective 10% of traffic as per Test 3, the variations at an even split get an effective 5% of traffic.