Skip to main content
Project settings open from the Settings entry in the project sidebar. The pages are grouped into Settings, Shared, Analysis settings, Shopping Settings and Advanced.

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.
Deletion is irreversible and removes all queries, results and analysis data. Export first if you need to keep anything. Only organization Administrators can delete a project.

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.
Click Create setting to add 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.
Scheduling is hour-granular, so picking a time forces the minutes to zero. Leave Starting On empty on an Every N days schedule and the days it lands on are chosen for you.
There is no “Manual” setting. Manual is the absence of one: a project with no active schedule runs only when you press Launch analysis.

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.
New projects start with their schedule paused, whatever interval you picked in the wizard. Nothing runs automatically until you resume it.
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.
AI responses vary from run to run. Three iterations is the practical floor for a stable reading. The Launch analysis dialog defaults to 7, a good balance of cost and reliability.

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.
Deleting a container never deletes its entities: a division’s entities move up to its parent group (or become ungrouped), and a group’s divisions become standalone. Both entities and groups support CSV import from this page.

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.
See Queries & Tags.

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.
See Shopping.

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_text column and can grow the file substantially.
  • Entities → Include merged entities adds the entities merged into another one, with merged_into_id naming the target.
Exports run in the background. You receive an email with download links when they are ready, and the page lists your three most recent exports with their status. A failed export states why on the page.
Download links expire after 7 days. Output is always CSV.
Each file is capped at 1,048,575 rows (Excel’s limit) and 5 GB. An export over either cap fails with a message rather than producing a partial file. Narrow the date range or add filters and run it again.