Skip to content

Commit 8714684

Browse files
chore: Update content to simplify serialization
1 parent 9bf0b4f commit 8714684

File tree

6 files changed

+9
-9
lines changed
  • src/connections/destinations/catalog

6 files changed

+9
-9
lines changed

src/connections/destinations/catalog/actions-linkedin-audiences/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ The setup is complete and the Audience will start syncing to LinkedIn. Segment a
4747

4848
To sync additional Audiences from your Engage space, create a separate mapping in the LinkedIn Audiences destination. Navigate to **Connections > Destinations**, search and select the LinkedIn Audiences destination, and follow Steps 9-11 above.
4949

50-
{% include components/actions-fields.html settings="true"%}
50+
{% include components/actions-fields.html settings="true" %}
5151

5252
## Linked Audiences
5353

src/connections/destinations/catalog/actions-liveramp-audiences/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ The LiveRamp Audiences destination can be connected to **Twilio Engage sources o
4444
> info "Mapping tester availability"
4545
> The Mapping Tester isn't available for this destination. Since this destination requires batched events for activation, testing can only be performed end-to-end with a connected source.
4646
47-
{% include components/actions-fields.html settings="false"%}
47+
{% include components/actions-fields.html settings="false" %}
4848

4949
## Limitations
5050

src/connections/destinations/catalog/actions-loops/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ id: 63360a5fe290ca3fdfad4a68
77

88
{% include content/plan-grid.md name="actions" %}
99

10-
[Loops](https://loops.so?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target:="_blank"} is a modern email platform for SaaS, a better way to send marketing and transactional email.
10+
[Loops](https://loops.so?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} is a modern email platform for SaaS, a better way to send marketing and transactional email.
1111

1212
You can use this Segment destination to create and update your Loops contacts and trigger email sending with events.
1313

@@ -66,4 +66,4 @@ Now you are able to send a test event. You can verify that the event was trigger
6666

6767
Read the tutorial for sending events [in the Loops docs](https://loops.so/docs/add-users/segment#send-event){:target="_blank"}.
6868

69-
{% include components/actions-fields.html %}
69+
{% include components/actions-fields.html %}

src/connections/destinations/catalog/actions-optimizely-feature-experimentation-cloud/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,4 +58,4 @@ Segment also handles the following mapping:
5858
## GDPR Support
5959
Segment supports deleting/suppressing users in Optimizely Feature Experimentation (Actions) using the [Segment app](/docs/privacy/user-deletion-and-suppression/). Before deleting/suppressing a user, create a [Personal Access Token](https://developers.optimizely.com/x/authentication/personal-token/){:target="_blank”} in Optimizely and provide it as the value of the Personal Access Token setting.
6060

61-
{% include components/actions-fields.html settings="true"%}
61+
{% include components/actions-fields.html settings="true" %}

src/connections/destinations/catalog/actions-pinterest-conversions-api/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ To connect the Pinterest Conversions API Destination:
4747
8. Follow the steps in [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
4848
9. Toggle **Enable Destination** on, then click **Save Changes**.
4949

50-
{% include components/actions-fields.html settings="true"%}
50+
{% include components/actions-fields.html settings="true" %}
5151

5252
> info "Setting conversion type"
5353
> By default, Segment sends all mappings as `web` conversions. To send events as mobile or offline conversions, set the Action Source in each mapping to `app_android`, `app_ios`, or `offline`.
@@ -156,4 +156,4 @@ Pinterest requires the `action_source` server event parameter for all events sen
156156
After you start sending events, you should start seeing them in dashboard. You can confirm that Pinterest received them by following these steps:
157157

158158
1. Go to **Events Overview** in Pinterest.
159-
2. Click **Event History** to see all the events Segment sent to Pinterest conversions.
159+
2. Click **Event History** to see all the events Segment sent to Pinterest conversions.

src/connections/destinations/catalog/actions-s3/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ To finish the setup, enable the AWS S3 (Actions) Destination in your workspace:
101101
* Enter the IAM External ID, which is a value set in the Trust Relationship under your AWS IAM Role.
102102
5. Enable the destination.
103103

104-
{% include components/actions-fields.html settings="true"%}
104+
{% include components/actions-fields.html settings="true" %}
105105

106106
### Step 3: Configure the AWS S3 (Actions) Destination mappings
107107
To finish the configuration, add mappings to your new AWS S3 (Actions) Destination:
@@ -111,4 +111,4 @@ To finish the configuration, add mappings to your new AWS S3 (Actions) Destinati
111111
3. Configure the Column Mappings. If you don't need any of the default columns, leave the value blank. You can also choose to add new mapping fields to set up customized columns as needed.
112112
4. Configure any additional settings as required.
113113
5. Enable the Mapping.
114-
6. Verify that Segment is sending data to your S3 bucket by navigating to `<your_S3_bucket>/` in the AWS console.
114+
6. Verify that Segment is sending data to your S3 bucket by navigating to `<your_S3_bucket>/` in the AWS console.

0 commit comments

Comments
 (0)