Set Data node reference
Use Set Data to adjust scores, save variables, assign segments, or update your email platform. See each action's settings and limits before you use it.
A Set Data node lets you save or change data at a particular point in your flow. It runs one or more actions when a visitor reaches it, without displaying a question or waiting for a response.
When to use it
Use Set Data when a later step needs a score, variable, or segment, or when you want to update a known contact in your email platform.
For example, WorkForge (opens in a new tab) could add 2 to a planning score and save last_topic as planning for seven days. A later message could read {{ variable.last_topic }}. A High Score node could compare planning with a separately assigned collaboration score.
Settings
Action rows
Each row has an Action Type. Choose the type, then fill in the fields below it. Rows run in the order you see them.
A new node starts with Update Score, a blank score name, and an adjustment of 1. Add another action adds another score row with an adjustment of 1. Remove controls appear when there's more than one row. In system flows, items such as Set Variable create the same kind of node with that action already selected.
Changing an action's type clears fields that don't belong to the new type. Switching between Add Tag and Remove Tag keeps the selected tag because both use the same field.
Update Score
Modify score accepts an existing score name or a new name. Positive numbers add points and negative numbers subtract them. The number is an adjustment, not a replacement total.
Scores can also come from question answers. Put the score action before the High Score node or condition that reads it.
Only the first score adjustment in a Set Data node is retained, even if you add several Update Score rows. Use a separate Set Data node for each score adjustment, then check each total before publishing.
Add / Update Variable
| Setting | What it does |
|---|---|
| Variable Name: | Names the variable so you can read it later. |
| Variable Value: | Sets a literal or Liquid-rendered value. A blank value removes the stored value. |
| Add Data | Inserts available flow data into a value field that supports Liquid. |
| Expires: | Defaults to Never. Choose In... to set a duration. This field appears when the value isn't blank. |
| Duration | Accepts a positive number of Minutes, Hours, Days, or Weeks. Unset duration fields start at 1 hour. |
Variables stay in the visitor's browser until they expire, you remove them, or browser storage is lost. RightMessage excludes expired variables when reading data. Assigning a variable again resets both its value and expiration. See store and expire variables.
Set Segment
Choose a group under Question / Segment Group:, then choose its segment under Set To Segment:. Both selectors can be cleared, and you can search the group selector. The everyone segment isn't available to assign. Changing the group clears the previously selected segment.
Setting a segment records an answer for that group, clears its other selected segments, and refreshes segmentation. If answer synchronization is active, it also triggers that synchronization.
For a multiple-answer group, this replaces the previous selections. It doesn't add another answer. For example, setting a WorkForge visitor's interest to Planning can change what later Routers and campaigns show them. If you only want to remember which recommendation they saw, use a separate variable instead.
Set Custom Field
This action appears when you've connected an email platform. Choose the destination field and enter a Value:. The value supports Liquid and Add Data when data is available.
RightMessage needs an identity the provider can update. Check the destination contact record during testing to confirm the field was saved.
Add Tag and Remove Tag
These actions appear only when your connected provider supports them. The selector loads the provider's tags or lists, and you can search or clear it. Depending on the provider, labels can say Tag or List.
A loading indicator isn't a destination you can select. An empty list also doesn't necessarily mean the provider has no tags.
For an unidentified visitor, supported tag actions can queue an addition or removal until they're identified. The provider hasn't been updated while the action is queued. Test both an already identified contact and an anonymous visitor who later submits a form.
Tag actions don't collect consent or complete the provider's subscription process.
How visitors move through it
After running its actions, Set Data continues through the flow. Updates to an email platform can happen asynchronously, so reaching a later message doesn't confirm that the provider accepted them.
A terminal form doesn't run ordinary Set Data nodes placed below it after submission. Configure its submission through form actions instead.
Things to know
Deleting an action row stops it from running in the future. It doesn't remove a value already saved in a visitor's browser or contact record.
If your node has several variable or field rows, check which value received an Add Data expression before you close the editor. The expression can go into the wrong row.
Check each action separately. A saved variable doesn't tell you whether a score changed or a provider field updated. Verify an integration change explains how to check the destination data.