OUR BOT
Keep Shopsteddy test traffic out of your customer numbers.
Shopsteddy uses real browser sessions for some tests, so those checks can look like visits in analytics. Where your analytics setup allows it, we recommend filtering or labelling Shopsteddy traffic.
The easiest identifier
Shopsteddy browser traffic uses a User-Agent containing NBTBot. If your analytics or tag-management setup can filter on User-Agent, that is the simplest place to start.
Common places to exclude it
At your edge or server
You can label Shopsteddy requests in Cloudflare or server logs using the User-Agent. This is useful for reporting and troubleshooting.
Before analytics loads
If you control your tag bootstrap, you can choose not to load analytics for Shopsteddy browser sessions.
if (!navigator.userAgent.includes('NBTBot')) {
// load analytics
}Server-side tag management
If events pass through your own server-side tagging layer, you can drop or label Shopsteddy events before they are sent to analytics providers.
Shopify reporting
Shopify does not provide one universal User-Agent exclusion switch for every report. Where needed, use Shopsteddy run times and your own reporting controls to separate test activity.
Removing Shopsteddy from your logs and reports
Shopsteddy cannot reach into your systems and delete log entries. If you do not want Shopsteddy traffic included in a report, filter it using the published User-Agent NBTBot/1.0 or, where your logging system records request headers, Shopsteddy-Scan-Id.
For old entries, use your own logging platform's filtering or retention tools. We recommend keeping security and audit logs intact where your own policies require them, and excluding Shopsteddy at the reporting or analytics layer instead.
User-Agent: NBTBot/1.0
Shopsteddy-Scan-Id: <scan UUID>We won't pretend a setting exists when it doesn't
Analytics products differ. If a platform cannot exclude Shopsteddy directly, we'll say so and point you towards the practical options that are actually available.