Skip to main content
Syncing turns a raw event in the Event Catalog into an event in the Semantic Catalog — the modeled version the agent actually uses. After sync, the agent reaches for the event by name in metrics, segments, and ad-hoc questions, without you having to point at the raw event in your warehouse. You sync a raw event when it’s ready — typically after you’ve described it and approved its parameters and user properties in the Event Catalog.

What Gets Created

Each synced raw event creates the following: Descriptions carry over, and the approver is recorded on the new components.

Running a Sync

1

Check the raw event's description

A raw event with an approved description becomes an Approved event. One that still has only a suggested description can be synced too — it becomes a Pending event, which the agent can use right away.
2

Select raw events

From the Events tab (or a raw event’s page), select one or more raw events and choose Sync to context layer.
3

Confirm

If you don’t have a branch yet, ClarityQ asks you to start one first. A dialog then shows how many raw events you selected and how many will be created as Pending. Click Sync.
4

Deploy

ClarityQ reports how many raw events were synced to your branch, how many were skipped because they already have an event, and any that failed with the reason. The new events go live for everyone when you deploy your branch.

What Status the Event Gets

You don’t choose the status at sync time — it follows the raw event’s description: A Pending event is usable immediately. The agent can answer with it, and any answer that does is flagged in context coverage and listed in the Inbox until someone approves it. Syncing early costs you nothing, and the Inbox tells you what still needs a look.

After the Sync

Once a raw event has an event in the Semantic Catalog, the two stay linked:
  • New parameters join the event as you approve them in the Event Catalog — you don’t need to sync again.
  • Descriptions stay the same on both sides. Change one and the other follows.
Everything else about the event — its rules, custom parameters, and deletions — you change in the Context Builder with /event and /parameter. See Building Events from the Event Catalog.

Notes

Syncing a raw event that already has an event skips it — the existing event is kept. To sync it again, for example after restructuring its parameters, delete the event first, then sync the raw event.
When you deploy a branch that deletes events or parameters, ClarityQ can also hide them in the Event Catalog, so they don’t reappear the next time your tracking is synced.