diff --git a/src/connections/destinations/catalog/actions-linkedin-audiences/index.md b/src/connections/destinations/catalog/actions-linkedin-audiences/index.md index ccef8864b2..5a860098ca 100644 --- a/src/connections/destinations/catalog/actions-linkedin-audiences/index.md +++ b/src/connections/destinations/catalog/actions-linkedin-audiences/index.md @@ -47,7 +47,7 @@ The setup is complete and the Audience will start syncing to LinkedIn. Segment a 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. -{% include components/actions-fields.html settings="true"%} +{% include components/actions-fields.html settings="true" %} ## Linked Audiences diff --git a/src/connections/destinations/catalog/actions-liveramp-audiences/index.md b/src/connections/destinations/catalog/actions-liveramp-audiences/index.md index 23690ca41b..a538d95cf1 100644 --- a/src/connections/destinations/catalog/actions-liveramp-audiences/index.md +++ b/src/connections/destinations/catalog/actions-liveramp-audiences/index.md @@ -44,7 +44,7 @@ The LiveRamp Audiences destination can be connected to **Twilio Engage sources o > info "Mapping tester availability" > 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. -{% include components/actions-fields.html settings="false"%} +{% include components/actions-fields.html settings="false" %} ## Limitations diff --git a/src/connections/destinations/catalog/actions-loops/index.md b/src/connections/destinations/catalog/actions-loops/index.md index 95752b48e9..d4af1fd414 100644 --- a/src/connections/destinations/catalog/actions-loops/index.md +++ b/src/connections/destinations/catalog/actions-loops/index.md @@ -7,7 +7,7 @@ id: 63360a5fe290ca3fdfad4a68 {% include content/plan-grid.md name="actions" %} -[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. +[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. You can use this Segment destination to create and update your Loops contacts and trigger email sending with events. @@ -66,4 +66,4 @@ Now you are able to send a test event. You can verify that the event was trigger Read the tutorial for sending events [in the Loops docs](https://loops.so/docs/add-users/segment#send-event){:target="_blank"}. -{% include components/actions-fields.html %} \ No newline at end of file +{% include components/actions-fields.html %} diff --git a/src/connections/destinations/catalog/actions-moloco-rmp/index.md b/src/connections/destinations/catalog/actions-moloco-rmp/index.md index 595df788ed..ac53d4b1b1 100644 --- a/src/connections/destinations/catalog/actions-moloco-rmp/index.md +++ b/src/connections/destinations/catalog/actions-moloco-rmp/index.md @@ -90,7 +90,7 @@ However for iOS and Android, it won’t collect page information. Moloco Commercial Media requires the [page_id](https://mcm-docs.moloco.com/docs/51-user-event-data-specifications#page_view-event-type){:target="_blank”} attribute for a PAGE_VIEW event. Using the Web SDK, the page_id can be associated with the path attribute. However for iOS/Android, Moloco Commercial Media recommends using the Page Identifier Token field. The Page Identifier Token field accepts key:value pairs of strings that can identify the page. -Stringification Logic is: {key}:{value}s concatenated by ";" +Stringification Logic is: \{key}:\{value}s concatenated by ";" Moloco Commercial Media ignores the Page Identifier Token if page_id is passed, as page_id has a higher priority. diff --git a/src/connections/destinations/catalog/actions-movable-ink/index.md b/src/connections/destinations/catalog/actions-movable-ink/index.md index 0f15e7d7d2..19c1f037b6 100644 --- a/src/connections/destinations/catalog/actions-movable-ink/index.md +++ b/src/connections/destinations/catalog/actions-movable-ink/index.md @@ -47,7 +47,7 @@ Your client experience manager will then provide you with a Movable Ink endpoint 4. Map specific fields (optional): - Click **Test Mapping** to send a test event and identify any potential issues. - Return to the Mappings overview page and enable your mapping. -6. Navigate to your integration’s **Settings** tab and activate the integration by toggling on **Enable Destination**. +5. Navigate to your integration’s **Settings** tab and activate the integration by toggling on **Enable Destination**. > info "" > For any unexpected errors, contact your Movable Ink client experience team with the full sample payload. diff --git a/src/connections/destinations/catalog/actions-optimizely-feature-experimentation-cloud/index.md b/src/connections/destinations/catalog/actions-optimizely-feature-experimentation-cloud/index.md index 01ffec24f3..1d1917b35b 100644 --- a/src/connections/destinations/catalog/actions-optimizely-feature-experimentation-cloud/index.md +++ b/src/connections/destinations/catalog/actions-optimizely-feature-experimentation-cloud/index.md @@ -58,4 +58,4 @@ Segment also handles the following mapping: ## GDPR Support 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. -{% include components/actions-fields.html settings="true"%} +{% include components/actions-fields.html settings="true" %} diff --git a/src/connections/destinations/catalog/actions-pinterest-conversions-api/index.md b/src/connections/destinations/catalog/actions-pinterest-conversions-api/index.md index 3c4cf30deb..8dae16424e 100644 --- a/src/connections/destinations/catalog/actions-pinterest-conversions-api/index.md +++ b/src/connections/destinations/catalog/actions-pinterest-conversions-api/index.md @@ -47,7 +47,7 @@ To connect the Pinterest Conversions API Destination: 8. Follow the steps in [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings). 9. Toggle **Enable Destination** on, then click **Save Changes**. -{% include components/actions-fields.html settings="true"%} +{% include components/actions-fields.html settings="true" %} > info "Setting conversion type" > 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 After you start sending events, you should start seeing them in dashboard. You can confirm that Pinterest received them by following these steps: 1. Go to **Events Overview** in Pinterest. -2. Click **Event History** to see all the events Segment sent to Pinterest conversions. \ No newline at end of file +2. Click **Event History** to see all the events Segment sent to Pinterest conversions. diff --git a/src/connections/destinations/catalog/actions-s3/index.md b/src/connections/destinations/catalog/actions-s3/index.md index 61acf60c98..db3ab8a919 100644 --- a/src/connections/destinations/catalog/actions-s3/index.md +++ b/src/connections/destinations/catalog/actions-s3/index.md @@ -101,7 +101,7 @@ To finish the setup, enable the AWS S3 (Actions) Destination in your workspace: * Enter the IAM External ID, which is a value set in the Trust Relationship under your AWS IAM Role. 5. Enable the destination. -{% include components/actions-fields.html settings="true"%} +{% include components/actions-fields.html settings="true" %} ### Step 3: Configure the AWS S3 (Actions) Destination mappings 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 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. 4. Configure any additional settings as required. 5. Enable the Mapping. -6. Verify that Segment is sending data to your S3 bucket by navigating to `/` in the AWS console. \ No newline at end of file +6. Verify that Segment is sending data to your S3 bucket by navigating to `/` in the AWS console.