Operating
Troubleshooting
The four things people write in about, each with the places to look, in the order that finds the cause fastest.
Updated All docs as one Markdown file
No visits are arriving
- You are on localhost. The script ignores it unless the tag carries data-allow-localhost.
- The tag is not on this page, or loads twice. View the page source and search for data-website-id; it should appear once, with this website's id.
- A Content-Security-Policy blocks it. The console says so; allow https://geckostats.com in script-src and connect-src, or serve the script from your own domain.
- A content blocker drops the request. Serving the script from your own domain (see Install) gets past most of them.
- The request is sent but refused. In the Network tab, the POST to https://geckostats.com/api/event should answer 202; a 4xx means a wrong website id or a domain that does not match the website's.
The install step of each website watches for the first event and says when it has arrived, so leave it open while you check.
A payment is missing or not attributed
- Is it held? The Connect payments step lists payments waiting for a visit. If the sale is there, the webhook worked and the identity did not arrive with it: check the metadata and the success page on the attribution page.
- Did the webhook arrive at all? The endpoint URL must carry this website's id, the secret must be the one pasted into the step, and the provider must be sending the events listed on the webhooks page. Test mode and live mode are separate endpoints with separate secrets.
- Is it on another website? Two websites on one Stripe account each receive every payment; the placement rules on the Stripe page decide which records it.
- Is it an amount problem? The server-to-server API takes major units, 29.99 not 2999.
The search panel is empty
- Search Console publishes about three days late. Today and yesterday are never there; widen the period.
- The first sync runs when the property is chosen; after that it is hourly, a few days at a time, ninety days of history filling in backwards. The Search Console step says how far it has got.
- The property has to be the one that holds this website's data. A domain property covers every subdomain and protocol; a URL-prefix property covers exactly that prefix.
The numbers differ from another tool
- Visitors are counted without cookies, from a hash that rotates daily, so a person who returns tomorrow is a new visitor here and a returning one in a tool that sets a cookie. Turn cookie mode on in the website's settings if identity across days matters more to you than the privacy property.
- Your own visits are left out once owner exclusion is on, and traffic from your other domains stops being a referral once they are listed.
- Crawler hits are counted separately and never as visitors.
- Times are in the website's timezone and money in its currency, both set in its General settings; a tool on a different clock splits days differently.