Lytics
Step-by-step guide to send your event data from RudderStack to Lytics.
Last updated
Was this helpful?
Step-by-step guide to send your event data from RudderStack to Lytics.
Last updated
Was this helpful?
Lytics is a popular customer data platform built for marketers. It allows you to efficiently leverage your first-party customer data to deliver tailored customer journeys.
RudderStack supports Lytics as a destination to which you can seamlessly send your event data.
Find the open-source transformer code for this destination in the GitHub repository.
Before configuring Lytics as a destination in RudderStack, verify if the source platform is supported by Lytics, by referring to the table below:
Connection Mode
Web
Mobile
Server
Device mode
Supported
-
-
Cloud mode
Supported
Supported
Supported
To know more about the difference between cloud mode and device mode in RudderStack, refer to the RudderStack Connection Modes guide.
Once you have confirmed that the source platform supports sending events to Lytics, follow these steps:
From your RudderStack dashboard, add the source. Then, from the list of destinations, select Lytics.
Assign a name to your destination and click on Next.
To successfully configure Lytics as a destination, you need to configure the following settings:
API Token: Create an API token in your Lytics dashboard and enter the details here.
To get the API token, go to your Lytics dashboard and navigate to Account > Account Settings > API Token. You can create an API token here and use this information to configure Lytics as a destination.
Stream Name: Enter the name of the Lytics stream where you want to send the events.
Client-side Event Filtering: This setting is applicable only if you are sending events to Lytics via the device mode.
Refer to the Client-side Event Filtering guide for more information on this setting.
If you are using the JavaScript SDK to send the events to Lytics, enter the following settings:
Account ID: Enter the the Lytics account ID obtained from your Lytics dashboard. For more information on obtaining the account ID, refer to the Lytics support page. This is a mandatory field.
Allow UID Sharing Across Multiple Domains: When enabled, this option lets you identify users across domains.
Ensure Entity: When this option is enabled, RudderStack gets your most updated audience membership and profile data, before sending it to Lytics.
Use native SDK to send events: Enable this setting if you are sending events via the device mode, that is, via the native web SDK.
The identify
call captures the relevant details about the visiting user.
For more information on the identify
method, refer to the RudderStack API Specification guide.
A sample identify
payload is as shown in the snippet below:
With the page
method, RudderStack makes a call to Lytics to record a page view.
For more information on the page
method, refer to the RudderStack API Specification guide.
A sample page
call is as shown:
Similarly, you can also make screen
calls. However, this is supported only in the cloud mode.
A sample screen call is as shown:
With the track
API, RudderStack makes a call to Lytics to track user actions and their associated properties.
For more information on the track
method, refer to the RudderStack API Specification guide.
A sample track
call is as shown:
Go to your Lytics dashboard, and navigate to Account > Account Settings > API Token. You can create an API token here, which can be used to configure the destination on the RudderStack dashboard.
For more information, refer to the Lytics documentation.
To obtain your Lytics account ID, follow these steps:
Log into your Lytics dashboard.
Click on the account name on the top right and go to Manage Accounts.
Here, you will see the account ID associated with your Lytics account.
For more information, refer to this Lytics support page.
For queries on any of the sections covered in this guide, you can contact us or start a conversation in our Slack community.