Loading...
Loading...
ASM challenge makes Google Analytics stats appear as if they are 'Direct' instead of 'Organic'.
Incorrect data is displayed in the Google Analytics dashboard.
Scenario 1: -- ASM provisioned. -- ASM policy attached to a virtual server with challenge mitigation enabled (as part of brute force protection, for example). Scenario 2: -- Bot defense profile attached to a virtual server with challenge mitigation enabled. Scenario 3: -- DoS Application profile attached to a virtual server with challenge mitigation enabled.
Have an iRule that injects google-analytics.js into the challenge white page at the HTTP_RESPONSE_SENT time event.
ASM now handles the backend's response to fix up document.referrer for tools that read this property.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.