> 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/update-profile.md).

# Update profile

Update or remove profile attributes at a journey step with fixed values or values from the journey context.

Use **Update Profile** to change or remove profile attributes when a user reaches this journey step. You can update one or more attributes, using fixed values or values from the journey context.

A profile attribute is information stored for one user. Examples include a user status, preferred category, or most recent conversion date. Use this action when later journeys or messages need the updated value.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2Fce5PbEBr4qLUX7wtqyS8%2FEkran%20Resmi%202026-09-28%2013.28.16.png?alt=media&amp;token=55c6dfcc-65a4-407b-a450-b2ca500568f9" alt="" width="563"><figcaption></figcaption></figure>

### Step 1: Add the action

1. In **Journey Builder**, select **Add Step**.
2. Under **Action**, select **Update Profile**.
3. Enter a **Step Name**.

Use a name that describes the result. For example, enter `Mark user as converted`. The name helps you identify this action in the journey flow. Users never see it.

### Step 2: Configure an attribute

1. Select an attribute in **Select Attribute**.
2. Select **Update** or **Delete** in **Action**.
3. For **Update**, select a **Value Type** and enter a **Value**.

Select the attribute before choosing its value. **Update** needs a new value. **Delete** removes the attribute and does not need a value.

**Select Attribute** lists the profile fields available for users. Select the exact field you want later steps, campaigns, or reports to use.

<table><thead><tr><th width="138.12890625">Setting</th><th>Effect</th></tr></thead><tbody><tr><td><strong>Update</strong></td><td>Sets the selected profile attribute to the configured value.</td></tr><tr><td><strong>Delete</strong></td><td>Removes the selected attribute from the user's profile.</td></tr><tr><td><strong>Constant</strong></td><td>Uses the same value for every user.</td></tr><tr><td><strong>Variable</strong></td><td>Uses a value from the journey or user profile.</td></tr></tbody></table>

For example, select **Update**, choose `User Status`, and set a Constant value of `Converted`. Every user reaching this step receives that profile value.

Choose **Constant** when every user should receive the same value. Choose **Variable** when the value differs for each user.

For example, choose **Variable** for `Most Recent Conversion Date` when each user reaches the step on a different date. Choose **Constant** for `User Status` when every user should receive `Converted`.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FfTx3Y2Of9L20x5XdZydh%2FEkran%20Resmi%202026-09-28%2013.27.51.png?alt=media&amp;token=36d8d6bd-ac43-4591-88d8-e908e27a2211" alt=""><figcaption></figcaption></figure>

### Step 3: Add more attributes

Select **Add More** to configure another attribute in the same step. Repeat Step 2 for each attribute.

Use one Update Profile action when the changes should happen together. Use separate actions when you need another journey step between the changes.

For example, update `User Status` to `Converted` and set `Most Recent Conversion Date` from a journey variable. Both changes run when the user reaches this step.

### Step 4: Save the action

Select **Save**.

The configured profile updates apply as users progress through the journey.

For example, a user can complete a purchase, receive `User Status = Converted`, and then enter a later branch based on that updated status.

Review every selected attribute before saving. A later row can update a different field, but it cannot recover a value removed with **Delete**.

{% hint style="info" %}
Use **Fire Event** when you need to record an event. Use **Update Profile** when you need to maintain a user attribute.
{% 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/update-profile.md?ask=<question>&goal=<user_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.