Common Missed Opportunities

Overview

These are common implementation mistakes that can silently reduce the effectiveness of your A/B testing setup. Each one is easy to fix once identified.

1. GA Revenue Tracking Disabled

GA revenue interception stops working when Revenue Tracking is turned off in the project settings. If you're expecting revenue data from GA purchase events, verify this setting is enabled.

2. Stopped Variations with Incomplete Traffic Allocation

When you stop a variation, the remaining running variations may not sum to 100% traffic allocation. The Convert UI does not warn about this — visitors allocated to the stopped variation simply receive no experience.

Additionally, forced and preview links for stopped variations remain accessible but will not bucket visitors, which can be misleading during QA.

3. Disabled Body Hiding Causes Flicker

The project setting "Disable body hiding" interrupts the tracking script's default anti-flicker logic. If flicker appears after enabling this setting, that is the cause.

The anti-flicker mechanism hides the page body briefly while variations are applied. Disabling it means the original content is visible until the variation code executes.

4. Lifecycle Listeners Must Be Registered Early

Convert's lifecycle event listeners only work when pushed to the queue either:

• Before the tracking script starts executing, or
• From GlobalJS

Events fired before the listener is added to the queue are missed. If you're registering listeners from VariationJS or ExperienceJS, they may miss early lifecycle events.

5. Synchronous Script Impacts Core Web Vitals

Only an asynchronous implementation of the tracking script guarantees no impact on Core Web Vitals. If CWV scores are a concern, use the async loading snippet with the anti-flicker protection.

See the Anti-Flicker Async Loading recipe for the implementation.