Update profile update-profile
Use the Update Profile action activity to update an existing ۶Ƶ Experience Platform profile with information from an event, a datasource, or a specific value. This action keeps profile data current and dynamically reflects user actions or incoming events within a journey.
Key concepts key-concepts
- The Update Profile action is available only in journeys that use a namespace. A namespace uniquely identifies records, ensuring updates apply to the correct profile.
- This action updates existing fields only and does not create new profile fields. For example, if the schema does not include a “Loyalty Status” field, the action cannot add it.
- The Update Profile action does not generate experience events, such as a “purchase event”. It modifies profile attributes exclusively.
- Define alternative paths for errors or timeouts, but avoid running two actions in parallel to ensure clear orchestration within the journey.
- Update requests sent to ۶Ƶ Experience Platform process immediately (within a second). However, processing time may vary. Actions relying on updated fields should account for potential delays. For example, if a downstream action reads “field 1” immediately after an update, the change may not yet be reflected.
- The Update Profile activity does not support XDM fields defined as enumerations or suggested values. Enumerations are predefined lists of values that cannot be modified using this activity.
- The Update Profile activity updates only the Profile Store, not the Data Lake. The Profile Store manages real-time customer profiles and is distinct from broader data storage in the Data Lake.
Dataset selection dataset-selection
The Update Profile activity requires a profile-enabled dataset to store updates. Since this activity updates only the Profile Store (not the Data Lake), ensure updates save to a dataset specifically designated for Update Profile actions. For example, if using a dataset named “Customer Engagement Profiles”, confirm it is profile-enabled and properly configured for this purpose.
Using datasets intended for batch or streaming ingestion may cause newly onboarded data to overwrite changes made by the Update Profile action, resulting in potential data conflicts.
Although the Update Profile activity does not require an identity namespace for configuration, the selected dataset must use the same Identity namespace as the event that launched the journey. This ensures updates map to the correct profile. For example, if the journey’s event uses the “Email” namespace, the dataset must also recognize “Email”. The identity map, if used, helps maintain accurate profile updates. Selecting a dataset with an incorrect namespace or without an identity map causes the Update Profile activity to fail.
Using the profile update using-the-profile-update
-
Design the journey by starting with an event. See this section. For example, use a “Web Form Submission” event.
-
In the Action section of the palette, drag and drop the Update Profile activity onto the canvas.
-
Select a schema from the list. For example, choose the “Retail Customer Schema” to update customer-related attributes.
-
Click Field to select the field to update. Only one field can be selected. For example, update the “Preferred Language” field to personalize future communications.
-
Select a dataset from the list.
note note NOTE The Update Profile action updates profile data in real time but does not update datasets. Dataset selection is required because the profile is a record related to a dataset. -
Click the Value field to define the value to use:
-
Use the simple expression editor to select a field from a data source or the incoming event. For example, map the event’s “Language Preference” field to the profile’s “Preferred Language” field.
-
For advanced functions or specific values, click Advanced mode. For example, set the “Loyalty Tier” field to “Gold” for high-value customers.
-
The Update Profile activity is now configured. This setup ensures the selected profile attribute updates in real time based on the event or data source.
Using the test mode using-the-test-mode
In test mode, the profile update is not simulated. The update applies to the test profile, allowing validation of the configuration before deploying the journey to live profiles.
Only test profiles can enter a journey in test mode. Create a new test profile or convert an existing profile into a test profile. In ۶Ƶ Experience Platform, update profile attributes via a CSV file or API calls. Alternatively, use an Update Profile action activity to change the test profile boolean field from false to true. For example, create a test profile with the “Is Test Profile” field set to true.
For more information on converting existing profiles into test profiles, see this section.