# Page Views

Instrumenting Page View lets you visualize user flows and sessions within the Spindl App. These are optional, but give you more insight into user journeys and sources of traffic.

Spindl supports two modes for Page View tracking:

### 1. Automatic Page View Tracking

You can initialize this once in the app, and Spindl will log Page View events automatically:

{% tabs %}
{% tab title="NPM SDK" %}

```javascript
spindl.enableAutoPageViews();
```

{% endtab %}

{% tab title="HTML Script SDK" %}

<pre class="language-javascript"><code class="lang-javascript"><strong>window.spindl.enableAutoPageViews();
</strong></code></pre>

{% endtab %}
{% endtabs %}

* Check out our [examples repo](https://github.com/spindl-xyz/sdk-examples/tree/main) to see how it's implemented in different contexts in Next.js/React or HTML

### 2. Manual Page View Tracking

You can call this method manually on every page load.

{% tabs %}
{% tab title="NPM SDK" %}

```javascript
spindl.pageView();
```

{% endtab %}

{% tab title="HTML Script SDK" %}

```javascript
window.spindl.pageView();
```

{% endtab %}
{% endtabs %}


---

# 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.spindl.xyz/spindl/techncial/javascript-sdk-html-script-guide/page-views.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.