Presets
A preset bundles everything a project needs to measure leads well: events and goals (form, booking, WhatsApp, phone, quiz, calculator, video, buttons), the relevance rules, conversion definitions with values, the lead value and the consent defaults.
Built-in templates
Read-only starting points, generic and free of customer content:
| Key | For |
|---|---|
default | Any site: form, buttons, call, WhatsApp, appointment |
clinic | Clinics and aesthetics: appointment request, quiz, price calculator, WhatsApp |
real-estate | Real estate: exposé, viewing, search profile, financing calculator |
b2b-services | B2B services: first call with questionnaire, whitepaper, pricing page |
coaching-high-ticket | Coaching and high-ticket offers: application, video to the end, calendar |
ecommerce-lead | E-commerce with quotes: quote with questionnaire, cart, advice |
presets_list also returns each template's highlights and current version.
Your own presets
Each organization can keep its own presets – private to that organization, versioned, never visible to others.
| Action | API | MCP |
|---|---|---|
| List (built-in + own) | GET /v1/orgs/{org}/presets | presets_list |
| Read | GET /v1/orgs/{org}/presets/{preset} | presets_get |
| Create | POST /v1/orgs/{org}/presets | presets_create |
| Edit (new version) | PATCH /v1/orgs/{org}/presets/{preset} | presets_update |
| Duplicate | POST /v1/orgs/{org}/presets/{preset}/duplicate | presets_duplicate |
| Archive / restore | POST …/{preset}/archive, …/unarchive | presets_archive |
| Preview interest weights on real visits | POST /v1/orgs/{org}/presets/preview-relevance | – |
| Apply to a project | POST /v1/projects/{project}/preset/apply | presets_apply |
Reading needs analytics:read in the organization, writing config:write, applying project:admin
on the project. Every change is audited.
Create from one of four starting points:
{ "from": { "kind": "template", "id": "clinic" }, "key": "our-clinics", "name": { "de": "Unsere Kliniken", "en": "Our clinics" } }kind is blank, template (a built-in key), project (copy the setup of an existing project) or
definition (a full preset definition). patch applies changes on top.
Edit sends the version it is based on; when someone saved in between the answer is
409 preset_conflict. Archived presets cannot be applied
(preset_archived).
Apply with a diff first
{ "presetId": "our-clinics", "dryRun": true }dryRun defaults to true and returns the differences per section (added, changed, removed) –
defaults, page groups, CTAs, privacy and tracking options, settings, relevance model, questionnaires, goals,
funnels, conversion definitions, event schemas – without changing anything. Send "dryRun": false
to apply atomically; version pins an older preset version. Applying replaces goals, funnels,
conversion definitions, the relevance model and tracking options with the preset's: goals missing
from the preset are archived, funnels deleted and definitions disabled; questionnaires and event
schemas are never removed. With
"recompute": "30d" or "90d" X3 recalculates relevance scores for that period afterwards;
the default none only affects new data. Existing projects keep their preset until you apply another.
In the dashboard
Team → Templates opens a wizard instead of a form: starting point, industry and goal, events and goals (pick elements on your site), relevance rules with a live preview on real visits, conversions, consent defaults, summary – then apply to projects with the diff.
Let Claude build one
The MCP prompt preset_from_website (arguments url, optional org and template) starts from the
best-fitting template, reads the site – forms, quizzes and calculators, booking widgets, WhatsApp, phone
and e-mail links, videos – and proposes a preset as a diff. Nothing is saved before you confirm; then
presets_create stores it and presets_apply (dry run first) puts it on a project.