SiteSpect assigns a visitor arriving at your site to active Campaigns that they qualify for. When a visitor is assigned to a Campaign, that visitor has the opportunity to see, but may not be included in, a particular test experience. For example, it may be the case that the visitor arrives on the home page but the test focuses on a specific product page. It is also possible that this particular visitor may never get to that product page to see the active test. If this is the case, you do not want to count them and report on them for the Campaign since they have never been exposed to the test experience. Including them in the reporting would add unwanted noise. SiteSpect manages this using Counted settings.
There are two places you can specify this setting: Variations and Metrics.
Variations: Variations within the Campaign itself can manage counting. The setting is called Count users who see this Variation. It’s located on the Advanced Settings dialog for the Variation. To see it:
- Open the Campaign that contains the Variation.
- Locate the Variation.
- On the right side of the page in the same row as the Variation, click the three-dot menu and select Advanced Settings. Count users who see this Variation is set to Yes by default.
This is the default option for counting visitors in Campaigns within SiteSpect. This means that the visitor is counted and is included in Campaign reports only if they trigger (have seen) the Variation. SiteSpect counts them and continues to measure their behavior against the Metrics (such as Add to Cart, Purchase Complete, and so on) included in the Campaign while it is active.
Metrics: In some cases you may not want to or be able to use the Variation counting setting. In this case you can use a Metric instead to count visitors who see the test page or change that is applied in the Campaign. The setting is called Count users who trigger this Metric. It’s located on the Advanced Settings dialog for the Metric. To see it:
- Open the Metric.
- Click Show Advanced Settings on the right side of the page.
- Count users who trigger this Metric is set to No by default.
- For Origin Experiments, SiteSpect sets a cookie that is available across the visitor’s journey. Since the cookie is present at all times, SiteSpect doesn’t know when the visitor is exposed to the change. To get around this, use SiteSpect’s counting Metric to specify the location of the change within your site so SiteSpect knows when to include visitors in reporting for that Campaign.
See Using Metrics to Count Visits for more information.
When you set the counting parameter to No for all Variations and Metrics, visitors who see a Variation are not counted in reporting. In special circumstances, you may want set this value to No to prevent a visitor from being counted even if they see the Variations. For example, if a Variation exists solely to rewrite a URL link (href) to any of several alternate target pages, the act of rewriting the URL link should not cause the visitor to be counted. However, in this example, we recommend creating a Variation that triggers on the target page (even if the Search Text and Replacement Text are empty), so that the visitor is counted.
Q: A visitor comes to the site on a Monday and sees a Variation and is counted in the Campaign. Then you pause the Campaign. On Tuesday, the same visitor returns to your Site, when the Campaign is paused, and makes a purchase. Is that conversion included in the Campaign data for the Campaign the visitor was initially counted in?
A: While a Campaign is paused, SiteSpect collects no data for that Campaign. In the case described in the question, if the Campaign is still paused on Tuesday when the visitor converts, that conversion is not included in the Campaign data. However, if the Campaign is turned back on before the visitor converts, that conversion is included in the Campaign data.
Keep in mind that there is approximately a 45-minute data delay when you pause or end a Campaign. This means, once you pause a Campaign, you will see data trickling in for another 45 minutes or so. This is data collected for the visitors prior to the Campaign pause.
Q: What if a visitor bounces? For example, a visitor comes to your site and is exposed to a page with a Variation that is being tested and spends 30 seconds, but then exits. Is that bounce counted?
A: SiteSpect defines a bounce as a visit with only one page view, regardless of the length of time of the visit. This means that a visitor can spend 3 seconds, 30 seconds, or 3 minutes on the page; if it's the only page the visitor sees during the visit, SiteSpect considers it a bounce. SiteSpect counts bounces.