Skip to main content

Journeys - API Documentation

Enterprise

This feature is part of Countly Enterprise. To get access, contact sales or compare versions. Existing customers can reach the support portal with questions.

Overview

Journey Engine lets you build automated journeys that react to user events, profile changes, and engagement actions. A journey definition can have multiple versions, with a single active version at a time. Journeys create instances per user, track block execution, and compute performance metrics.

Configuration & Settings

The feature uses config stored in the plugins document:

  • journey_engine.cooldown (hours, default: 24)
    • Used to throttle content delivery between journeys
    • If missing, the setting is migrated from content.cooldown

Journeys

Versions

Stats

Logs & Instances

Utilities

Permissions & Access

Most endpoints require the journey_engine feature permission. Some endpoints are restricted to global admins (see endpoint docs).

  • Content: Journey blocks can trigger content delivery
  • Drill: Journey filters and events use Drill data
  • Surveys: Survey events can advance journeys
Implementation details

Database Collections

CollectionPurpose
countly.journey_definitionStores journey definitions (name, status, app, creator)
countly.journey_versionsStores journey versions and block graphs
countly.journey_instancesStores per-user journey execution instances
countly.journey_logsStores journey instance status logs
countly.journey_block_logsStores per-block execution logs
countly.journey_statsStores aggregated journey performance stats (daily)
countly.eventsStores app event metadata (created via journey event API)
countly_drill.drill_metaStores drill event metadata for custom events
countly.membersJourney creator lookups
countly.appsApp metadata for journey lookups
countly.app_users{appId}User profiles for instance lookups
countly.pluginsStores plugin config (including journey_engine.cooldown migration data)