Skip to content

Commit 6a76a17

Browse files
api feedback
1 parent ae07996 commit 6a76a17

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

src/content/docs/cloudflare-challenges/challenge-types/javascript-detections.mdx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ If you enable JavaScript Detections via the dashboard, Cloudflare will insert a
3737

3838
The JavaScript Detections API allows you more granular control over when and where JavaScript Detections are injected on your website, as well as an option for callback handling (for logging or other additional actions).
3939

40-
You can explicitly add a script reference to `jsd/api.js` and your own code calling `window.cloudflare.jsd.executeOnce` on specific HTML pages of your website.
40+
You can explicitly add a script reference to `/cdn-cgi/challenge-platform/scripts/jsd/api.js` and your own code calling `window.cloudflare.jsd.executeOnce` on specific HTML pages of your website.
4141

4242
:::caution
4343
It is not recommended to combine both approaches (zone-wide toggle and the manual injection). If you want to selectively deploy JavaScript Detections only on certain pages, disable JavaScript Detections via the Cloudflare dashboard and use the JavaScript Detections API exclusively.
@@ -60,6 +60,10 @@ function jsdOnload(){
6060
<script src="/cdn-cgi/challenge-platform/scripts/jsd/api.js?onload=jsdOnload" async>
6161
```
6262
63+
:::note
64+
`result` = `success` or `error` only refers to the execution of JavaScript Detections. It does not indicate whether a visitor is a human or a bot.
65+
:::
66+
6367
## Considerations
6468
6569
JavaScript Detections do not guarantee a specific bot score.

0 commit comments

Comments
 (0)