---
title: Logging and Snippet Verification
slug: extensions/logging-and-snippet-verification
docTags: 
createdAt: 2026-09-22T18:20:22.602Z
---

## Logging

The cartridge writes logs under a custom SFCC category called `forter`. Add this category in Business Manager: **Administration > Operations > Custom Log Settings**, add category `forter`, log level `DEBUG` during integration or `INFO` in production.

The category has four loggers, each writing to its own file:

| Logger         | File pattern                 | Content                                  |
| -------------- | ---------------------------- | ---------------------------------------- |
| `forter-error` | `custom-forter-error-...log` | API failures, exceptions, void decisions |
| `forter-warn`  | `custom-forter-warn-...log`  | Retries, skipped pre-auth, fail-opens    |
| `forter-info`  | `custom-forter-info-...log`  | Entry points, job results                |
| `forter-debug` | `custom-forter-debug-...log` | Request/response bodies (PII)            |

Debug entries only appear when both the SFCC log level is `DEBUG` and `forterEnableDebugLogging` is `true`.

:::BlockQuote
**Note:** Set `forterEnableDebugLogging` back to `false` before production. Debug logs include PII.
:::

## Verifying the device fingerprint snippet

1. Open the storefront in a browser and go to any page.
2. **Elements tab**: search for `ftr__script`, confirm the tag exists with your `forterSiteID`.
3. **Network tab**: filter for `SaveToken`. Confirm a `POST` to `ForterToken-SaveToken` returns 200, with form data including `ftrToken`.
4. **Console tab**: confirm no CSP errors for forter.com domains.