# Collab Travel CRM 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 **Collab Travel CRM** 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.
* This destination is **Beta.**

[Collab Travel CRM](https://collabtravelcrm.com) is an all-in-one platform for modern travel agencies. This destination lets you sync your bookings, leads, and agent activity directly with marketing and analytics tools.

This destination is maintained by Collab Travel CRM. For any issues with the destination, [contact the Collab Travel CRM support team](mailto:support@collabtravelcrm.com).

## Getting started

### Generate your API Key

1. Log in to your [Collab Travel CRM](https://collabtravelcrm.com) account.
2. Navigate to **Settings > Integrations**.
3. Go to the **Segment** integration card.
4. Click **Generate Webhook Secret**. Copy the secret - you need this to configure the destination in Segment.

### Configure the destination in Segment

To set up the Collab Travel CRM destination in Segment:

1. From the Segment web app, go to **Connections > Catalog**.
2. Search for "Collab Travel CRM" in the Destinations Catalog, and select your destination.
3. Configure your destination.
4. Choose the source you want to connect the destination to.
5. Paste the API Key (**Webhook Secret**), generated in the Collab Travel CRM dashboard, into the Segment connection settings.
6. Save your settings.

## Data mapping

Collab Travel CRM automatically maps Segment data to CRM contacts:

| Segment field      | Collab CRM field |
| ------------------ | ---------------- |
| `userId`           | External ID      |
| `traits.email`     | Email            |
| `traits.firstName` | First Name       |
| `traits.lastName`  | Last Name        |
| `traits.phone`     | Phone            |

## Supported methods

Collab Travel CRM supports Segment's [Identify](#identify) and [Track](#track) methods.

### Identify

Send Identify calls to create or update Contacts in Collab Travel CRM.

To configure how user traits are mapped to Collab Travel CRM Contact fields, check the **Mappings** tab in the destination settings for your Collab Travel CRM destination.

Here's an example of an Identify call payload:

```json
{
  "type": "identify",
  "userId": "123456",
  "traits": {
    "firstName": "Grace",
    "lastName": "Hopper",
    "email": "grace@example.com",
    "phone": "+1234567890"
  }
}
```

### Track

Send Track calls to log events to the Contact's activity timeline.

Here's an example of a Track call payload:

```json
{
  "type": "track",
  "event": "Trip Booked",
  "userId": "123456",
  "properties": {
    "destination": "Paris",
    "revenue": 5000
  }
}
```

## Supported events

This destination supports the following events:

* [**Trip Booked**](#trip-booked): Sent when a booking is confirmed. This includes revenue, currency, and destination details.
* [**Lead Created**](#lead-created): Sent when a new client profile is created.
* [**Proposal Sent**](#proposal-sent): Sent when an agent shares a proposal.
* [**Review Submitted**](#review-submitted): Sent when a client submits a review.

### Trip booked

Track when a customer books a trip. This event follows the Segment [E-commerce spec](/docs/segment/connections/spec/ecommerce/v2/).

| Property              | Type   | Description                        |
| --------------------- | ------ | ---------------------------------- |
| `order_id`            | string | Unique booking identifier          |
| `revenue`             | number | Total booking value                |
| `currency`            | string | Currency code (for example, "USD") |
| `destination_city`    | string | Travel destination city            |
| `destination_country` | string | Travel destination country         |
| `start_date`          | string | Trip start date (ISO 8601)         |
| `end_date`            | string | Trip end date (ISO 8601)           |
| `number_of_travelers` | number | Number of travelers                |
| `products`            | array  | Array of itinerary items           |

### Lead created

Track when a new lead is captured.

| Property               | Type   | Description                         |
| ---------------------- | ------ | ----------------------------------- |
| `lead_source`          | string | Where the lead came from            |
| `interest_level`       | string | Lead interest level (hot/warm/cold) |
| `service_category`     | string | Type of travel service              |
| `travel_date_interest` | string | Approximate travel dates            |
| `group_size`           | number | Expected group size                 |

### Proposal sent

Track when a proposal is sent to a client.

| Property            | Type   | Description                |
| ------------------- | ------ | -------------------------- |
| `proposal_id`       | string | Unique proposal identifier |
| `proposal_title`    | string | Title of the proposal      |
| `total_value`       | number | Total proposal value       |
| `number_of_options` | number | Number of options included |
| `client_email`      | string | Client email address       |

### Review submitted

Track when a client submits a review.

| Property           | Type   | Description              |
| ------------------ | ------ | ------------------------ |
| `review_id`        | string | Unique review identifier |
| `rating`           | number | Rating score (1-5)       |
| `trip_destination` | string | Destination reviewed     |
| `review_text`      | string | Review content           |

## FAQs

#### How do I find my API Key?

You can generate an API (Webhook Secret) in your Collab Travel CRM dashboard. For more steps on how to do so, refer to the [Getting started](#generate-your-api-key) section.

#### What happens to existing contacts?

When an [Identify](/docs/segment/connections/spec/identify) event is received for an email that already exists in your CRM, the contact is updated with the new information rather than creating a duplicate.

#### What happens if a user doesn't exist?

Collab Travel CRM attempts to create a new Lead/Contact if the email address in the Identify call does not match an existing record.

#### Are events logged for auditing?

Yes, all inbound Segment events are logged in the **Segment Activity Log**, which is accessible from the **Integrations settings** page.

#### Which regions are supported?

Collab Travel CRM is hosted on [Supabase infrastructure](https://supabase.com/dashboard/project/*/settings/infrastructure) with global edge functions, providing low-latency data ingestion worldwide.

For additional support, contact [support@collabtravelcrm.com](mailto:support@collabtravelcrm.com).

## Destination Settings

| Field   | Description                                                                            | Required | Type     |
| ------- | -------------------------------------------------------------------------------------- | -------- | -------- |
| API Key | Your Collab Travel CRM webhook secret. Find this in Settings > Integrations > Segment. | Yes      | password |

## Available Presets

Collab Travel CRM has the following presets

| Preset Name    | Trigger                 | Default Action |
| -------------- | ----------------------- | -------------- |
| Identify Users | Event type = "identify" | Identify User  |
| Track Events   | Event type = "track"    | Track Event    |

## Available Actions

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

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

* [Track Event](#track-event-4)
* [Identify User](#identify-user-2)

### Track Event

Send track events (bookings, leads, page views) to Collab Travel CRM.

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

| Field            | Description                                                  | Required | Type     |
| ---------------- | ------------------------------------------------------------ | -------- | -------- |
| Event Name       | The name of the event (e.g., "Trip Booked", "Lead Created"). | Yes      | STRING   |
| Event Properties | Additional properties associated with the event.             | No       | OBJECT   |
| User ID          | The unique identifier for the user.                          | No       | STRING   |
| Anonymous ID     | An anonymous identifier when User ID is not available.       | No       | STRING   |
| Timestamp        | The timestamp of the event.                                  | No       | DATETIME |

### Identify User

Create or update a contact in Collab Travel CRM.

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

| Field             | Description                         | Required | Type   |
| ----------------- | ----------------------------------- | -------- | ------ |
| Email             | The email address of the contact.   | Yes      | STRING |
| First Name        | The first name of the contact.      | No       | STRING |
| Last Name         | The last name of the contact.       | No       | STRING |
| Phone             | The phone number of the contact.    | No       | STRING |
| User ID           | The unique identifier for the user. | No       | STRING |
| Additional Traits | Additional user traits to sync.     | No       | OBJECT |