From 1d2a9ae98f1c19f77c608f605130194304998759 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Tue, 8 Apr 2025 17:28:12 +1000 Subject: [PATCH 01/17] Ortto index docs rev 1 --- .../catalog/actions-ortto/index.md | 47 +++++++++++++++++++ 1 file changed, 47 insertions(+) create mode 100644 src/connections/destinations/catalog/actions-ortto/index.md diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md new file mode 100644 index 0000000000..831209498b --- /dev/null +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -0,0 +1,47 @@ +--- +# The end name should be similar to `Slack (Actions) Destination` +title: Ortto (Actions) Destination +hide-boilerplate: true +hide-dossier: true +--- + +{% include content/plan-grid.md name="actions" %} + +[Ortto](https://ortto.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} helps thousands of organizations worldwide automate their communications — including email newsletters, abandoned cart emails, SMS messages, and more — to accelerate marketing and business growth. + +Once Segment is connected to Ortto, you can take advantage of Ortto's powerful [campaign](https://help.ortto.com/user/latest/campaigns/){:target="_blank"} features on your Segment customer data. + +This destination is maintained by Ortto. For support or questions,[contact the Ortto Support team](mailto:help@ortto.com). + + + + +> success "" +> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Ortto Segment destination. There's also a page about the [non-Actions Ortto destination](/docs/connections/destinations/catalog/autopilotapp/). Both of these destinations receives data from Segment. + + + +## Ortto (Actions) provides the following benefits over the classic Ortto destination: + +- **Granular control and flexibility**. Map any Segment event type to specific Ortto actions with full control over field mappings. This lets you tailor how and when customer data is sent to Ortto, ensuring more accurate and relevant automations. +- **Audience syncing**. Ortto (Actions) lets you sync computed audiences from Segment Engage directly into Ortto, enabling precise activation of rich, behavior-based audiences—ideal for lifecycle marketing, retargeting, and personalization at scale. You can also manually create or select existing audiences in Ortto and dynamically add or remove contacts as part of profile upserts or activity tracking, giving you full control over audience membership in real time. +- **Improved transparency and debugging**.Because Ortto (Actions) uses direct API calls to Ortto’s endpoints, it provides clearer delivery status and error messages to help teams troubleshoot faster and ensure data integrity. +- **Future-proofed**. Built on Segment’s modern Destination Actions framework, Ortto (Actions) will receive ongoing updates and support for new features, while the classic destination remains static. + + +## Getting started + +1. In the Segment web app, go to **Connections > Catalog**, then open the **Destinations** tab. +2. Search for **Ortto (Actions)**, select it, and then add the destination. +3. Choose the existing Source you want to connect to **Ortto (Actions)**. +4. Name your destination. You can either configure the settings manually or copy them from an existing instance, then create a new destination. +5. [Log in](https://ortto.app/login){:target="_blank"} to your Ortto account and add a new **Segment (Actions)** data source, or use an existing one. +6. Copy the API key from the data source and paste it into the destination **Settings** in Segment. + + +{% include components/actions-fields.html %} + +## Notes + +- All events sent through the supported actions must include either the `User ID` or `Anonymous ID` fields, regardless of whether these are set as [Unique Identifiers](https://help.ortto.com/a-55-unique-identifiers){:target="_blank"} in Ortto. +- Ortto (Actions) and Ortto Classic are subject to the same [rate limits](https://help.ortto.com/segment-integration#Rate-limits){:target="_blank"}. Profile upserts, audience entry requests, and activity tracking events that include contact traits are all treated as identify events. \ No newline at end of file From 67f61bc46cd1781ee203e587adad04fc39c04e52 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Wed, 9 Apr 2025 13:16:18 +1000 Subject: [PATCH 02/17] Remove comments --- .../destinations/catalog/actions-ortto/index.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index 831209498b..a725234c96 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -1,5 +1,4 @@ --- -# The end name should be similar to `Slack (Actions) Destination` title: Ortto (Actions) Destination hide-boilerplate: true hide-dossier: true @@ -11,11 +10,9 @@ hide-dossier: true Once Segment is connected to Ortto, you can take advantage of Ortto's powerful [campaign](https://help.ortto.com/user/latest/campaigns/){:target="_blank"} features on your Segment customer data. -This destination is maintained by Ortto. For support or questions,[contact the Ortto Support team](mailto:help@ortto.com). +This destination is maintained by Ortto. For support or questions, [contact](mailto:help@ortto.com) the Ortto Support team. - - > success "" > **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Ortto Segment destination. There's also a page about the [non-Actions Ortto destination](/docs/connections/destinations/catalog/autopilotapp/). Both of these destinations receives data from Segment. @@ -25,7 +22,7 @@ This destination is maintained by Ortto. For support or questions,[contact the O - **Granular control and flexibility**. Map any Segment event type to specific Ortto actions with full control over field mappings. This lets you tailor how and when customer data is sent to Ortto, ensuring more accurate and relevant automations. - **Audience syncing**. Ortto (Actions) lets you sync computed audiences from Segment Engage directly into Ortto, enabling precise activation of rich, behavior-based audiences—ideal for lifecycle marketing, retargeting, and personalization at scale. You can also manually create or select existing audiences in Ortto and dynamically add or remove contacts as part of profile upserts or activity tracking, giving you full control over audience membership in real time. -- **Improved transparency and debugging**.Because Ortto (Actions) uses direct API calls to Ortto’s endpoints, it provides clearer delivery status and error messages to help teams troubleshoot faster and ensure data integrity. +- **Improved transparency and debugging**. Because Ortto (Actions) uses direct API calls to Ortto’s endpoints, it provides clearer delivery status and error messages to help teams troubleshoot faster and ensure data integrity. - **Future-proofed**. Built on Segment’s modern Destination Actions framework, Ortto (Actions) will receive ongoing updates and support for new features, while the classic destination remains static. From 4504983aa5cded35d1414834fba245af8bf86c70 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Mon, 19 May 2025 10:46:26 +1000 Subject: [PATCH 03/17] Update audience syncying docs --- .../catalog/actions-ortto/index.md | 22 ++++++++++++++----- 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index a725234c96..31241cd62a 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -21,8 +21,7 @@ This destination is maintained by Ortto. For support or questions, [contact](mai ## Ortto (Actions) provides the following benefits over the classic Ortto destination: - **Granular control and flexibility**. Map any Segment event type to specific Ortto actions with full control over field mappings. This lets you tailor how and when customer data is sent to Ortto, ensuring more accurate and relevant automations. -- **Audience syncing**. Ortto (Actions) lets you sync computed audiences from Segment Engage directly into Ortto, enabling precise activation of rich, behavior-based audiences—ideal for lifecycle marketing, retargeting, and personalization at scale. You can also manually create or select existing audiences in Ortto and dynamically add or remove contacts as part of profile upserts or activity tracking, giving you full control over audience membership in real time. -- **Improved transparency and debugging**. Because Ortto (Actions) uses direct API calls to Ortto’s endpoints, it provides clearer delivery status and error messages to help teams troubleshoot faster and ensure data integrity. +- **Improved transparency and debugging**. Because Ortto (Actions) uses direct API calls to Ortto’s endpoints, it provides clearer delivery status and error messages to help teams troubleshoot faster and ensure data integrity. It also supports HTTP [multi-status](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/207) responses, allowing multiple outcomes to be returned in a single response—this means partial successes or failures can be clearly identified, making debugging more efficient and reducing the risk of silent data loss. - **Future-proofed**. Built on Segment’s modern Destination Actions framework, Ortto (Actions) will receive ongoing updates and support for new features, while the classic destination remains static. @@ -35,10 +34,21 @@ This destination is maintained by Ortto. For support or questions, [contact](mai 5. [Log in](https://ortto.app/login){:target="_blank"} to your Ortto account and add a new **Segment (Actions)** data source, or use an existing one. 6. Copy the API key from the data source and paste it into the destination **Settings** in Segment. - {% include components/actions-fields.html %} -## Notes +> [!IMPORTANT] +> All events sent through the supported actions must include either the `User ID` or `Anonymous ID` fields, regardless of whether these are set as [Unique Identifiers](https://help.ortto.com/a-55-unique-identifiers){:target="_blank"} in Ortto. + +> [!IMPORTANT] +> Ortto (Actions) and Ortto Classic are subject to the same [rate limits](https://help.ortto.com/segment-integration#Rate-limits){:target="_blank"}. Profile upserts, audience entry requests, and activity tracking events that include contact traits are all treated as identify events. + +## Audience Membership + +**Ortto (Actions)** allows you to sync your Segment users with an Ortto Audience, enabling precise activation of rich, behavior-based segments—perfect for lifecycle marketing, retargeting, and large-scale personalization. You can manually create new audiences or use existing ones in Ortto, and dynamically add or remove contacts through profile upserts or activity tracking. This gives you real-time control over audience membership. + +To prevent excessive churn, audience membership in Ortto is protected from frequent updates. When too many enter/exit events are received from Segment, Ortto aggregates these changes and updates the contact’s final audience state once per day. + +> [!NOTE] +> Segment audience names in Ortto are case-sensitive and must be unique. If you enter the name of an existing audience during action setup, contacts will be synced to that existing audience in Ortto. + -- All events sent through the supported actions must include either the `User ID` or `Anonymous ID` fields, regardless of whether these are set as [Unique Identifiers](https://help.ortto.com/a-55-unique-identifiers){:target="_blank"} in Ortto. -- Ortto (Actions) and Ortto Classic are subject to the same [rate limits](https://help.ortto.com/segment-integration#Rate-limits){:target="_blank"}. Profile upserts, audience entry requests, and activity tracking events that include contact traits are all treated as identify events. \ No newline at end of file From 129a99ce99cd04280c63c11b28cb6be3bb38e3c1 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Sat, 31 May 2025 07:21:55 +1000 Subject: [PATCH 04/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index 31241cd62a..e9f616bee3 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -10,7 +10,7 @@ hide-dossier: true Once Segment is connected to Ortto, you can take advantage of Ortto's powerful [campaign](https://help.ortto.com/user/latest/campaigns/){:target="_blank"} features on your Segment customer data. -This destination is maintained by Ortto. For support or questions, [contact](mailto:help@ortto.com) the Ortto Support team. +This destination is maintained by Ortto. For support or questions, [contact the Ortto Support team](mailto:help@ortto.com). > success "" From 55a8364a9d0e81ebea1067876e484bed3cd81519 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Sat, 31 May 2025 07:30:33 +1000 Subject: [PATCH 05/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index e9f616bee3..d6b6491f82 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -14,7 +14,7 @@ This destination is maintained by Ortto. For support or questions, [contact the > success "" -> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Ortto Segment destination. There's also a page about the [non-Actions Ortto destination](/docs/connections/destinations/catalog/autopilotapp/). Both of these destinations receives data from Segment. +> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Ortto Segment destination. There's also a page about the [non-Actions Ortto destination](/docs/connections/destinations/catalog/autopilotapp/). Both of these destinations receives data from Segment. Ortto (Actions) and Ortto Classic are subject to the same [rate limits](https://help.ortto.com/segment-integration#Rate-limits){:target="_blank"}. Profile upserts, audience entry requests, and activity tracking events that include contact traits are all treated as identify events. From 832227c4ab4035786596772ba10df20b74a78674 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Sat, 31 May 2025 07:30:52 +1000 Subject: [PATCH 06/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index d6b6491f82..3c76eae261 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -20,7 +20,7 @@ This destination is maintained by Ortto. For support or questions, [contact the ## Ortto (Actions) provides the following benefits over the classic Ortto destination: -- **Granular control and flexibility**. Map any Segment event type to specific Ortto actions with full control over field mappings. This lets you tailor how and when customer data is sent to Ortto, ensuring more accurate and relevant automations. +- **Granular control and flexibility**: Map any Segment event type to specific Ortto actions with full control over field mappings. This lets you tailor how and when customer data is sent to Ortto, ensuring more accurate and relevant automations. - **Improved transparency and debugging**. Because Ortto (Actions) uses direct API calls to Ortto’s endpoints, it provides clearer delivery status and error messages to help teams troubleshoot faster and ensure data integrity. It also supports HTTP [multi-status](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/207) responses, allowing multiple outcomes to be returned in a single response—this means partial successes or failures can be clearly identified, making debugging more efficient and reducing the risk of silent data loss. - **Future-proofed**. Built on Segment’s modern Destination Actions framework, Ortto (Actions) will receive ongoing updates and support for new features, while the classic destination remains static. From dad5cb27d2d5d281b889709a0fcfd76af0d27d7c Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Sat, 31 May 2025 07:31:23 +1000 Subject: [PATCH 07/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index 3c76eae261..296fa4aadd 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -21,7 +21,7 @@ This destination is maintained by Ortto. For support or questions, [contact the ## Ortto (Actions) provides the following benefits over the classic Ortto destination: - **Granular control and flexibility**: Map any Segment event type to specific Ortto actions with full control over field mappings. This lets you tailor how and when customer data is sent to Ortto, ensuring more accurate and relevant automations. -- **Improved transparency and debugging**. Because Ortto (Actions) uses direct API calls to Ortto’s endpoints, it provides clearer delivery status and error messages to help teams troubleshoot faster and ensure data integrity. It also supports HTTP [multi-status](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/207) responses, allowing multiple outcomes to be returned in a single response—this means partial successes or failures can be clearly identified, making debugging more efficient and reducing the risk of silent data loss. +- **Improved transparency and debugging**: Because Ortto (Actions) uses direct API calls to Ortto’s endpoints, it provides clearer delivery status and error messages to help teams troubleshoot faster and ensure data integrity. It also supports HTTP [multi-status](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/207){:target="_blank"} responses, allowing multiple outcomes to be returned in a single response—this means partial successes or failures can be clearly identified, reducing the risk of silent data loss and making debugging more efficient. - **Future-proofed**. Built on Segment’s modern Destination Actions framework, Ortto (Actions) will receive ongoing updates and support for new features, while the classic destination remains static. From 462294c3182e5dae476d1b276042a67d46a11519 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Sat, 31 May 2025 07:31:40 +1000 Subject: [PATCH 08/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index 296fa4aadd..a66a88f7d7 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -22,7 +22,7 @@ This destination is maintained by Ortto. For support or questions, [contact the - **Granular control and flexibility**: Map any Segment event type to specific Ortto actions with full control over field mappings. This lets you tailor how and when customer data is sent to Ortto, ensuring more accurate and relevant automations. - **Improved transparency and debugging**: Because Ortto (Actions) uses direct API calls to Ortto’s endpoints, it provides clearer delivery status and error messages to help teams troubleshoot faster and ensure data integrity. It also supports HTTP [multi-status](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/207){:target="_blank"} responses, allowing multiple outcomes to be returned in a single response—this means partial successes or failures can be clearly identified, reducing the risk of silent data loss and making debugging more efficient. -- **Future-proofed**. Built on Segment’s modern Destination Actions framework, Ortto (Actions) will receive ongoing updates and support for new features, while the classic destination remains static. +- **Future-proofed**: Built on Segment’s modern Destination Actions framework, Ortto (Actions) will receive ongoing updates and support for new features, while the classic destination remains static. ## Getting started From 5253b5a040cb7cc2dec321c5066ad40ef196de46 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Sat, 31 May 2025 07:32:37 +1000 Subject: [PATCH 09/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index a66a88f7d7..432372cd5b 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -36,7 +36,7 @@ This destination is maintained by Ortto. For support or questions, [contact the {% include components/actions-fields.html %} -> [!IMPORTANT] +> warning "All events must contain an identifier" > All events sent through the supported actions must include either the `User ID` or `Anonymous ID` fields, regardless of whether these are set as [Unique Identifiers](https://help.ortto.com/a-55-unique-identifiers){:target="_blank"} in Ortto. > [!IMPORTANT] From e6a0e5f3d16842cead2e969a3223f732ddef691d Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Sat, 31 May 2025 07:34:47 +1000 Subject: [PATCH 10/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 1 - 1 file changed, 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index 432372cd5b..c171c7643c 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -40,7 +40,6 @@ This destination is maintained by Ortto. For support or questions, [contact the > All events sent through the supported actions must include either the `User ID` or `Anonymous ID` fields, regardless of whether these are set as [Unique Identifiers](https://help.ortto.com/a-55-unique-identifiers){:target="_blank"} in Ortto. > [!IMPORTANT] -> Ortto (Actions) and Ortto Classic are subject to the same [rate limits](https://help.ortto.com/segment-integration#Rate-limits){:target="_blank"}. Profile upserts, audience entry requests, and activity tracking events that include contact traits are all treated as identify events. ## Audience Membership From f54e627b9a4ad5716268943ade41c00ca53c9363 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Sat, 31 May 2025 07:40:36 +1000 Subject: [PATCH 11/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index c171c7643c..95fb4dfd42 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -47,7 +47,7 @@ This destination is maintained by Ortto. For support or questions, [contact the To prevent excessive churn, audience membership in Ortto is protected from frequent updates. When too many enter/exit events are received from Segment, Ortto aggregates these changes and updates the contact’s final audience state once per day. -> [!NOTE] -> Segment audience names in Ortto are case-sensitive and must be unique. If you enter the name of an existing audience during action setup, contacts will be synced to that existing audience in Ortto. +> info "Ortto audience names must be unique" +> Segment audience names in Ortto are case-sensitive and must be unique. If you enter the name of an existing audience during action setup, contacts will be synced to the existing audience in Ortto. From 73899e4e43a3940e5e54bab13e3ded348ad42e0d Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Sat, 31 May 2025 07:42:27 +1000 Subject: [PATCH 12/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 1 - 1 file changed, 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index 95fb4dfd42..1f9da1da33 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -39,7 +39,6 @@ This destination is maintained by Ortto. For support or questions, [contact the > warning "All events must contain an identifier" > All events sent through the supported actions must include either the `User ID` or `Anonymous ID` fields, regardless of whether these are set as [Unique Identifiers](https://help.ortto.com/a-55-unique-identifiers){:target="_blank"} in Ortto. -> [!IMPORTANT] ## Audience Membership From ebb80920d0e21293b3f67f61364f946c5e6e2c52 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Mon, 2 Jun 2025 08:59:46 +1000 Subject: [PATCH 13/17] Update audience membership limits --- src/connections/destinations/catalog/actions-ortto/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index 1f9da1da33..42c8457e72 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -44,7 +44,7 @@ This destination is maintained by Ortto. For support or questions, [contact the **Ortto (Actions)** allows you to sync your Segment users with an Ortto Audience, enabling precise activation of rich, behavior-based segments—perfect for lifecycle marketing, retargeting, and large-scale personalization. You can manually create new audiences or use existing ones in Ortto, and dynamically add or remove contacts through profile upserts or activity tracking. This gives you real-time control over audience membership. -To prevent excessive churn, audience membership in Ortto is protected from frequent updates. When too many enter/exit events are received from Segment, Ortto aggregates these changes and updates the contact’s final audience state once per day. +To prevent excessive churn, Ortto defers audience membership updates when a contact rapidly enters and exits an audience within a short period. Specifically, re-entry is blocked if it occurs within one minute of exiting. These changes are then aggregated and the contact’s membership is recalculated once per day based on the most recent instruction, helping to maintain stable audience membership and reduce unnecessary fluctuations. > info "Ortto audience names must be unique" > Segment audience names in Ortto are case-sensitive and must be unique. If you enter the name of an existing audience during action setup, contacts will be synced to the existing audience in Ortto. From 3334649485c796b0e81b90bdfd35604be4e051ae Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Mon, 2 Jun 2025 10:15:06 +1000 Subject: [PATCH 14/17] Further explanation of audience limits --- src/connections/destinations/catalog/actions-ortto/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index 42c8457e72..7903c842e7 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -44,7 +44,8 @@ This destination is maintained by Ortto. For support or questions, [contact the **Ortto (Actions)** allows you to sync your Segment users with an Ortto Audience, enabling precise activation of rich, behavior-based segments—perfect for lifecycle marketing, retargeting, and large-scale personalization. You can manually create new audiences or use existing ones in Ortto, and dynamically add or remove contacts through profile upserts or activity tracking. This gives you real-time control over audience membership. -To prevent excessive churn, Ortto defers audience membership updates when a contact rapidly enters and exits an audience within a short period. Specifically, re-entry is blocked if it occurs within one minute of exiting. These changes are then aggregated and the contact’s membership is recalculated once per day based on the most recent instruction, helping to maintain stable audience membership and reduce unnecessary fluctuations. +Rapid re-entry to an audience is blocked by Ortto to avoid the potential of undesirable side-effects from asynchronous updates. Specifically, if a contact has exited an audience and then an update causes them to re-enter within 1 minute of exiting, this update will be blocked. Instead, a daily synchronisation is applied to make sure the result of any rapid updates is correctly applied. +The segment member audience field will be updated as normal, and any audience re-entries throughout the day that are longer than 1 minute after the last exit will be processed as normal, in real time. > info "Ortto audience names must be unique" > Segment audience names in Ortto are case-sensitive and must be unique. If you enter the name of an existing audience during action setup, contacts will be synced to the existing audience in Ortto. From 1f5cb690772ea1c21958c356f8fda8e4e5424b78 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Tue, 3 Jun 2025 12:42:47 +1000 Subject: [PATCH 15/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index 7903c842e7..44da16146f 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -45,7 +45,7 @@ This destination is maintained by Ortto. For support or questions, [contact the **Ortto (Actions)** allows you to sync your Segment users with an Ortto Audience, enabling precise activation of rich, behavior-based segments—perfect for lifecycle marketing, retargeting, and large-scale personalization. You can manually create new audiences or use existing ones in Ortto, and dynamically add or remove contacts through profile upserts or activity tracking. This gives you real-time control over audience membership. Rapid re-entry to an audience is blocked by Ortto to avoid the potential of undesirable side-effects from asynchronous updates. Specifically, if a contact has exited an audience and then an update causes them to re-enter within 1 minute of exiting, this update will be blocked. Instead, a daily synchronisation is applied to make sure the result of any rapid updates is correctly applied. -The segment member audience field will be updated as normal, and any audience re-entries throughout the day that are longer than 1 minute after the last exit will be processed as normal, in real time. +Ortto updates the Segment member audience field as normal, and any audience re-entries throughout the day that are longer than 1 minute after the last exit are processed in real time. > info "Ortto audience names must be unique" > Segment audience names in Ortto are case-sensitive and must be unique. If you enter the name of an existing audience during action setup, contacts will be synced to the existing audience in Ortto. From 50e2c8e30029ef91b3ddfbb6c52445c0b02a4c23 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Tue, 3 Jun 2025 12:42:58 +1000 Subject: [PATCH 16/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index 44da16146f..e6eeff744a 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -2,6 +2,8 @@ title: Ortto (Actions) Destination hide-boilerplate: true hide-dossier: true +id: 682db7017819e7e055f55cb4 +beta: true --- {% include content/plan-grid.md name="actions" %} From d476ae143111cf1f23c2541f5ff30fa02633a548 Mon Sep 17 00:00:00 2001 From: Alex Golshani Date: Tue, 3 Jun 2025 12:43:11 +1000 Subject: [PATCH 17/17] Update src/connections/destinations/catalog/actions-ortto/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/destinations/catalog/actions-ortto/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-ortto/index.md b/src/connections/destinations/catalog/actions-ortto/index.md index e6eeff744a..9ededd79b2 100644 --- a/src/connections/destinations/catalog/actions-ortto/index.md +++ b/src/connections/destinations/catalog/actions-ortto/index.md @@ -46,7 +46,7 @@ This destination is maintained by Ortto. For support or questions, [contact the **Ortto (Actions)** allows you to sync your Segment users with an Ortto Audience, enabling precise activation of rich, behavior-based segments—perfect for lifecycle marketing, retargeting, and large-scale personalization. You can manually create new audiences or use existing ones in Ortto, and dynamically add or remove contacts through profile upserts or activity tracking. This gives you real-time control over audience membership. -Rapid re-entry to an audience is blocked by Ortto to avoid the potential of undesirable side-effects from asynchronous updates. Specifically, if a contact has exited an audience and then an update causes them to re-enter within 1 minute of exiting, this update will be blocked. Instead, a daily synchronisation is applied to make sure the result of any rapid updates is correctly applied. +Ortto blocks rapid audience re-entry to avoid undesirable side-effects from asynchronous updates. If a contact exits an audience and then re-enters the audience within 1 minute, Ortto blocks the update that causes them to rejoin the audience. Ortto uses a daily synchronization to make sure the result of any rapid updates is correctly applied. Ortto updates the Segment member audience field as normal, and any audience re-entries throughout the day that are longer than 1 minute after the last exit are processed in real time. > info "Ortto audience names must be unique"