Troubleshooting

The most common problems users report — in a "symptom → what to check" layout.

Checks and results

A check doesn't start, or ends with a budget message. Check the Cost Center: the monthly budget may be exhausted, or the daily safety valve kicked in after an unusual usage spike. Raise the budget or wait until the end of the day/month.

I can't add a question to a map / create a new map. You've hit a package limit (maps per workspace or questions per map) — see Limits.

My brand isn't mentioned even though it "should be". That's not a measurement bug — it's usually the real state of AI answers (and exactly why monitoring exists). Check the question ranking and AI Sources to see who AI cites instead of you.

Integrations

Bot Analytics shows no data. The module requires a site behind Cloudflare plus a Zone ID + API token in the company profile. Import runs hourly — first data appears within an hour of configuration. See AI Bot Analytics.

The product catalog doesn't sync with my shop. Check the shop integration credentials in the company profile (the API key may have expired or changed permissions). Alternatively, connect a product feed.

Publishing to WordPress / Webflow fails. Verify the connection details in the company profile (WP application password / Webflow token and collection). After changing your WordPress password, the application password must be regenerated.

The attribution pixel isn't collecting data. Make sure the tag is installed on the whole site (not just the homepage) and that a consent manager isn't blocking it. Distribution shows a warning when the pixel isn't detected.

E-mails and notifications

I'm not receiving alerts / e-mail reports. In order: (1) check the settings in the user menu → Notifications (per-user opt-in), (2) the spam folder, (3) whether your company mail server blocks the sender. See Notifications.

Export and API

The export doesn't include a dataset I need. Datasets are gated by package (e.g. orders require the attribution module) — see Data export.

The API returns 401 / 403. Check the X-API-Key header (keys are created in the API Keys section), whether the key has been revoked, and whether it has the required scope (e.g. orders:write for order ingest).

The API returns 429. The key's per-minute request limit was exceeded — slow down or spread out the calls.

Still not working?

Write to us with a description of the problem, the workspace name and the approximate time it occurred — it speeds up diagnosis on our side.