You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although trait fields are not frequently used in event rules, the StackAdapt destination forwards them and they can be used if desired.
112
+
113
+
| Segment Trait Property | StackAdapt Event Key |
114
+
|------------------------|----------------------|
115
+
|`traits.email`|`email`|
116
+
|`traits.first_name`|`first_name`|
117
+
|`traits.last_name`|`last_name`|
118
+
|`traits.phone`|`phone`|
119
+
120
+
For example, to create a conversion event when a user with the domain `example.com` completes an order, you could set up an event rule matching an `action` value of `Order Completed` and an `email` containing `@example.com` as shown below:
121
+
122
+

123
+
124
+
This rule would match a Segment event fired with code such as:
If you are using URL rules, these will be matched whenever Segment sends an event to StackAdapt with a `url` matching the URL rule. This should be accomplished by the page event Segment automatically fires when a page is viewed, so setup of URL rules should be identical to setting up URL rules with the StackAdapt pixel.
0 commit comments