# Ortto (Actions) Destination

> \[!IMPORTANT]
>
> This feature is in active development and may change before general availability.

[Ortto](https://ortto.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) 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/) 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).

> \[!TIP]
>
> **Good to know**: This page is about the [Actions-framework](/docs/segment/connections/destinations/actions/) Ortto Segment destination. There's also a page about the [non-Actions Ortto destination](/docs/segment/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). Profile upserts, audience entry requests, and activity tracking events that include contact traits are all treated as identify events.

## 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, 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.

## 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) 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.

## Destination Settings

| Field   | Description   | Required | Type     |
| ------- | ------------- | -------- | -------- |
| API Key | Ortto API key | Yes      | password |

## Available Presets

Ortto (Actions) has the following presets

| Preset Name    | Trigger                 | Default Action |
| -------------- | ----------------------- | -------------- |
| Upsert Contact | Event type = "identify" | Upsert Contact |
| Track Activity | Event type = "track"    | Track Activity |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Ortto-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Track Activity](#track-activity)
* [Upsert Contact](#upsert-contact-1)

### Track Activity

Track user activity

Track Activity is a **Cloud** action. The default Trigger is `type = "track"`

| Field                 | Description                                                                                                                                              | Required | Type    |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- |
| Timestamp             | Event timestamp in ISO 8601 format. Used with the Message ID to uniquely identify an activity in Ortto. If not provided, duplicate activities may occur. | No       | STRING  |
| Message ID            | Message ID. Combined with the event timestamp to uniquely identify an activity in Ortto. If omitted, duplicate activities may occur.                     | No       | STRING  |
| User ID               | The unique user identifier                                                                                                                               | No       | STRING  |
| Anonymous ID          | Anonymous user identifier                                                                                                                                | No       | STRING  |
| Batch data            | When enabled, events will be sent to Ortto in batches for improved efficiency.                                                                           | No       | BOOLEAN |
| IP Address            | The IP address of the location where the activity occurred.                                                                                              | No       | STRING  |
| Location              | The location where the activity occurred. Takes priority over the IP address.                                                                            | No       | OBJECT  |
| Custom Contact traits | key-value custom property pairs to be assigned to the Contact's profile                                                                                  | No       | OBJECT  |
| Audience update mode  | Indicates whether the Contact should be added to or removed from the Audience.                                                                           | No       | STRING  |
| Event name            | Event name                                                                                                                                               | Yes      | STRING  |
| Activity properties   | An object containing key-value pairs representing activity attributes                                                                                    | No       | OBJECT  |
| Audience Name         | The name of the Ortto Audience to link the Contact to.                                                                                                   | No       | STRING  |
| Associate Audience    | Link the Contact to an Audience in Ortto. If the Audience does not already exist, it will be created in Ortto.                                           | No       | OBJECT  |

### Upsert Contact

Create or update a Contact in Ortto

Upsert Contact is a **Cloud** action. The default Trigger is `type = "identify"`

| Field                 | Description                                                                                                    | Required | Type    |
| --------------------- | -------------------------------------------------------------------------------------------------------------- | -------- | ------- |
| User ID               | The unique user identifier                                                                                     | No       | STRING  |
| Anonymous ID          | Anonymous user identifier                                                                                      | No       | STRING  |
| Batch data            | When enabled, events will be sent to Ortto in batches for improved efficiency.                                 | No       | BOOLEAN |
| IP Address            | The Contact's IP address                                                                                       | No       | STRING  |
| Location              | The Contact's location. Takes priority over the IP address.                                                    | No       | OBJECT  |
| Custom Contact traits | An object containing key-value pairs representing custom properties assigned to Contact profile                | No       | OBJECT  |
| Audience update mode  | Indicates whether the Contact should be added to or removed from the Audience.                                 | No       | STRING  |
| Audience Name         | The name of the Ortto Audience to link the Contact to.                                                         | No       | STRING  |
| Associate Audience    | Link the Contact to an Audience in Ortto. If the Audience does not already exist, it will be created in Ortto. | No       | OBJECT  |

> \[!WARNING]
>
> 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) in Ortto.

## 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 define which audience the contact should be linked to, enter the **Audience Name** in the "**Associate Audience**" section.

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.

> \[!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 the existing audience in Ortto.