Skip to main content
How Can We Help?

Logging & Diagnostics

Posted
Updated
ByEmily Gomez
Bluvia A/B Testing includes diagnostic logging to help identify technical issues with the WordPress plugin.
Most users won’t need logging during normal use. Enable it when you’re troubleshooting a problem or when Bluvia A/B Testing Support asks you to collect additional diagnostic information.

Enabling Logging

To enable diagnostic logging:
  1. Navigate to Bluvia A/B Testing ā†’ Settings.
  2. Find Logging under Plugin Behavior.
  3. Enable Logging.
  4. Select Save Changes.
Once enabled, Bluvia A/B Testing can collect additional diagnostic information when critical plugin errors occur.

When Should You Enable Logging?

Logging is most useful when you’re experiencing a technical issue that can’t be resolved through normal troubleshooting.
For example, Support may ask you to enable logging if:
  • An experiment isn’t working as expected.
  • A plugin error occurs.
  • A feature isn’t loading or functioning correctly.
  • A technical conflict is difficult to identify.
  • Additional information is needed to investigate an issue.
You generally don’t need to keep logging enabled if Bluvia A/B Testing is working normally.

What Information Is Included?

When Logging is enabled, critical errors may be automatically reported to Bluvia A/B Testing for troubleshooting.
Diagnostic reports may include technical information such as:
  • Site domain
  • Active theme name
  • Bluvia A/B Testing plugin version
  • PHP version
  • WordPress version
  • Error description
  • Code stack trace
This information can help identify whether an issue is related to the plugin, WordPress environment, theme, or another technical component.

What Isn’t Included?

Diagnostic error reports are designed to provide technical information needed to investigate a problem.
They do not include:
  • Personal data
  • Page content
  • Visitor information
This allows Bluvia A/B Testing Support to investigate technical errors without requiring your website’s visitor or page content as part of the diagnostic report.

Logging and Troubleshooting

Logging is only one part of troubleshooting.
Depending on the issue you’re experiencing, you may first want to check:
  • Whether the experiment is Active.
  • Whether the Variant works in Preview.
  • Conversion Goal configuration.
  • WordPress caching.
  • CDN configuration.
  • JavaScript conflicts.
The guides in Troubleshooting can help you identify common issues before diagnostic logging is necessary.

After Troubleshooting

If you enabled Logging specifically to investigate an issue, you can return to Bluvia A/B Testing ā†’ Settings and disable it once troubleshooting is complete.
If Bluvia A/B Testing Support asked you to enable logging, follow any instructions they provide before disabling it so the necessary diagnostic information can be collected.

Contacting Support

If you continue experiencing an issue after following the relevant troubleshooting guide, contact Bluvia A/B Testing Support.
Include information that can help reproduce the problem, such as:
  • The experiment name, if applicable.
  • The page or feature affected.
  • What you expected to happen.
  • What happened instead.
  • Any error message you received.
  • Steps you’ve already taken to troubleshoot the issue.
Support may ask you to enable Logging if additional technical information is needed.
Never send passwords, one-time codes, or other account credentials when requesting support.

Related Articles

Continue with:

Tags: