# Koala (Cloud) Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Koala (Cloud)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

> \[!NOTE]
>
> This destination enables data transfer from Segment to Koala server-side. Additionally, Koala offers a device-mode destination that sends data directly from the browser using Koala's SDK. For more information, see the [documentation](/docs/segment/connections/destinations/catalog/actions-koala).

Koala enables you to identify website visitors with ease so you can turn traffic into actionable leads. See which companies are researching your docs, checking out your pricing page, and showing intent to buy.

Koala maintains this destination. For any issues with the destination, [contact the Koala Support team](mailto:support@getkoala.com).

## Getting Started

1. From the Segment web app, navigate to **Connections > Catalog > Destinations**.
2. Search for *Koala (Cloud)* and select **Add Destination**.
3. Select the source that will send data to Koala and follow the steps to name your destination.
4. On the **Settings** tab, input your **Public API Key** which can be found in your Koala workspace settings under **Settings > Install**.
5. Once connected, you can configure how you want to send data to Koala. By default, Segment forwards track events and identify events to Koala. Koala recommends sticking with the defaults.

## Destination Settings

| Field      | Description     | Required | Type     |
| ---------- | --------------- | -------- | -------- |
| Public Key | Your public key | Yes      | password |

## Available Presets

Koala (Cloud) has the following presets

| Preset Name    | Trigger                 | Default Action |
| -------------- | ----------------------- | -------------- |
| Track Calls    | Event type = "track"    | Track          |
| Identify Calls | Event type = "identify" | Identify       |

## Available Actions

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

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

* [Identify](#identify-9)
* [Track](#track-7)

### Identify

Send an Identify call to Koala.

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

| Field              | Description                               | Required | Type   |
| ------------------ | ----------------------------------------- | -------- | ------ |
| Email              | The email to associate with the user      | No       | STRING |
| Traits             | Traits to associate with the user         | No       | OBJECT |
| Sent At            | The timestamp of the event                | Yes      | STRING |
| Context properties | Context properties to send with the event | No       | OBJECT |
| Device IP          | The device IP collected from the context  | No       | STRING |
| MessageId          | The Segment messageId                     | Yes      | STRING |

### Track

Send an Event to Koala.

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

| Field              | Description                               | Required | Type   |
| ------------------ | ----------------------------------------- | -------- | ------ |
| Email              | The email to associate with the user      | No       | STRING |
| Event Name         | The event name                            | Yes      | STRING |
| Event properties   | Properties to send with the event         | No       | OBJECT |
| Sent At            | The timestamp of the event                | Yes      | STRING |
| Context properties | Context properties to send with the event | No       | OBJECT |
| Traits             | Traits inherited from the context object  | No       | OBJECT |
| Device IP          | The device IP collected from the context  | No       | STRING |
| MessageId          | The Segment messageId                     | Yes      | STRING |

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

> \[!NOTE]
>
> Real-time audience syncs to Koala (Cloud)  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field      | Description     | Required | Type     |
| ---------- | --------------- | -------- | -------- |
| Public Key | Your public key | Yes      | password |