Lytics Projects in Contentstack

Lytics is set up in Contentstack as a Lytics project, which replaces the Data Activation Layer.

Lytics is set up in Contentstack as a Lytics project. Projects replace the Data Activation Layer (DAL), which is deprecated.

A project is the top-level container for one customer data initiative. It is the same thing the Lytics app calls an account — you will see both names depending on which surface you are working in. Creating a project provisions the account at app.lytics.com, generates a JavaScript tag snippet, and opens a default data stream ready to receive events.

Lytics Projects in Contentstack is where you:

  • Install the Lytics JavaScript tag. On Contentstack Launch, connect the Launch project and Launch deploys the tag for you. Otherwise copy the snippet from Install Lytics on the project dashboard and paste it as the first element in <head>. Installing it manually or through a tag manager — to fit it around your consent setup — works too; the same snippet is in Lytics under Data Pipeline → SDK → Web (JS).
  • Connect Lytics to a CMS stack, Launch project, or Personalize project. The Personalize connection is what makes Lytics audiences available for variant targeting and experiments — no manual export job required.
  • Invite users and manage their access to Lytics. Collaborators and roles are scoped per project: organization membership alone does not grant access, and a role on one project does not carry over to another.

Setting up a project

Projects are created and managed in Contentstack, so the setup guides sit with the rest of the platform documentation:

Once events are flowing, the rest of these docs cover what you do in the Lytics app: the Contentstack integration for syncing stack entries into Lytics, plus audiences and experiences.


Did this page help you?