Skip to content

Commit f3655ef

Browse files
committed
add launchdarkly actions note
1 parent 1a052f6 commit f3655ef

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

src/_includes/components/actions-fields.html

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -115,6 +115,19 @@
115115
<p>{{action.description | markdownify}}</p>
116116
<p>{{action.name}} is a <strong>{{action.platform | capitalize}}</strong> action. {% if action.defaultTrigger %}The default Trigger is: <code>{{action.defaultTrigger}}</code> {%endif%}</p>
117117

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+
<div class="premonition info">
122+
<div class="fa fa-check-circle"></div>
123+
<div class="content">
124+
<p class="header">Segment automatically maps Audience ID and Audience Key fields</p>
125+
<p markdown=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 %}
118131

119132
{% if action.fields.size > 0 %}
120133
<p class="button button-hollow" data-toggle="collapse" data-target=".settings-content-{{action.slug}}">Click to show / hide fields</p>

0 commit comments

Comments
 (0)