September 2026 Summaries

No summary generated yet.

No summary generated yet.

No summary generated yet.

Fastly’s Next-Gen WAF and VCL can be configured to protect an origin from automated traffic while preserving marketing attribution that might otherwise be lost when users complete browser challenges. The approach addresses a common issue in which a post-challenge page reload replaces the original external Referer with the challenge URL, causing analytics platforms such as Google Analytics to misclassify traffic as direct. An NGWAF rule identifies suspicious requests and returns a 456 status while checking for an invalid challenge token to prevent verification loops, and VCL intercepts that response to serve a custom synthetic HTML challenge page. The embedded page includes Fastly Bot Management challenge scripts, client-side detection, Google Tag Manager or Google Analytics tracking, and JavaScript that reloads the requested page after verification succeeds. By handling the workflow at the edge, the method aims to provide a seamless visitor experience, retain accurate source attribution, and reduce unnecessary requests to the origin.