Skip to content

Commit 4504983

Browse files
committed
Update audience syncying docs
1 parent 4733260 commit 4504983

File tree

1 file changed

+16
-6
lines changed
  • src/connections/destinations/catalog/actions-ortto

1 file changed

+16
-6
lines changed

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

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,7 @@ This destination is maintained by Ortto. For support or questions, [contact](mai
2121
## Ortto (Actions) provides the following benefits over the classic Ortto destination:
2222

2323
- **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.
24-
- **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.
25-
- **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.
24+
- **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.
2625
- **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.
2726

2827

@@ -35,10 +34,21 @@ This destination is maintained by Ortto. For support or questions, [contact](mai
3534
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.
3635
6. Copy the API key from the data source and paste it into the destination **Settings** in Segment.
3736

38-
3937
{% include components/actions-fields.html %}
4038

41-
## Notes
39+
> [!IMPORTANT]
40+
> 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.
41+
42+
> [!IMPORTANT]
43+
> 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.
44+
45+
## Audience Membership
46+
47+
**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.
48+
49+
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.
50+
51+
> [!NOTE]
52+
> 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.
53+
4254

43-
- 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.
44-
- 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.

0 commit comments

Comments
 (0)