General
Project information
Changes only save when you click Save Changes in the bar that appears once the form is dirty.
Organizations on partner billing also get an Active purchase order field here. Its value is
stamped onto future token purchases for this project and appears on its statement; historical
purchases keep their original PO.
Analysis
See Entity Types for what each type covers and how to write instructions.
Deleting a project
Under Irreversible Actions → Danger Zone. You must type the project name to confirm.Recurrence Settings
Settings → Recurrence Settings holds the project’s automatic runs. A project can carry several named schedules, each with its own interval, models and set of queries.Recurrence is no longer a card on the General page. It is its own page, and one project can hold
many schedules instead of a single one.
Intervals
Schedules run in UTC. There is no timezone picker. The preview spells the schedule out in plain
English, states the UTC hour with your local time beside it, and lists the next five run dates.
Assigning queries
A schedule runs only the queries linked to it. Use Assign queries on the setting card. Queries linked to no schedule run on demand only, and a banner at the top of the page counts them. The Recurrence column on the queries table names the schedule each query belongs to. Every card carries an Active or Paused badge with a Pause / Resume button, plus its models, iterations, query count and next run. Pausing does not affect existing results.Choosing models
Each model card shows a Scraping or API chip, and a Web search chip where the model searches the web. Turn on Specific versions to pick a pinned version instead of the rolling model. Availability varies by country, see Models Availability.A saved model that is no longer offered stays in the grid with a Deprecated badge until you
deselect it. Results it already produced are untouched.
Entities
Settings → Entities manages every tracked brand, its aliases, domains and flags. See Competitors & Brands for the full picture. The page also holds Entity Groups, where you create the two-level structure:- A Group is top-level.
- A Division nests under a group, or stands alone.
Domain Categories
Shared → Domain Categories lists every domain cited across your project with the category it resolved to — “the system categorizes domains automatically. Pick a category to override it. Your override always wins.” Filter by category, or by Set by (Manual override / Automatic) to audit what you’ve changed. Clearing an override reverts the domain to its automatic category. These categories drive the Source type distribution chart on the Sources page.Queries
Analysis settings → Queries → All queries is full CRUD over your queries, with CSV import, bulk tag operations, and the Launch analysis button. Queries → Tags manages query tag definitions and their groups. Two things to know about Launch analysis:- Select rows first and the button reads Launch partial analysis (N queries). It asks you to tick a box acknowledging that running a subset can put those queries out of sync with the rest.
- If the project already launched a job in the last 10 minutes you get a Recent job detected confirmation, because a second run would duplicate results. Choose Launch anyway to proceed.
Response Tagging
Two pages:- All responses — browse raw AI responses and tag them, individually or in bulk.
- Tags — create and manage the response tag definitions, each with a Matching mode of Exact or Semantic, plus their Response Tag Groups.
Shopping Settings
- Products — your canonical product catalog. Select two or more products of the same brand and merge them to fix duplicates.
- Shopping Products — the raw per-appearance rows, where you map anything marked Unknown or Not matched to the right entity and product.
Jobs
Jobs tracks every execution run. Columns: ID, Created At, Created By (a person, or “Recurring Job” for scheduled runs), Status, Total, Success, Pending and Failed.
Expand a row for its individual executions, filterable by status, with per-step badges.
Recurrences History
A read-only log of past scheduled executions. Columns: Recurring Execution ID, Recurrence Setting (which schedule fired), Status, Date and Next Execution. Expand a row to see the error message when one failed.Members, Recurrence Settings, Jobs and Recurrences History are only visible to
project Managers and Editors. Viewers are redirected back to General.
Members
Project-level access, with three roles — Manager, Editor and Viewer. Pending invitations are listed below the member table and can be cancelled.Only a project Manager can invite, remove or change roles. Editors can open the page but not
act on it. See Organization & Billing.
Export data
Advanced → Export data is the only settings page that keeps the global filter bar — your current filters and date range are applied to the export. Pick exactly one of seven export types:
Two exports have a switch:
- Full Run Data → Include full response text adds a
response_textcolumn and can grow the file substantially. - Entities → Include merged entities adds the entities merged into another one, with
merged_into_idnaming the target.
Download links expire after 7 days. Output is always CSV.