Custom Attributes
Tag users with text and counter values as they move through a real-time journey.
Custom attributes let you tag each user with named values as they pass through journey nodes. In real-time journeys, attributes are available immediately to downstream nodes in the same event routing.
Supported attribute types
Real-time journeys support text and counter custom attributes. Related-dataset custom attributes and attribute formulas remain batch-only. Related-dataset fields can still be fetched through real-time warehouse enrichment when a node needs them.
| Type | Real-time journeys | Batch journeys |
|---|---|---|
| Static text | Yes | Yes |
| Counter | Yes | No |
| Attribute formula (SQL) | No | Yes |
| Related dataset custom attribute | No — batch-only | Yes |
For formulas and batch-only configuration, see Custom Attributes for Journeys.
Counters
Counters are integer attributes that track a value for each user while the user moves through a real-time journey. Choose one operation for each counter update:
- Set replaces the current value with the specified amount.
- Increment adds the specified amount to the current value.
- Decrement subtracts the specified amount from the current value.
Counters can be referenced by downstream criteria and destination fields. They are runtime-only: GrowthLoop keeps their state in the real-time journey runtime and does not create glca_* columns or write counter values to the warehouse journey-state rows.
Where to set custom attributes
Add custom attributes in the Settings tab on:
- Entry node
- Criteria node (separate values depending on which sub-criteria matches)
- Destination node
- Experiment variation node (separate values depending on which variation the message is assigned to)
- Trigger node (via response fields)
Waterfall behavior
Custom attribute values set at one node are available at all downstream nodes in the same message path — the same waterfall behavior as batch journeys. A criteria node can filter on attributes set by an upstream node, and downstream destinations and trigger templates can reference these labels. Attributes set on the current criteria node are applied after that node evaluates its conditions.
Using attributes downstream
Custom attributes can be selected in destination nodes as match fields or additional fields. Map them to template fields for email, SMS, or in-app destinations. Text and counter values are inserted into the template before the event is triggered in real time.
Related-dataset custom attributes are batch-only in real-time journeys. Using one creates a batch boundary, so the node and its downstream nodes process within minutes rather than in the real-time path. This is separate from fetching a related-dataset field through real-time warehouse enrichment.
Related guides
- Trigger node — response fields
- Criteria node
- Destination node
- Custom Attributes for Journeys — batch journey attributes and formulas
Updated 19 days ago