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.

cid

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.

api

Paste into your Destination page:

key

Features

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.


Supported Sources and Connection Modes

WebMobileServer
📱 Device-based✅
☁️ Cloud-based✅✅

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

Settings

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

Allow UID Sharing Across Multiple Domains

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

Ensure Entity

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

API Key

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.

CID

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

Stream

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


If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!