# Advanced Configuration

Signet is opinionated by default but flexible when necessary. The initialization object accepts several optional parameters that allow you to fine-tune how data is collected and processed.

#### Proxying and Custom Domains

For enterprise deployments requiring maximum data resilience, you may choose to proxy Signet traffic through your own domain. This technique mitigates the risk of client-side blockers interfering with the script delivery.

You can configure the SDK to direct traffic to a specific endpoint on your own infrastructure, which then forwards the payload to Signet.

```
code Tsx
downloadcontent_copy
expand_less
<SignetProvider
siteId="YOUR_ID"
apiHost="https://analytics.yourdomain.com"
/>
```

#### Hash-Based Routing

Legacy applications or specific electron-based web apps may utilize hash-based routing where the URL changes after the # symbol. By default, many trackers ignore these changes. Signet can be configured to treat hash updates as unique page views.

```
 code Tsx
downloadcontent_copy
expand_less
<SignetProvider 
  siteId="YOUR_ID"
  hashRouting={true}
/>
```

#### Excluding Traffic

While you can filter traffic in the dashboard, it is often more efficient to prevent specific traffic from being sent at the source. The ignoreRoutes configuration allows you to define an array of path patterns that should strictly be ignored by the tracker. This is useful for admin panels, draft previews, or internal tools.

```
 code Tsx
downloadcontent_copy
expand_less
<SignetProvider 
  siteId="YOUR_ID"
  ignoreRoutes={['/admin/*', '/staging/*']}
/>
```


---

# Agent Instructions: 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:

```
GET https://docs.signtoken.vip/3.-implementation/advanced-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.