> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/create-a-project/07-analytics-and-access.md).

# 07. Project analytics and feature access

Read project traffic reports when available and understand current feature-access limitations.

**Open:** your project → **see how many people visit it**, or builder **More options** → **Visitor numbers**.

## Availability first

SPAWN has no subscriptions or card payments; Stripe has been removed. Analytics availability can still depend on project access. If the interface displays an old paid-tier label or an upgrade button, it is not an available subscription checkout. Open the report from your own project and contact support if access is blocked.

## Use the report when your project has access

1. Sign in to the account that owns the project.
2. Open **Visitor numbers** for that specific project.
3. Read **Total Views**, **Unique Visitors** and **Referral Sources**.
4. Use **Views Over Time** to compare recorded activity by date.
5. Review **Traffic Sources** and any **Project inquiries** collected through your page.

These are the records available to SPAWN's report. Unique visitors are based on recorded visitor identifiers, not a verified count of individual people. Traffic-source reporting can be incomplete. Repeated visits, browser settings and blocked tracking can affect the figures.

## What success looks like

The report names the intended project and displays recorded views, sources or inquiries. An empty report means no records were returned; it is not proof that nobody ever opened the page.

## Troubleshooting

| Symptom                            | Resolution                                                                                                            |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Upgrade button opens publishing    | This is a current flow limitation; there is no documented self-service analytics purchase through that button.        |
| No views recorded                  | Confirm the page is published, use its public URL, and check again later.                                             |
| Counts differ from another service | Different collection rules and visitor identifiers produce different totals. Compare equivalent dates and metrics.    |
| Project not found                  | Use the owning account and open the report from the project rather than a copied URL with another project ID.         |
| No inquiries                       | Confirm the relevant page form is present and configured. Avoid collecting test submissions with real sensitive data. |

Handle inquiry details as private project information. Share only the minimum needed with your team, and never include visitor emails in public support screenshots.

***

[Guide home](/spawnmeme-docs/feature-guides.md) · [Troubleshooting](/spawnmeme-docs/feature-guides/reference-and-support/38-troubleshooting.md) · [Get help](/spawnmeme-docs/feature-guides/reference-and-support/39-support-and-safety.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/create-a-project/07-analytics-and-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.