Lytics Destination

Segment makes it easy to send your data to Lytics (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Lytics in the format they understand. Learn more about how to use Lytics with Segment.

Getting Started

  1. Lytics uses our Javascript library so make sure to go through our quickstart guide to get setup on that first.

2) Once you’re recording data enable Lytics on your destination page using your Customer ID number, which can be found in the admin section of your Lytics account: Account -> Manage Accounts.


You can also enter your Data API Key under Advanced Options. The data API Key can send data to Lytics, but not edit your account info. The Full API Key has access to edit all of your account info, so it should not be used for sending data.


Paste into your Destination page:



You can see what data fields Lytics pulls in by default. However, if you would like to pull in any custom data, you can test it here. This is generally not necessary when using Segment.


You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Supported Sources and Connection Modes

📱 Device-mode
☁️ Cloud-mode

To learn more about about Connection Modes and what dictates which we support, see here.

We offer optional Cloud-mode connections for Web data with Lytics. As a reminder, this removes the Lytics javascript library from your site, which might improving performance. However, there are a few differences between the Cloud- and Device-mode to keep in mind before enabling it in the Segment app. When you enable Cloud-mode here’s what happens:

  • 6/3/2019 -> update to reflect unbundling IS available


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.


Your API key should be a series of numbers and letters, like 3daDLlqb4ANg7l0rf4cfl6xF. This is only required if you are using the Lytics server side integration.

Ensure Entity

If true, ensures entity returned from Lytics personalization api reflects all events from current page view.


Your CID should be a series of numbers, like 9289.

Allow UID Sharing Across Multiple Domains

If true, allows for the Lytics _uid to load the same across multiple domains.


A brief, but informative name for organizating your data in Lytics. Only necessary when you are tracking multiple websites.

Adding Lytics to the integrations object

To add Lytics to the integrations JSON object (for example, to filter data from a specific source), use one of the 1 valid names for this integration:
  • Lytics

  • Questions? Need help? Contact us!
    Can we improve this doc?
    Email us:!