> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-components/action/fire-event.md).
# Fire event
Record an event with attributes at a journey step, using fixed values or values from the journey context.
An event records something that happened. Event attributes add details about that occurrence. For example, a `View Product` event can include the product name, category, and price.
Use **Fire Event** to record an event when a user reaches a journey step. Define the event and its attributes using fixed values or values from the journey context.
### Step 1: Add the action
1. In **Journey Builder**, select **Add Step**.
2. Under **Action**, select **Fire Event**.
3. Enter a **Step Name**.
Use a name that identifies the recorded event, such as `Record product view`. The name appears only in the journey builder.
### Step 2: Select the event
Select the event in **Select Event**.
Choose the event that represents the action or outcome you want to record. The event name identifies the occurrence. Its attributes describe it.
For example, select `View Product` to record that event when a user reaches this step.
### Step 3: Configure an event attribute
1. Select an event attribute in **Select Attribute**.
2. Select a value type.
3. Enter or select the **Value**.
Select an attribute only when its value is available or can be set. Each configured attribute becomes part of the event when the journey runs.
Use **Select Attribute** to choose the detail that belongs to the event. For a product-view event, this can include the product name, category, or price.
Value type
Effect
Variable
Uses a journey variable.
Fixed
Uses a value you define.
For example, select `Product Name`, choose **Variable**, and select `ProductName`. The recorded event receives the product name available in the journey context.
Choose **Fixed** for a value that is always the same. Choose **Variable** when the journey or user profile provides the value.
For example, set a Fixed `Category` value to `Electronics` when this journey only handles that category. Use a Variable `Product Name` when each user views a different product.
### Step 4: Add more attributes
Select **Add More** to attach another attribute to the event. Repeat Step 3 for each attribute.
For example, add `Category` and `Price` alongside `Product Name`. One event records all configured values.
Add only attributes that describe the selected event. This keeps the event data meaningful when you use it for analysis or a later follow-up.
### Step 5: Save the action
Select **Save**.
The event triggers as users reach this step.
For example, a `Purchase` event can include the product category and price. Reporting and follow-up journeys can then use the recorded event data.
{% hint style="info" %}
Use **Update Profile** when you need to change a user profile field. Use **Fire Event** when you need to record an interaction or outcome.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-components/action/fire-event.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
