When does it make sense to group domains in a single configuration vs. separate configurations?
Configuration Trade offs
| Grouped Domains | Separated Domains |
| + Easily test and track user across sub domains by top level domain (*.topleveldomain.com). Therefore, common reporting across domains. 1 | - Will not test users across domains that are separated by configuration. Reporting separated by domains per configuration. 1 |
| - Common concurrent ceiling per configuration 2 | + Separate concurrent ceiling per configuration |
| - Need to use host triggers when isolating domains to test on | + No additional steps needed to isolate testing on specific domains |
| + No need to export and import campaigns from another environment. Manage a single set of metrics and audiences (and global variations that support things like analytics integrations) | - Re-using a campaign structure on another configuration requires exporting and importing the campaign and managing duplicate metrics and audiences |
| ~ One set of cookies (per top level domain) | ~ A new set of cookies per configuration (user only sees them if they visit one of the domains) 3 |
| ~ Control Panel Permissions apply to more domains | ~ Control Panel Permissions apply to less domains |
1. It may be an option to use Engine API to trigger metrics in reporting across domains. Users could still be tracked across different top level domains with the use of OmniChannel.
2. Concurrent ceiling settings are configurable, please consult your Account Manager.
3. It is recommended to specify each configuration use unique SiteSpect cookie names, e.g. SSID_C1 where SSID is the “base” name. This will prevent loss of assignments when a user does pass from a domain in one configuration to another.
+ Could be considered to be more efficient - depending upon workflow
- Could be considered to be less efficient - depending upon workflow
~ Could be neutral - depending upon organizational governance
Note: There are generally few limitations on what domains can exist in a single SiteSpect configuration. This means, for example, that a staging site and production site can be in the same configuration and yet be isolated in terms of traffic. In this scenario it would enable targeting a campaign to traffic simply by changing the audience or host trigger. And would eliminate the steps of export and import as well as provide an environment of managing only one set of metrics and audiences.