Koala (Cloud) Destination
Cloud Mode Destination
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.
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.
- From the Segment web app, navigate to Connections > Catalog > Destinations.
- Search for Koala (Cloud) and select Add Destination.
- Select the source that will send data to Koala and follow the steps to name your destination.
- On the Settings tab, input your Public API Key which can be found in your Koala workspace settings under Settings > Install.
- 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.
Your public key
Koala (Cloud) has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Track Calls | Event type = "track" | Track |
| Identify Calls | Event type = "identify" | Identify |
Build your own Mappings. Combine supported triggers with the following Koala (Cloud)-supported actions:
Mapping limits per destination
Send an Identify call to Koala.
Identify is a Cloud action. The default Trigger is type = "identify"
Optional
The email to associate with the user
Optional
Traits to associate with the user
The timestamp of the event
Optional
Context properties to send with the event
Optional
The device IP collected from the context
The Segment messageId
Send an Event to Koala.
Track is a Cloud action. The default Trigger is type = "track"
Optional
The email to associate with the user
The event name
Optional
Properties to send with the event
The timestamp of the event
Optional
Context properties to send with the event
Optional
Traits inherited from the context object
Optional
The device IP collected from the context
The Segment messageId
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an 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.
Real-time to batch destination sync frequency
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.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Your public key