The snippet is not verifying
The dashboard connection status stays unverified after you install. Likely causes and fixes:- The snippet is not on the live site. View source on a published page and confirm the script tag is present in the
<head>. Republish or deploy if it is not. - It was placed in the wrong website. The snippet loads by SDK key, so a key from a different website will not verify the one you are looking at. Confirm you copied the key for the correct website. See Install the snippet.
- No page view has happened yet. The status flips after a real page view. Load a page on the live site, then recheck.
- A consent or tag manager gate is blocking the script. If you load it through a tag manager, confirm the trigger fires on all pages and is not held behind a consent condition.
No or low visitors identified
The snippet verifies, but few or no visitors appear. Likely causes and fixes:- Page rules are too narrow. If an inclusion list is active, identification runs only on those pages. Widen the list or switch page rules off. See Managing websites.
- Capture flags are off. Confirm the signals you expect are enabled for the website.
- Filters are hiding matches. B2C, own-domain, and suppression filters remove visitors from view. Review them. See Filters.
- An ICP is scoped tightly. If you are viewing through an ICP, the list reflects only matching companies. See ICP filtering.
- Traffic is genuinely anonymous. Not every visit can be de-anonymized, so low-traffic sites naturally see fewer matches.
Slack alerts not arriving
Visitors appear in the dashboard, but Slack does not notify. Likely causes and fixes:- The Slack connection is for a different website. Routes are per website. Confirm the route exists on the site you expect.
- The route’s filter excludes the matches. If the route is scoped to an ICP or filter, only matching visitors trigger it.
- The Slack authorization was revoked. Reconnect Slack and re-select the channel.
An integration stopped syncing
A connector that worked has stopped. Likely causes and fixes:- The integration’s credentials expired or were revoked. Reconnect it from its settings.
- For Webhooks, confirm the endpoint is reachable and returns a success status. Repeated failures can stop delivery.
- For HubSpot, confirm the connected account still has access and the required scopes.
- An API token was revoked. A revoked token stops working immediately; create a new one. See API tokens.
Still stuck? Contact support@asksquid.ai with the website name and what you have already checked.