Post-purchase: Race condition causing Post-Purchase page bypass (15-20% loss in impressions)

Extensions
1

Hello Team,

We are experiencing a significant issue where a large percentage of customers are bypassing our post-purchase page. Instead of seeing the offer, they are redirected straight from the checkout to the Thank You page—even when ShouldRender is explicitly set to return true.

The Pattern:
Through internal testing, we have identified a consistent pattern: the bypass occurs when a customer completes the checkout faster than the ShouldRender script can execute. This is most prevalent with:

  • Shop Pay users: Accelerated checkout means almost zero friction.

  • 3-step checkouts: The script is triggered on the final step, leaving a very small window for execution.

Testing Conducted:
To isolate the issue, I simplified the ShouldRender logic to the absolute minimum:

() => {
  return {
    render: true
  };
}

Even with this near-instantaneous logic, we are still losing 15%–20% of checkout completions. This is resulting in a direct and measurable loss of revenue.

Question:
Since this is an in-house custom app and we have full control over the codebase, how can we ensure that 100% of eligible customers are served the post-purchase page? Is there a way to force a “wait” state or ensure the script takes priority over the final redirect?

Thank you for your assistance!