Configure One-Visitor-One-Campaign for Wingify Testing

This article covers the following:

• Overview
• Enable One-Visitor-One-Campaign
• How One-Visitor-One-Campaign Works
• Verify the One-Visitor-One-Campaign Setup
• Disable One-Visitor-One-Campaign
• Troubleshooting
• FAQs

Overview

When multiple campaigns run on the same URL, a visitor might become part of several tests simultaneously. This leads to overlapping results, making it difficult to determine which specific campaign influenced a visitor's conversion. The One-Visitor-One-Campaign feature ensures that a specific user participates in only one testing campaign at a time.

Enabling this feature provides cleaner data by preventing cross-campaign interference. It ensures that once a visitor is bucketed into a campaign, they are locked into that experience across the entire domain.

For example, imagine an e-commerce site is running three different tests: one on the home page, one on the product page, and one on the checkout page. With One-Visitor-One-Campaign enabled, if a user enters the site and qualifies for the homepage test, Wingify will not include them in the product page or checkout tests during that journey. This allows you to attribute their conversion purely to the first campaign they encountered.

Enable One-Visitor-One-Campaign

To enable this feature for your account, follow these steps:

1. Log in to your Wingify account.
2. Go to Profile > Settings > Campaigns.
3. Locate the 1 visitor 1 campaign section.

4. Select the Testing campaigns: ensure visitors participate in only one campaign checkbox.

   Attention: Enabling this setting impacts the entire account. While it ensures cleaner experiment data by preventing visitors from participating in multiple tests, it can reduce the number of visitors available for other concurrent campaigns. This happens because once a visitor is bucketed into the first eligible campaign they encounter, they are locked into that campaign and excluded from other testing campaigns. As a result, they cannot contribute to the sample size of later campaigns in their journey.
5. Click Save.

How One-Visitor-One-Campaign Works

After you enable the One-Visitor-One-Campaign feature and save the configuration, Wingify immediately changes how it buckets visitors across your testing campaigns. Here is the sequential breakdown of what happens:

• Wingify applies the rule account-wide for all A/B, Multivariate (MVT), and Split URL campaigns.
• Wingify prioritizes campaigns based on the order in which they were created. When multiple campaigns are eligible for a visitor, Wingify evaluates them in this order and assigns the visitor to the first campaign they qualify for. Once assigned, the visitor is bucketed into that campaign and won’t be evaluated for the remaining campaigns.
• When a visitor lands on your site, Wingify checks their eligibility for the highest-priority campaign first.
  • If they qualify, they are bucketed into that campaign.
  • Wingify then locks the visitor into that specific campaign. They are now automatically excluded from all other current and future testing campaigns in your account for as long as that campaign is running and the setting remains active.
• Since visitors are restricted to a single test, their conversion data is attributed solely to that campaign. This prevents noise in your reports caused by a visitor interacting with multiple experimental variables simultaneously.
• If a visitor was bucketed into a campaign that is later paused, they remain locked. They will not be freed up to join other active campaigns unless the One-Visitor-One-Campaign feature is disabled or their browser cookies are cleared.

Verify the One-Visitor-One-Campaign Setup

Once the feature is enabled, Wingify uses a specific cookie parameter to track the visitor's locked status. To ensure the configuration is correct and functioning as expected, you can manually verify it in your browser's developer tools. Follow these steps to verify the configuration:

1. Open your website in an Incognito mode or a Private browser window.
2. Navigate to a page where multiple testing campaigns (A/B, MVT, or Split URL) are currently running.
3. Right-click anywhere on the page and select Inspect to open the Developer Tools.
4. Go to the Application tab.
5. In the left sidebar, expand Cookies and select your website’s domain.
6. Look for the _vis_opt_exp_{CAMPAIGN_ID}_combi cookie. This cookie indicates which variation the visitor is seeing for a specific campaign.
7. To confirm the One-Visitor-One-Campaign restriction, check for the _wingify_uuid_v2 cookie or the Wingify library call in the Network tab.
   1. When this feature is active, Wingify should only trigger the tracking request for the highest-priority campaign.
   2. You will notice that requests for other eligible campaigns are not initiated, even if the visitor matches their segment criteria.

Tip: You can also use the Wingify Chrome Extension to quickly view which campaigns are active on a page. If the setup is correct, the extension will show the visitor as Excluded or Not Eligible for subsequent tests once they are bucketed into the first one.

Disable One-Visitor-One-Campaign

You can disable this feature at any time if you want visitors to be eligible for multiple overlapping tests.

1. In your Wingify account, go to Profile > Settings > Campaigns.
2. Scroll to the 1 visitor 1 campaign section.
3. Clear the Testing campaigns: ensure visitors participate in only one campaign checkbox.
4. Click Save.

Once you disable the feature:

• New and returning visitors are no longer restricted to a single campaign. They can be bucketed into any testing campaign for which they meet the segment criteria.
• Visitors who were previously locked into a specific campaign will now be able to participate in other active campaigns upon their next visit to the site.

Troubleshooting

FAQs

• Does this feature affect visitors who return on a different device or browser? 
  No. Visitor locking is based on browser cookies. If the same user visits the site from a different browser, device, or after clearing cookies, they may be treated as a new visitor and become eligible for another campaign.
• Can I change the priority of campaigns? 
  Wingify fixes campaign priority based on the order of creation. The first eligible campaign the visitor encounters is the one they will be locked into. Note: This setting is a global rule. It takes precedence over Campaign Priority rules and Mutually Exclusive Groups (MEG).
• What is the difference between One-Visitor-One-Campaign and Mutually Exclusive Groups (MEG)? 
  Both features are designed to prevent visitors from being part of multiple campaigns, but they operate at different levels.
  • One-Visitor-One-Campaign works at the account level and ensures that a visitor is included in only one testing campaign at a time. Once assigned, the visitor is excluded from all other testing campaigns.
  • Mutually Exclusive Groups (MEG) work at a group level, where you define a set of campaigns. A visitor can enter only one campaign within that group, but may still participate in campaigns outside the group.
• Can this feature be enabled for specific campaigns only? 
  No. The setting is applied at the account level. Once enabled, it affects all testing campaigns in the account and cannot be configured individually for specific campaigns.
• What happens if I disable the feature mid-test? 
  If disabled, visitors who were previously locked into one campaign can then become eligible for other active campaigns on the site upon their next visit.
• Does the feature apply to campaigns running on subdomains? 
  Yes. The feature applies across pages where the Wingify SmartCode is installed and operating within the same account. If a visitor is assigned to a testing campaign on one subdomain, they may still become eligible for campaigns on another subdomain depending on how cookies are configured and shared across domains.

Need more help?

For more information or further assistance, contact Wingify Support.