Understanding Low Checkout Alerts

Last updated: March 19, 2026

Noibu's low checkout alerts are designed to notify you when there's a significant drop in successful checkouts on your website compared to previous periods. However, you may occasionally receive alerts that appear to be false positives when you can verify that orders are still being processed normally.

Common Causes of False Positive Alerts

Script Deployment Issues

The most common cause of false checkout alerts is when the Noibu script is not properly deployed throughout your entire checkout flow, particularly on:

  • Billing/payment pages

  • Order confirmation/thank you pages

  • Pages that load after checkout steps

If the script is missing from these critical pages, Noibu cannot capture successful checkout events, leading to false alerts even when orders are completing normally.

Page Refresh and Session Continuity

When customers refresh pages during checkout, the Noibu script may lose session continuity if it's not explicitly included in the checkout flow headers. This can cause successful checkouts to go untracked.

Geographic Script Blocking

Script blocking for certain countries or regions can prevent Noibu from capturing checkout data, resulting in false alerts when orders from those regions complete successfully.

Cookie Blocking

Cookie blocking settings can interfere with Noibu's ability to track sessions through the checkout process, causing legitimate checkouts to appear as failures.

How to Investigate Alert Accuracy

Check Your Order Management System

First, verify in your own order management system or e-commerce platform whether orders were actually processed during the time period mentioned in the alert.

Verify Script Deployment

Use your browser's developer tools to check if the Noibu script is loading on all checkout pages:

  1. Navigate through your checkout flow

  2. Open developer tools and check the Network tab

  3. Look for the Noibu script (collect.js) and websocket connections

  4. Verify the script loads on every step, including the final confirmation page

Resolving Script Deployment Issues

If you discover the Noibu script is missing from parts of your checkout flow:

For Google Tag Manager Deployments

Ensure your GTM container fires the Noibu tag on all checkout pages, not just the initial pages. The tag should be configured to fire on "Container Loaded" events for all relevant pages.

For Direct Script Implementation

Add the Noibu script directly to your checkout page headers to ensure session continuity even if pages are refreshed during the checkout process.

When to Contact Support

Contact Noibu support if:

  • You've verified orders are processing normally but continue receiving alerts

  • The Noibu script appears to be properly deployed but alerts persist

  • You need help identifying gaps in script deployment

  • You suspect there may be a technical issue with the alerting system

When contacting support, include details about your order volume during the alert period and any recent changes to your checkout flow or script deployment.