Cloudflare and server logs
Label NBT traffic for reporting, but keep the original security and audit record.
ANALYTICS
Test traffic should not look like customer traffic.
If your analytics or edge setup allows it, label or exclude NBT QA traffic using the published bot identity.
Useful identifiers
User-Agent contains: NBTBot
NBT-Scan-Id: <opaque run UUID>Use the scan ID to trace a request. It deliberately contains no account name or customer identity.
Where to filter
Browser analytics
If your tag loader can see the browser User-Agent, you can avoid loading non-essential analytics for NBT browser sessions.
Server-side tagging
Drop or label known NBT QA events before forwarding them to analytics destinations.
Historical reports
Prefer report filters to deleting security logs. NBT cannot remove records from your systems remotely.