signup_completed, purchase_made, level_finished. You don’t build them from scratch in the Context Builder. You create them by syncing raw events from the Event Catalog, and then refine them in the Builder.
How Events Are Created
1
Approve the raw event in the Event Catalog
Give the raw event a description, and approve its parameters and user properties. The Missing Description Wizard speeds this up.
2
Sync it
Select one or more raw events and choose Sync to context layer. See Syncing Events to the Semantic Catalog for the full walkthrough.
3
Deploy
The new events and their parameters are created on your branch. Test them, then deploy to make them live for everyone.
What Gets Created
A raw event whose description is still pending becomes a Pending event. The agent can use it straight away, and answers that rely on it are flagged until someone approves it.
Keeping Events Up to Date
Once an event is in the Semantic Catalog, new parameters join it as you approve them in the Event Catalog — you don’t need to sync the raw event again. Descriptions stay linked in both directions: change one in the Event Catalog or the Semantic Catalog, and the other follows.Common Parameters
A parameter that belongs to two or more events — such ascountry, platform, or user_id — is a common parameter. It’s a single item shared by all its events, so changing it once changes it everywhere. Common parameters have their own Common Parameters tab in the Semantic Catalog.
A parameter that belongs to only one event is specific to that event.
Changing Events and Parameters
After an event exists, change it in the Context Builder like any other component:/event— Update descriptions (one at a time or in batch), add rules, and delete events or parameters./parameter— Build and fix parameters, and add rules to them.
Custom Parameters
When a value is worked out from the event’s own row — aCASE or an IF over its columns, or a cleaned-up version of an existing value — add it as a custom parameter with /parameter.
A custom parameter can only use the event’s own row. If the value has to be looked up in another table, keep the key the event already carries and add a rule to it explaining which table to look it up in.