jahia-dev-jexperience

To set up jExperience analytics locally, configure the Docker Compose stack to orchestrate Jahia, jCustomer, Elasticsearch, and Kibana, then provision the required modules to enable end-to-end visitor event capture.

jExperience captures visitor events using client components that emit structured data via the wem API, specifically the window.wem object, sending interaction records to jCustomer for indexing and subsequent visualization in Kibana dashboards.

Yes, Docker is required for the local development stack. You need Docker-based orchestration to provision and run Jahia, jCustomer, Elasticsearch, and Kibana together before validating visitor events in analytics dashboards.

Yes, you can package and deploy Kibana dashboards directly from your Jahia module. This approach provisions ready-to-use insights on site activity, allowing you to validate captured visitor events without manual dashboard configuration.

The best way to validate jCustomer events is to enable jExperience on your Jahia site, trigger client interactions, and monitor the incoming source and target data directly within the provisioned Kibana dashboards.

If jExperience events are missing in Kibana, verify that your Docker Compose services are running, jExperience is enabled on the site, and your client components correctly emit structured events via the window.wem API to jCustomer.