Skip to main content
How Can We Help?
Cookie & Visitor Tracking
Bluvia A/B Testing uses cookies to help maintain a consistent experiment experience for visitors.
When a visitor participates in an experiment, Bluvia A/B Testing uses a cookie to remember which version of the experiment that visitor was assigned to. This helps ensure that visitors continue seeing the same Control or Variant as they navigate and return to the experience.
How Visitor Assignment Works
When an eligible visitor enters an experiment, Bluvia A/B Testing determines which experience the visitor should see based on the experiment’s Traffic Allocation.
Depending on the experiment, the visitor may be assigned to:
- The Control
- Variant 1
- Variant 2
- Another Variant included in the experiment
Bluvia A/B Testing then uses a cookie to remember that assignment.
This means a visitor assigned to the Control should continue seeing the Control, while a visitor assigned to a Variant should continue seeing that Variant.
Each experiment assigns visitors independently, so a visitor seeing the Control in one experiment may be a part of a variant in another experiment.
Why Visitor Assignment Stays Consistent
Consistent assignment is important for both the visitor experience and the accuracy of your experiment.
Without it, the same visitor could see the Control during one visit and a Variant during another. That could make the experience confusing and make it harder to understand which version influenced the visitor’s behavior.
Maintaining the visitor’s assignment helps Bluvia A/B Testing associate activity and conversions with the experience that visitor received.
Refreshing Doesn’t Change Your Variant
If you’re checking an experiment yourself, repeatedly refreshing the page won’t necessarily show you a different Variant.
Your browser may already have a cookie identifying the version of the experiment you’ve been assigned to.
For example, if you’re assigned to the Control, refreshing the page doesn’t mean you’ll eventually receive Variant 1.
This is expected behavior and doesn’t mean the Variant isn’t running.
If you need to inspect a specific Variant, use the experiment’s Preview functionality.
Cookies and Conversion Tracking
Visitor assignment also helps Bluvia A/B Testing understand which experience was associated with a conversion.
For example, a visitor might:
- Enter an experiment and receive Variant 1.
- Interact with the website.
- Complete the configured Conversion Goal.
Maintaining that visitor’s experiment assignment allows the conversion to be associated with the experience they received.
This helps you compare the performance of the Control and Variants in your experiment report.
Cookies and Traffic Allocation
Traffic Allocation determines how eligible visitors are distributed across your experiment.
For example, an experiment might allocate:
- 50% to the Control.
- 50% to Variant 1.
This doesn’t mean the same visitor alternates between the two experiences.
Instead, visitors are assigned according to the configured allocation, and the cookie helps maintain each visitor’s assignment afterward.
See Experiment Settings for more information about Traffic Allocation.
GDPR and Cookie Consent
If your website uses a cookie consent solution, Bluvia A/B Testing includes a GDPR Cookie setting that can be used with your website’s consent configuration.
Go to Bluvia A/B Testing ā Settings and locate GDPR Cookie under Tracking Settings.
Enter the cookie name associated with your website’s consent implementation.
Because cookie consent requirements and implementations vary between websites and jurisdictions, make sure your website’s consent configuration reflects the privacy requirements that apply to your organization.
For information about the setting itself, see Plugin Settings.
Testing Your Own Experiments
When reviewing a live experiment yourself, remember that your browser behaves like other participating visitors.
Once you’re assigned to an experience, Bluvia A/B Testing may continue showing you that experience because of your existing visitor assignment.
For quality assurance, use Preview when you need to verify a particular Control or Variant.
You may also want to exclude internal traffic from experiment tracking so repeated visits from your team don’t affect your results.
See Excluding Internal Traffic for more information.
Cookies vs. Targeting
Cookies maintain the experiment experience a visitor has been assigned to. They don’t replace your experiment’s Targeting Rules or Exclusion Rules.
Targeting Rules determine whether a visitor is eligible for an experiment.
Exclusion Rules determine which visitors should not participate in a particular experiment.
Traffic Allocation determines how eligible experiment traffic is distributed between the Control and Variants.
Visitor assignment cookies help keep the resulting experience consistent for that visitor.
Together, these controls determine who participates and what experience they receive.
Related Articles
Continue with:
