Understanding Your Lytics Project Setup

This guide covers the setup and access components of a Lytics project, the pieces you configure to get data flowing. 

Lytics is not a single feature, it is a chain of components working in a fixed sequence. Each one unlocks the next. A project generates the JStag snippet. JStag fills the project with data. Connections route that data to your other Contentstack products. Collaborators and roles control who can manage any of it. Remove one component from the chain and the flow stops at that point. This guide explains each dependency so you know what to set up, in what order, and why it matters.

For definitions of each term, see Key Concepts.

Click to enlarge

A project is the entry point for Lytics. When a project is created, three things happen automatically, a corresponding Lytics account is created on app.lytics.com, a unique JStag snippet is generated for the project, and a default data stream is created ready to receive events.

Nothing else in Lytics can be configured or generated without a project in place. Until a project exists, there is no snippet to install, no stream to receive events, and no data to monitor.

A JStag is the data input layer for the project. It sends visitor events from your website into the project's default stream. The Lytics platform processes those events and builds customer profiles from the accumulated behavioral data. Those profiles are the raw material that connections and audiences depend on downstream.

Without JStag, the project exists but contains no data, no events, no profiles, and no audiences.

A Connection define the data pathways between the Lytics project and other Contentstack products. Without a connection, data collected by JStag remains inside the Lytics platform and does not reach any other product.

The Launch connection has a direct relationship with JStag, when a Launch project is connected, Launch manages JStag automatically and the manual installation step is not required. The Personalize connection is the bridge between data collection and content targeting, without it, audiences built on app.lytics.com exist in Lytics but are not available for variant targeting or experiments in Personalize.

If no connections are configured, JStag continues collecting data into the Lytics platform but that data does not flow into any other Contentstack product.

Collaborators and roles govern access to the project and run parallel to the entire component chain. Collaborators are the users who manage the project. Roles define what each collaborator is permitted to do.

Both collaborators and roles are scoped to the project. A user's access to one project does not extend to any other project in the organization. A collaborator without a role has no meaningful access regardless of their Contentstack organization membership.

The five components follow a fixed sequence of dependencies:

1. The project must exist before any other component can be created or configured.
2. JStag must be installed or a Launch connection must be in place before any data enters the project.
3. Connections must be configured before data can reach other Contentstack products.
4. Collaborators must be invited and roles assigned before anyone other than the project owner can interact with any of the above.

As each component is configured, the Lytics project overview screen reflects the current state event counts climb once JStag is running, and audience counts appear once audiences are built on app.lytics.com.