Astrolabe Destination

1. Log in to your Astrolabe workspace.
2. Navigate to the Connectors page 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.

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.

Astrolabe supports the following methods, as specified in the Segment Spec.

If you aren't familiar with the Segment Spec, take a look at the Identify method documentation to learn about what it does. An example call would look like:

1
analytics.identify("userId123", {
2
  email: "john.doe@example.com",
3
});

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.

If you aren't familiar with the Segment Spec, take a look at the Group method documentation to learn about what it does. An example call would look like:

1
analytics.group("0e8c78ea9d97a7b8185e8632", {
2
  name: "Initech",
3
  industry: "Technology",
4
  employees: 329,
5
  plan: "enterprise",
6
  "total billed": 830,
7
});

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.

If you aren't familiar with the Segment Spec, take a look at the Track method documentation to learn about what it does. An example call would look like:

1
analytics.track("User Registered", {
2
  plan: "Pro Annual",
3
  accountType: "Facebook",
4
});

Segment sends Track calls to Astrolabe as a track event.

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.

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