> For the complete documentation index, see [llms.txt](https://fulbix.gitbook.io/fulbix-fraud-and-ip-blocker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fulbix.gitbook.io/fulbix-fraud-and-ip-blocker/setup/persistent-visitor-protection.md).

# Persistent Visitor Protection

### The Problem: Fraudsters Who Keep Coming Back

When you block a visitor's IP address, a determined fraudster can simply:

* Reconnect on a different Wi-Fi network or mobile connection (new IP address)
* Clear their browser cookies and history
* Open a private/incognito browsing window
* Switch to a different browser

In all of these cases, a simple IP block fails — the visitor looks like a brand new person.

**Persistent Visitor Protection solves this.** Instead of relying on IP address alone, Fulbix creates a unique fingerprint from signals inside the browser itself — signals that remain consistent even when the IP changes or cookies are cleared.

***

### How Fingerprinting Works

When a visitor is flagged as suspicious, Fulbix records a fingerprint made up of browser characteristics such as:

* Screen size and resolution
* Browser type and version
* Installed fonts and graphics capabilities
* Hardware configuration signals
* Language and timezone settings

This fingerprint is not a cookie — it cannot be deleted by the visitor. The combination of these signals creates a unique enough profile to re-identify the same visitor across sessions.

> **Privacy note:** The fingerprint does not contain personally identifiable information. It is stored only for your store and is not shared with other merchants or third parties.

***

### Enabling Persistent Visitor Protection

1. Go to **Security** in the left sidebar.
2. Select the **Bot Protection** tab.
3. Scroll down to the **Protection Modules** section.
4. Find **Persistent Visitor Protection** and toggle it **on**.

The toggle saves instantly — no Save button needed.

***

### Setting the Track Duration

Once the toggle is on, a **Track Duration** dropdown appears below it.

This controls how long Fulbix remembers a flagged visitor's fingerprint. After this period, the fingerprint expires and the visitor is evaluated fresh on their next visit.

| Duration    | Best for                                                                         |
| ----------- | -------------------------------------------------------------------------------- |
| **7 days**  | Dealing with short-term fraud campaigns; lower risk of long-term false positives |
| **14 days** | A balanced default suitable for most stores                                      |
| **30 days** | High-risk stores with persistent fraudsters; maximum protection                  |

**Recommendation:** Start with **14 days**. If you are dealing with an active fraud campaign, increase to 30 days. You can change this at any time.

***

### What Happens When a Flagged Visitor Returns

1. Visitor was previously flagged as suspicious or blocked
2. They reconnect — new IP, cleared cookies, incognito window
3. Fulbix evaluates their browser fingerprint
4. The fingerprint matches a stored flagged record
5. The visitor is blocked or redirected, exactly as before

From the visitor's perspective, it looks like the block is still in effect even after they "reset."

***

### A Note for EU Merchants

Browser fingerprinting may be considered a form of tracking under GDPR in some interpretations. If your store serves EU customers, consider reviewing your Privacy Policy to mention that browser characteristics are analyzed for security purposes.

The fingerprint data does not include names, email addresses, or purchase history — it is purely a technical security identifier.

***

>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fulbix.gitbook.io/fulbix-fraud-and-ip-blocker/setup/persistent-visitor-protection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.