# Astrolabe Destination

## Destination Info

* Accepts [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Astrolabe** 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.**

[Astrolabe](https://astrolabe.so/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) is a Revenue Operations Platform built for go-to-market teams to generate pipelines, prioritize, close, and grow accounts. It's a no-code AI-based platform that empowers teams to easily access data, build advanced predictive machine learning models, create efficient workflows, and drive better results without technical expertise.

This destination is maintained by Astrolabe. For any issues with the destination, [contact the Astrolabe Support team](mailto:team@astrolabe.so).

## Getting started

### Obtain your Astrolabe API Key

1. Log in to your [Astrolabe workspace](https://console.astrolabe.so/login).
2. Navigate to the [Connectors page](https://console.astrolabe.so/connectors) and click **Add Connector**.
3. Choose the **Segment.com Connector**.
4. Name the Connector and click **Continue**.
5. Decide whether to allow or block users with free email providers, then click **Finish**.
6. Copy the **API key** displayed in the dialog window.

### Add Astrolabe Destination to your Segment Workspace

1. In the Segment web app, go to **Connections > Catalog** and then click on the **Destinations** tab.
2. Search for **Astrolabe** and select it.
3. Click **Add destination**.
4. Choose an existing data Source to connect to **Astrolabe**.
5. Give the destination a name that is recognizable.
6. Paste the **Astrolabe API key** (copied earlier).
7. Enable the destination by changing the bottom **Enable Destination** toggle to active.
8. Click **Save Changes**.

## Supported methods

Astrolabe supports the following methods, as specified in the [Segment Spec](/docs/segment/connections/spec).

### Identify

If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/segment/connections/spec/identify/) to learn about what it does. An example call would look like:

```js
analytics.identify("userId123", {
  email: "john.doe@example.com",
});
```

Segment sends Identify calls to Astrolabe as an `identify` event. When you identify a new user, Astrolabe creates a new User record. If the User already exists, Astrolabe updates the User's properties.

### Group

If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/segment/connections/spec/group/) to learn about what it does. An example call would look like:

```js
analytics.group("0e8c78ea9d97a7b8185e8632", {
  name: "Initech",
  industry: "Technology",
  employees: 329,
  plan: "enterprise",
  "total billed": 830,
});
```

Segment sends Group calls to Astrolabe as an `group` event. A `group` event can create an Account, If the Account already exists, Astrolabe updates the Account's properties. A `group` event can also associate a User to an Account within Astrolabe.

### Track

If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/segment/connections/spec/track/) to learn about what it does. An example call would look like:

```js
analytics.track("User Registered", {
  plan: "Pro Annual",
  accountType: "Facebook",
});
```

Segment sends Track calls to Astrolabe as a `track` event.

## 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 Astrolabe  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   |
| ------- | ---------------------- | -------- | ------ |
| API Key | Your Astrolabe API key | Yes      | string |