Understanding Lytics / Product Documentation / Data Onboarding and Management

Custom Data Sources

Lytics can onboard and process data from custom data sources helping to further build out user profiles with data specific to your company. This data is often the most valuable for building user profiles meaningful for your marketing efforts. Custom data grants the ability to personalize web experiences and build audiences using data unique to you and your users.

Onboarding process

Unlike data collected from web activity and integrated marketing tools which automatically map data to Lytics user fields, custom data sources requires an evaluation, planning, and implementation process. During this process our customer engineering (CE) team will assist in identifying use cases and the data fields needed to achieve them. Our CE team will then produce a data dictionary that describes the structure, format, location and relationship of your data. The data dictionary is used to write Lytics Query Language (LQL) queries which map custom data fields to Lytics user fields as it is ingested. Finally your custom data is uploaded to the Lytics and made available for use to build audiences, personalize web experiences, or export to marketing tools.

Uploading custom data

Data can be uploaded to Lytics via CSV and JSON sFTP upload or our data upload API. Lytics can ingest both large, bulk uploads of user data and smaller, realtime uploads of event data. Before uploading data to Lytics ensure all necessary LQL queries are in place or it will not be mapped to to Lytics user fields, preventing identity resolution. When considering large uploads to the Lytics platform, be aware that this may cause an event backlog on your account. This occurs as our platform queues incoming information as it processes the content of the upload. Processing begins when the upload completes and can last considerably longer than the initial upload. This can result in a delay in seeing information from other sources in your account as well as delays in any outbound, trigger-based workflows.