Skip to content

Commit 695a0c8

Browse files
vladfalonGitHub Enterprise
authored andcommitted
Merge pull request #6559 from AdobeDocs/Updating-bot-detection-considerations
PDCL-14480-Bot Detection docs improvements
2 parents 873aee3 + 103d7c3 commit 695a0c8

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

help/datastreams/bot-detection.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,13 @@ This bot scoring helps the solutions receiving the request correctly identify bo
2929
>
3030
>Adobe solutions may handle bot scoring in different ways. For example, Adobe Analytics uses its own [bot filtering service](https://experienceleague.adobe.com/docs/analytics/admin/admin-tools/manage-report-suites/edit-report-suite/report-suite-general/bot-removal/bot-rules.html) and does not use the score set by the Edge Network. The two services use the same [IAB bot list](https://www.iab.com/guidelines/iab-abc-international-spiders-bots-list/), so the bot scoring is identical.
3131
32-
Bot detection rules can take up to 15 minutes to propagate across the Edge Network after being created.
32+
## Technical considerations {#technical-considerations}
33+
34+
Before enabling bot detection on your datastreams, here are a few key points to keep in mind to ensure accurate results and a smooth implementation:
35+
36+
* Bot detection applies only to unauthenticated requests sent to `edge.adobedc.net`.
37+
* Authenticated requests sent to `server.adobedc.net` are not evaluated for bot traffic, as authenticated traffic is considered trustworthy.
38+
* Bot detection rules can take up to 15 minutes to propagate across the Edge Network after being created.
3339

3440
## Prerequisites {#prerequisites}
3541

0 commit comments

Comments
 (0)