Learn how to configure Vitally to send data back to Segment for distribution to your other destinations.
This article is about pushing Vitally's data back to Segment. If you are instead wanting to import your Segment data into Vitally, you'll want to head here.

How data gets pushed to Segment

Vitally pushes data to Segment via the group API. Each time we detect that an account should be pushed to Segment (using the logic detailed here), we'll send a group call for every user in the account. We will not send identify calls for those Users, just groups associating their id with the Customer's groupId and the traits defined here.

Setting up Vitally as a Segment source

Create a new source in Segment

So that you can isolate the data sent from Vitally from your other sources, we recommend creating a new source for Vitally in Segment using the HTTP API template. That way, you can decide which destinations you want to receive data from Vitally.

Add the write key to your Segment config

After creating the new source in Segment, enable sending group calls in your Segment integration settings and add the write key for the Vitally source.
To access the Segment integration in Vitally, navigate to Integrations -> Segment in your Account Settings (or get there via Quick Jump).
Once you've added your API write key, then back in Segment, just connect the Vitally source to a new destination to get your data flowing!

Define your group traits

Once you've setup Vitally as a Segment source, you then just need to define which Vitally account fields you want to send back to Segment as group traits. Back in the Segment integration configuration page in Vitally, define a mapping of Vitally account fields to named group traits. For each mapping defined, we'll add a new trait to the data we push back to Segment.


Q: Does Vitally's Segment integration work in "device" or "cloud" mode?
A: We are a Segment destination, there should be no impact to your app if you already have Segment integrated to your app. To clarify further, we’re a “cloud” destination, so Segment does not load any of our code.