Skip to content

Commit 52cc683

Browse files
committed
cleanup
1 parent 151fbd8 commit 52cc683

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

src/engage/journeys/event-triggered-journeys-steps.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -156,4 +156,19 @@ To edit or delete an activation, click the destination name in the journey canva
156156

157157
#### Deleting activations
158158

159-
If you delete an activation, future instances of the journey step will fail to send data to that destination. To avoid disruptions, make sure you've configured alternative logic or destintions before removing an activation.
159+
If you delete an activation, future instances of the journey step will fail to send data to that destination. To avoid disruptions, make sure you've configured alternative logic or destintions before removing an activation.
160+
161+
### Handling missing attributes
162+
163+
There may be cases where events sent to Segment are missing specific properties or when profile traits are unavailable. How Segment handles these scenarios depends on whether the attribute is explicitly mapped.
164+
165+
#### If values are not mapped
166+
167+
- When an event property is configured but it's not present in the incoming Track event, that property gets excluded from the payload sent to the destination.
168+
- Similarly, if a trait is configured but isn't present on the profile, the trait gets excluded from the payload.
169+
170+
#### If values are mapped
171+
- If an event property is mapped but is missing in the Track event, Segment still includes the mapped key in the payload but with a value of `undefined`.
172+
- Similarly, if a mapped trait is missing on the profile, the key is included in the payload with a value of `undefined`.
173+
174+
Carefully configuring mappings and handling missing attributes can help you maintain data integrity and avoid errors in downstream systems.

0 commit comments

Comments
 (0)