Stabilizing "Random" Selections With Your Visitor Identifier

In some Conductrics usage scenarios (for instance, when using Conductrics both server-side and client-side), there can be cases where your experiments would benefit if variation selections remained "stable" in different contexts. Conductrics doesn't build a unified/stitched "profile" of your visitors, so there isn't a single centralized record of what variations have been assigned to each visitor. This is by design, but sometimes gets in the way when attempting to coordinate visitor experiences across different channels or multiple browsers.

This functionality is currently in Beta - please reach out to Conductrics if you're interested in trying it out.

Please refer to this working document for details.