Lytics FAQs
Lytics FAQs
The Lytics App is the Contentstack's dedicated interface for the Lytics customer data platform (CDP). It centralizes management for project creation, JStag installation, collaborator access, product connections, and a live dashboard. Note that audience authoring and profile inspection are performed separately on the Lytics platform at app.lytics.io.
If you cannot see the Lytics App in your Contentstack organization, Lytics is not enabled on your plan. Contact your Contentstack support to discuss access.
You must be signed in as an Organization Owner, Organization Admin, or a user who has been granted project-creation permission. Users without this permission see a Limited Access screen instead of the projects list.
Your organization has reached its project quota. Contact your Contentstack account team to discuss increasing the limit.
Paste it as the first item inside the <head> of every web page you want to track. It must be in <head>, not <body>.
Confirm the snippet is in <head> and not <body>, the page is live and loading in a normal browser session (not incognito), and your front end is not using a non-default Lytics stream. If it is using a non-default stream, the verification check will keep reporting Not installed even when data is flowing correctly.
Within a few minutes of verification succeeding, the Event Activity chart begins populating and event, profile, and audience counts start climbing.
No. Connecting a Launch project via Project Connections manages JStag automatically. Manual installation is only needed for non-Launch front ends.
A project is the top-level container for one customer data initiative inside the Lytics App. It holds connections, collaborators, and a Lytics account ID that ties it to the corresponding Lytics platform account.
They are the same thing. The Lytics App (inside Contentstack) uses "project" to align with Contentstack's naming conventions. When you open app.lytics.io via Go To App, the same entity is referred to as an "account."
Yes. A single project can connect to multiple CMS stacks, Launch projects, and Personalize projects simultaneously.
Three connection types are supported. A CMS Stack connection links a CMS stack that publishes content for audiences built in the project. A Launch Project connection links a Launch project where JStag runs and collects visitor behavior. A Personalize Project connection links a Personalize project so Lytics audiences become available for variant targeting and experiments.
Disconnecting a product may have side effects on how data flows between your products. Review the impact before removing a connection.
No. Organization membership does not grant access to any Lytics project. A user must be explicitly invited as a collaborator on each project they need to access.
Roles are assigned per project. The same user can be an Admin on one project and an Observer on another.
Organization Owners and Organization Admins have full access to every Lytics project in the organization, regardless of project-level role assignment.
The user who creates a project is automatically its owner and always retains full access, regardless of other role assignments.
Three live counts pulled from the Lytics platform: total events collected across all streams, number of audiences defined on the project, and number of customer profiles built so far. It also shows an Event Activity chart and a Go To App button for single sign-on into app.lytics.io.
It opens the Lytics platform at app.lytics.io via single sign-on. This is where audience authoring, profile inspection, stream configuration, and data activation happen.
Recheck the Install Lytics modal verification step, confirm the deployed page loads the snippet by viewing the page source, and open the Lytics platform via Go To App to inspect raw stream activity directly.