Skip to content

Add launchdarkly actions note #6796

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions src/_includes/components/actions-fields.html
Original file line number Diff line number Diff line change
Expand Up @@ -115,6 +115,19 @@
<p>{{action.description | markdownify}}</p>
<p>{{action.name}} is a <strong>{{action.platform | capitalize}}</strong> action. {% if action.defaultTrigger %}The default Trigger is: <code>{{action.defaultTrigger}}</code> {%endif%}</p>

<!--- 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 -->

{% if action.id == 'aPAULh8sgt5bcTeXJuXTB6' %}
<div class="premonition info">
<div class="fa fa-check-circle"></div>
<div class="content">
<p class="header">Segment automatically maps Audience ID and Audience Key fields</p>
<p markdown=1>
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`.
</p>
</div>
</div>
{% endif %}

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