Skip to main content
How Can We Help?

Conversion Not Tracking

Posted
Updated
ByEmily Gomez
If your experiment is running but conversions aren’t being recorded as expected, start by reviewing the Conversion Goal configured for the test.
Bluvia A/B Testing records conversions when participating visitors complete the action defined by your Conversion Goal. If the goal isn’t configured correctly or the expected action isn’t being completed, a conversion won’t be recorded.

Confirm the Test Is Active

First, make sure the experiment is currently running.
Navigate to Bluvia A/B Testing ā†’ Test Library and confirm that the experiment’s status is Active.
If the experiment is Draft, Scheduled, Paused, Completed, or Archived, new conversions won’t be collected.
If your experiment isn’t running as expected, see Test Not Running.

Review Your Conversion Goal

Open the experiment and confirm that the correct Conversion Goal is selected.
Bluvia A/B Testing currently supports the following Engagement and Developer Goals:
  • Click on Element ā€” Tracks when visitors click a selected button, link, or element.
  • Submit a Form ā€” Tracks when visitors submit a selected form.
  • Scroll of Page ā€” Tracks how far visitors scroll on a page.
  • View a Page ā€” Tracks visits to a selected page or post.
  • Click External Link ā€” Tracks clicks to a specified outbound URL.
  • Trigger Custom JS Event ā€” Tracks when a specified custom JavaScript event occurs.
Make sure the selected goal represents the action you’re expecting Bluvia A/B Testing to record.
For a complete explanation of each option, see Conversion Goals.

Check the Goal Configuration

Each Conversion Goal requires different information. If conversions aren’t being recorded, review the configuration for the goal you’re using.

Click on Element

Confirm that the correct element is selected.
The goal should be connected to the button, link, or other element you want visitors to click.
If the page or element has changed since the experiment was created, confirm that the intended element is still being tracked.

Submit a Form

Confirm that the correct form selector has been configured.
Bluvia A/B Testing uses the form’s ID or Class to identify the form that should trigger the conversion.
You can enter the selector or use Choose Selector to select the appropriate form.
If the form, its ID, or its Class has changed since the experiment was configured, review the selector before continuing.

Scroll of Page

Confirm that the selected scroll threshold represents the engagement you want to measure.
A conversion is only recorded when the visitor reaches the configured point on the page.
If visitors aren’t scrolling far enough to reach that threshold, you may see fewer conversions than expected.

View a Page

Confirm that the correct target page or post has been selected.
A conversion is recorded when a participating visitor reaches the content configured as the target.
If the destination has changed, verify that the correct page or post is still selected.

Click External Link

Confirm that the Target External URL matches the outbound link you want to track.
If the destination URL has changed or a different outbound link is being clicked, the expected conversion may not be recorded.

Trigger Custom JS Event

Confirm that the Event Name exactly matches the custom JavaScript event triggered by your website.
Because this is a Developer Goal, also confirm that your website is successfully firing the expected event.
If the event isn’t firingā€”or the configured event name doesn’t matchā€”the conversion won’t be recorded.

Make Sure You’re Participating in the Experiment

A conversion needs to be associated with a visitor participating in the experiment.
If you’re manually testing a conversion, confirm that you’re eligible for the experiment based on its:
For example, if administrators are excluded and you’re testing while logged into WordPress as an administrator, your activity may not be included in the experiment.

Remember Your Visitor Assignment

Bluvia A/B Testing uses cookies to remember which version of an experiment a visitor has been assigned to.
When testing conversions yourself, your browser may already be assigned to the Control or a specific Variant.
This consistent assignment is intentional and helps Bluvia A/B Testing accurately associate visitor behavior with the experience they received.

Allow Time for Results to Update

After completing a conversion, return to the experiment report and review the results.
If the conversion doesn’t appear immediately, allow a short period for the reporting data to update before repeating your test.
Avoid generating large amounts of artificial test activity, as this can affect the accuracy of your experiment data.

Check for Website Conflicts

If the experiment is Active and the Conversion Goal appears to be configured correctly, another part of your WordPress environment may be interfering with tracking.
Potential causes can include:
Continue with the relevant troubleshooting guide to investigate these issues further.

Still Not Tracking?

If you’ve confirmed that the experiment is Active, the Conversion Goal is configured correctly, and an eligible visitor has completed the expected action but conversions still aren’t being recorded, contact Bluvia A/B Testing Support.
When contacting Support, include:
  • The experiment name.
  • The test type.
  • The Conversion Goal being used.
  • The URL where the conversion should occur.
  • The action you expect to trigger the conversion.
  • Whether the issue affects the Control, a Variant, or both.
  • Any relevant error messages or unexpected behavior.
This information can help the Support team investigate the tracking issue more efficiently.

Related Articles

Continue with: