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
Copy file name to clipboardExpand all lines: src/_includes/components/actions-fields.html
+13Lines changed: 13 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -115,6 +115,19 @@
115
115
<p>{{action.description | markdownify}}</p>
116
116
<p>{{action.name}} is a <strong>{{action.platform | capitalize}}</strong> action. {% if action.defaultTrigger %}The default Trigger is: <code>{{action.defaultTrigger}}</code> {%endif%}</p>
117
117
118
+
<!--- IG 7/2024 - CSE requested this note, as customers were confused about why some required fields didn't appear in the in-app LaunchDarkly Audiences mappings -->
119
+
120
+
{% if action.id == 'aPAULh8sgt5bcTeXJuXTB6' %}
121
+
<divclass="premonition info">
122
+
<divclass="fa fa-check-circle"></div>
123
+
<divclass="content">
124
+
<pclass="header">Segment automatically maps Audience ID and Audience Key fields</p>
125
+
<pmarkdown=1>
126
+
Segment hides these two fields from the UI to avoid user error, as these fields remain static in Engage. Audience ID defaults to `property : context.personas.computation_id` and Audience Key defaults to `property : context.personas.computation_key`.
127
+
</p>
128
+
</div>
129
+
</div>
130
+
{% endif %}
118
131
119
132
{% if action.fields.size > 0 %}
120
133
<pclass="button button-hollow" data-toggle="collapse" data-target=".settings-content-{{action.slug}}">Click to show / hide fields</p>
0 commit comments