From b53c876bbfd9a629985246dac1f5abe0c986f476 Mon Sep 17 00:00:00 2001 From: Liz Kane <68755692+lizkane222@users.noreply.github.com> Date: Fri, 30 May 2025 14:09:40 -0700 Subject: [PATCH 1/3] Update track.md Customers were confused on why context.traits in Track events were not updating user traits within Unify. Added clarification warning --- src/connections/spec/track.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/connections/spec/track.md b/src/connections/spec/track.md index 644d062c6a..0d58d2a98a 100644 --- a/src/connections/spec/track.md +++ b/src/connections/spec/track.md @@ -121,6 +121,10 @@ _For instructions on how to pass fields to the context object for a specific lib Segment's Actions destinations allows your team to build individual actions that are triggered based on a set of configured conditions. By adding the user's latest traits to the Track event's `context.traits` object, its possible to build two separate Actions to be triggered by this single event. For example, if your team would like to send an Identify event anytime the specific Track event "Button Clicked" is triggered, simply add the available traits into the Track event's payload, then build a destination Actions for the Track event : `Event Name is Button Clicked`, and a destination Action for the Identify event : `All of the following conditions are true: Event Name is Button Clicked, Event Context traits exists`, and then both Actions will have access to reference the `context.traits` fields within its mappings. +> warning "" +> Sending traits in Track or Page events via the context.traits object will not update traits on profiles within Unify. Only traits sent within an Identify call will apply to user profiles within the Unify Space. +> The instructions above are only relevant in sending additional user data through Actions Destinations and not to Unify Spaces. + For more information on the context object, please see the [Spec: Common Fields](https://segment.com/docs/connections/spec/common/#context) documentation. From f9538e04b334ec3c3b7bfef586065a3af67de687 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Fri, 20 Jun 2025 16:14:29 -0500 Subject: [PATCH 2/3] minor rewording --- src/connections/spec/track.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/connections/spec/track.md b/src/connections/spec/track.md index 0d58d2a98a..db17a47c6b 100644 --- a/src/connections/spec/track.md +++ b/src/connections/spec/track.md @@ -121,9 +121,8 @@ _For instructions on how to pass fields to the context object for a specific lib Segment's Actions destinations allows your team to build individual actions that are triggered based on a set of configured conditions. By adding the user's latest traits to the Track event's `context.traits` object, its possible to build two separate Actions to be triggered by this single event. For example, if your team would like to send an Identify event anytime the specific Track event "Button Clicked" is triggered, simply add the available traits into the Track event's payload, then build a destination Actions for the Track event : `Event Name is Button Clicked`, and a destination Action for the Identify event : `All of the following conditions are true: Event Name is Button Clicked, Event Context traits exists`, and then both Actions will have access to reference the `context.traits` fields within its mappings. -> warning "" -> Sending traits in Track or Page events via the context.traits object will not update traits on profiles within Unify. Only traits sent within an Identify call will apply to user profiles within the Unify Space. -> The instructions above are only relevant in sending additional user data through Actions Destinations and not to Unify Spaces. +> warning "Unify profiles require Identify calls" +> Adding user traits to a Track or Page call using `context.traits` lets you send that data to Actions destinations, but it won’t update the user's profile in Unify. To update traits in Unify, use an Identify call instead. For more information on the context object, please see the [Spec: Common Fields](https://segment.com/docs/connections/spec/common/#context) documentation. From 400111cd6c039a1a7e0456bce36812be46a1e856 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Fri, 20 Jun 2025 16:14:54 -0500 Subject: [PATCH 3/3] change to info --- src/connections/spec/track.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/spec/track.md b/src/connections/spec/track.md index db17a47c6b..5594b26bff 100644 --- a/src/connections/spec/track.md +++ b/src/connections/spec/track.md @@ -121,7 +121,7 @@ _For instructions on how to pass fields to the context object for a specific lib Segment's Actions destinations allows your team to build individual actions that are triggered based on a set of configured conditions. By adding the user's latest traits to the Track event's `context.traits` object, its possible to build two separate Actions to be triggered by this single event. For example, if your team would like to send an Identify event anytime the specific Track event "Button Clicked" is triggered, simply add the available traits into the Track event's payload, then build a destination Actions for the Track event : `Event Name is Button Clicked`, and a destination Action for the Identify event : `All of the following conditions are true: Event Name is Button Clicked, Event Context traits exists`, and then both Actions will have access to reference the `context.traits` fields within its mappings. -> warning "Unify profiles require Identify calls" +> info "Unify profiles require Identify calls" > Adding user traits to a Track or Page call using `context.traits` lets you send that data to Actions destinations, but it won’t update the user's profile in Unify. To update traits in Unify, use an Identify call instead. For more information on the context object, please see the [Spec: Common Fields](https://segment.com/docs/connections/spec/common/#context) documentation.