SegMetrics Destination

1. Go to your Integrations tab in SegMetrics, and click Connect for the Segment Integration.
2. Go to your Account Settings and copy your SegMetrics Account Id and API Key.
3. From the Destinations catalog page in the Segment App, click Add Destination.
4. Search for "SegMetrics" in the Destinations Catalog and select the SegMetrics Destination.
5. Enter the Account Key and API Key in the SegMetrics destination settings in Segment.

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

analytics.page()

Segment sends page calls to SegMetrics as view events, which are available in the analytics dashboard as a click event.

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 SegMetrics as view events, which are available in the analytics dashboard as a click event.

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 SegMetrics as identify events.

An email address is required by SegMetrics to connect a contact to your existing contacts in your CRM.

When you identify a new contact, the user's visitor tracking is connected to contacts in your CRM that share the same email address.

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.