Account
Troubleshooting
Most of these are the product refusing to guess. Each one names what is missing, and this page says what to do about it.
“Awaiting data” everywhere
- Nothing has synced yet. Connect billing first — it produces numbers without a deploy.
- If a source is connected, open Integrations: a failed first sync shows the provider error there rather than leaving the dashboard blank and silent.
The snippet is installed but visitors stay at zero
- The tracker ignores
localhost,file://and*.local, and the ingest endpoint checks the reported domain against the project's own domain. Preview hosts like*.vercel.appnever count. - Check the snippet is in the
<head>of every page, not only the homepage, and thatdata-website-idmatches this project. - Check
data-excludeis not swallowing the paths you are testing on. - Ad blockers stop some visitors. The tracker fails silently by design — it will never break your page to prove a point.
A source says “stale”
Stale means no successful sync inside that provider's window — six hours for billing, two for error and infrastructure sources, a day for Search Console. Its fields stop counting toward the score until it recovers.
- Expired or revoked credentials are the usual cause. Reconnect from Integrations.
- Force a sync rather than waiting for the next cron tick: the Integrations page has a sync action, and so does the API and CLI.
seiton integrations sync --provider stripe“Disconnect Stripe first to connect Polar”
One primary billing source per project, deliberately — it is what stops MRR being counted twice. Disconnect the current one to switch. The exception is Easytools, which runs on your Stripe account and connects as an overlay without touching MRR.
A webhook returns 503
- The
?website_id=parameter is missing. The signature has to be verified against one project's secret, and the endpoint will not guess which. Copy the URL from the Integrations page after connecting. - Or the signing secret was never pasted back into Seiton. Add it in the connect dialog and resend the test event.
The briefing never arrived
- Project settings → Reports lists recent sends with their status and the provider error, if any. Start there.
- Check the recipients are saved and the daily briefing toggle is on.
- Check the project timezone. Delivery is at the project's local time, and a project created in the wrong zone arrives at the wrong hour.
- Press Send briefing now to separate a delivery problem from a scheduling one.
- First send from a new domain lands in spam more often than it should. Check there.
Search Console shows a gap at the right edge
Google publishes Search Console data two to three days late. The gap is theirs. If the whole chart is empty instead, confirm the connected property is the one that matches this domain — a domain property and a URL-prefix property for the same site are different properties with different data.
Crash-free sessions is blank
Sentry has not reported it for that project. An empty tile is the honest answer; a plausible 99.8% would not be. Error volume still scores Reliability on its own.
Revenue attribution says low coverage
Attribution joins a payment back to the visitor who made it, and that join needs an id you attach at checkout — metadata.visitor_id on a Stripe Checkout Session, custom_data.visitor_id on Paddle, checkout metadata on Polar and Dodo. Without it the payment still counts as revenue; it just has no channel.
The API answers 402, 403 or 429
402— the trial ended. Subscribing restores access to the same data.403— the token lacks that scope, or the action is dashboard-only (deleting a website, connecting or disconnecting a payment provider).429— over 60 requests per token per minute. The response says when the window resets.
The score dropped right after connecting something
Expected. A newly connected source adds a dimension that was previously excluded from the average, so the composite moves to reflect a wider view of the same product. Coverage going from 4/8 to 5/8 next to the change is the explanation.
Still stuck?
Something here wrong or missing? hello@seiton.online