Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Ortto (Actions) Destination


(new)

Beta

This feature is in active development and may change before general availability.

Ortto(link takes you to an external page) 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(link takes you to an external page) features on your Segment customer data.

This destination is maintained by Ortto. For support or questions, contact the Ortto Support team.

(success)

Success!

Good to know: This page is about the Actions-framework Ortto Segment destination. There's also a page about the non-Actions Ortto destination. Both of these destinations receives data from Segment. Ortto (Actions) and Ortto Classic are subject to the same rate limits(link takes you to an external page). 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:

ortto-actions-provides-the-following-benefits-over-the-classic-ortto-destination page anchor
  • 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(link takes you to an external page) 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.

  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(link takes you to an external page) 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.

Property nameTypeRequiredDescription
API Keypassword
required

Ortto API key


Ortto (Actions) has the following presets

Preset NameTriggerDefault Action
Upsert ContactEvent type = "identify"Upsert Contact
Track ActivityEvent type = "track"Track Activity

Build your own Mappings. Combine supported triggers with the following Ortto-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Track Activity

track-activity page anchor

Track user activity

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

Property nameTypeRequiredDescription
TimestampSTRING

Optional

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.


Message IDSTRING

Optional

Message ID. Combined with the event timestamp to uniquely identify an activity in Ortto. If omitted, duplicate activities may occur.


User IDSTRING

Optional

The unique user identifier


Anonymous IDSTRING

Optional

Anonymous user identifier


Batch dataBOOLEAN

Optional

When enabled, events will be sent to Ortto in batches for improved efficiency.


IP AddressSTRING

Optional

The IP address of the location where the activity occurred.


LocationOBJECT

Optional

The location where the activity occurred. Takes priority over the IP address.


Custom Contact traitsOBJECT

Optional

key-value custom property pairs to be assigned to the Contact's profile


Audience update modeSTRING

Optional

Indicates whether the Contact should be added to or removed from the Audience.


Event nameSTRING
required

Event name


Activity propertiesOBJECT

Optional

An object containing key-value pairs representing activity attributes


Audience NameSTRING

Optional

The name of the Ortto Audience to link the Contact to.


Associate AudienceOBJECT

Optional

Link the Contact to an Audience in Ortto. If the Audience does not already exist, it will be created in Ortto.

Create or update a Contact in Ortto

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

Property nameTypeRequiredDescription
User IDSTRING

Optional

The unique user identifier


Anonymous IDSTRING

Optional

Anonymous user identifier


Batch dataBOOLEAN

Optional

When enabled, events will be sent to Ortto in batches for improved efficiency.


IP AddressSTRING

Optional

The Contact's IP address


LocationOBJECT

Optional

The Contact's location. Takes priority over the IP address.


Custom Contact traitsOBJECT

Optional

An object containing key-value pairs representing custom properties assigned to Contact profile


Audience update modeSTRING

Optional

Indicates whether the Contact should be added to or removed from the Audience.


Audience NameSTRING

Optional

The name of the Ortto Audience to link the Contact to.


Associate AudienceOBJECT

Optional

Link the Contact to an Audience in Ortto. If the Audience does not already exist, it will be created in Ortto.

(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(link takes you to an external page) in Ortto.


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.

(information)

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.