Troubleshooting

No traffic appears

• Check the registered origin against the actual site, including HTTPS, www, and any port.
• Confirm the generated snippet is in the published site, rather than only in your local source.
• Use Check installation, then Run checks, from your website menu.
• Allow the Talvess origin in your Content Security Policy. Check whether an extension blocks the script or collector.
• Open the published site, choose the correct website, and select a date range that includes the visit.

Storage restrictions can explain missing visitors or sessions even when pageviews arrive. For installation steps, see Install the tracker.

Import problems

• Imports unavailable: the deployment's import configuration is unavailable. Try again later or contact support.
• Connection rejected: check your key, source account permissions, Stats API access, and the Simple Analytics user ID when required.
• Wrong totals: check the selected source site, inclusive dates, and source reporting timezone. Compare matching metric definitions.
• Interrupted import: inspect the error in Manage, use Resume when offered, or reconnect and choose a new period.
• History missing: wait for completion, then select the completed import in Analytics or use View history.

Imports contain aggregate reports, not reconstructed visitor journeys. See how to read imported history.

Unlinked signups

A received event with no linked attribution still counts as a confirmed signup. Check whether the browser had a persistent visitor ID, whether context reached the account-creation backend, and whether that context belongs to the same website as the server key.

For a separate signup origin or OAuth flow, use the explicit context handoff in the signup guide. A visit must be eligible and within the attribution window.

Get help

If you signed in and your websites are missing, check that you used the original Google or GitHub account.

Contact support with the website address, page or feature, expected behavior, steps to reproduce, approximate time and timezone, and a screenshot with private information removed. Include an error identifier if one is shown.

Never include passwords, server keys, database connection strings, or OAuth tokens. Revoke any exposed key before sharing a report.