CreateBlogSupport
Log inSign up
Home
Webex Contact Center
  • Overview
  • Guides
  • API REFERENCE
  • AI
  • Configuration
  • Data
  • Desktop
  • Journey
  • Media And Routing
  • Changelog
  • SDK
  • Customer Journey Data Service
  • AI Assistant for Developers
  • Webhooks
  • Contact Center Sandbox
  • Using Webhooks
  • Beta Program
  • Webex Status API
  • Contact Center Service Apps
  • FAQs

Webex Contact Center

Getting Started with CJDS

Cisco Journey Data Service (CJDS) is a journey management service that helps organizations turn raw customer data into real-time insights and actions. It enables businesses to unify identity, track intent signals, and drive smarter, more personalized interactions through Webex Contact Center.

anchorCJDS Overview

anchor

Cisco Journey Data Service is an API-driven service designed to empower organizations to harness customer data and transform it into actionable insights. By leveraging CJDS, companies can seamlessly integrate, analyze, and act on diverse data sources to optimize customer interactions. The service is built on four core capabilities:

  1. Listen: Ingest data from any source, whether internal systems or third-party applications, to gather insights from disparate data streams. This capability allows CJDS to continuously monitor customer interactions and behaviors across all channels.
  2. Identify: Build dynamic customer profiles by capturing critical propensity drivers, such as preferred communication channels, languages, and behavioral patterns. This step ensures a unified view of each customer, enabling better personalization.
  3. Analyze: Utilize powerful aggregation techniques to process collected data, transforming it into meaningful insights. These insights can uncover patterns, trends, and opportunities for enhancing customer engagement.
  4. Act: Leverage CJDS insights to optimize customer journeys in real-time. By integrating with the Webex Contact Center's flow control and orchestration capabilities, CJDS can intelligently route interactions based on customer profiles. Additionally, these insights are surfaced to agents through the Agent Desktop, providing real-time contextual data to enhance customer support.

anchorKey Capabilities Breakdown

anchor

The four foundational pillars of CJDS translate into specific API functionalities:

  1. Data Ingestion: Use Listening APIs to capture data from various sources, enabling continuous monitoring and enrichment of customer profiles.
  2. Customer Identification: Leverage the Create a Person API and Merge API to build and maintain dynamic customer profiles, consolidating data across different channels and interactions.
  3. Profile Creation & Insights: Utilize the Profile Template APIs to transform raw data into actionable insights, ensuring a robust understanding of customer behaviors and preferences.
  4. Trigger Actions: Implement the Action APIs to trigger automated workflows using business rules, enhancing customer experience and optimizing contact center operations.

anchorKey Onboarding Collateral

anchor
  • CJDS Overview Vidcast
  • Customer Journey Widget Overview
  • Journey - Getting Started
  • Journey - API documentation
  • API Deep Dive Webinar
  • How to integrate journey widget with your agent desktop?
  • Use Case Vidcast (Personalized Customer Experience)
  • Use Case Vidcast (Digital Channels & Webpage Use Case)

anchorProvisioning CJDS for Your Organization

anchor

Follow these steps based on when your Webex Contact Center Org was created:

  • If your org was created before Feb 28, 2025 → No action needed. CJDS is automatically linked to your Org ID.

  • If you’re already using CJDS with a custom layout → No changes required. Your existing setup is supported.

  • If your org was created after March 1, 2025 → Complete this form to request CJDS provisioning. A journey tenant will be created within 72 hours.

anchorTechnical Details

anchor
Authentication for CJDS APIs
  • CJDS uses Bearer Auth for all APIs. You will need to use CI generated Bearer Token in the 'Authorization' header.
  • Prefix token with 'Bearer'. Please look at the Authentication section on how to generate bearer token. You can also get the Bearer token from https://developer.webex.com login with your admin credentials.
  • It requires a full administrator role, CJDS appropriate cjp:config_read or cjp:config_write scopes.
CJDS Schema

CJDS Event Data Schema Details

AttributeTypeDescriptionConstraintsExamples
specversionStringThe version of the CloudEvents specification which the event uses. This enables the interpretation of the context. Compliant event producers MUST use a value of 1.0 when referring to this version of the specificationREQUIRED, MUST be a non-empty string1.0
typeStringThis attribute contains a value describing the type of event related to the originating occurrence.REQUIRED, MUST be a non-empty string, SHOULD be prefixed with a reverse-DNS name. The prefixed domain dictates the organization which defines the semantics of this event type.com.github.pull_request.opened, com.example.object.deleted.v2
sourceURI-referenceIdentifies the context in which an event happened. Often this will include information such as the type of the event source, the organization publishing the event or the process that produced the event. The exact syntax and semantics behind the data encoded in the URI is defined by the event producer. Producers MUST ensure that source + id is unique for each distinct event.REQUIRED, MUST be a non-empty URI-reference, An absolute URI is RECOMMENDEDhttps://github.com/cloudevents, mailto:cncf-wg-serverless@lists.cncf.io, urn:uuid:6e8bc430-9c3a-11d9-9669-0800200c9a66, /cloudevents/spec/pull/123, /sensors/tn-1234567/alerts, 1-555-123-4567
idStringIdentifies the event. Producers MUST ensure that source + id is unique for each distinct eventREQUIRED, MUST be a non-empty string, MUST be unique within the scope of the producer1eb65fdf-9643-417f-9974-ad72cae0e10f
timeTimestampTimestamp of when the occurrence happened.OPTIONAL, If present, MUST be a ISO Timestamp2018-04-05T17:31:00Z
identityStringThis describes the identifier to whom the event is produced.REQUIRED, MUST be non-emptyram@cisco.com
identitytypeStringThis specifies the type of identifier. It is an Enum. Currently, we support only email, phone and customerId.REQUIRED, MUST be a non-empty stringemail
previousidentityStringThe identity with whom we want to merge the new person's eventsOPTIONAL, If present, MUST be non-emptyram@cisco.com
datacontenttypeStringContent type of data value.REQUIRED, If present, MUST adhere to the format specified in RFC 2046application/json
dataBased on the datacontenttypeThe event payload. This specification does not place any restriction on the type of this information. It is encoded into a media format which is specified by the datacontenttype attribute (e.g. application/json), and adheres to the dataschema format when those respective attributes are present.REQUIRED{"taskId": "888b688e-b74e-4fa6-8260-1e8bd0a3523a","origin": "ram@cisco.com","destination": "1234567890","direction": "INBOUND","channelType": "email","outboundType": null,"queueId": "AXZvA7uJ1OI4n5klHgJA","createdTime": 160266966391}

Sample CJDS Event Data

{
  "specversion": "1.0",
  "type": "task:new",
  "source": "wxcc",
  "id": "1eb65fdf-9643-417f-9974-ad72cae0e10f",
  "time": "2022-03-14T01:48:45Z",
  "identity": "ram@cisco.com",
  "identitytype": "email",
  "previousidentity": "ramnat@cisco.com",
  "datacontenttype": "application/json",
  "data": {
    "agentId": "109332be-7fc4-4d4d-9488-ebdb8e13b9bbe",
    "destination": "+12147651210",
    "profileType": "BLENDED",
    "currentState": "idle",
    "idleCodeId": "AXUr0jX9H5TuplmIxiC",
    "createdTime": "1645819554383"
  }
}

anchorDay 0 Operations

anchor

To use CJDS for your organization, you must:

  • Create a journey project.
  • Activate the Webex Contact Center connector.
  • Add user identities to a journey project.
  • Enable customer journey widget on an agent desktop.
Create a Journey Project

Journey projects help organizations manage multiple data sources. Each journey project has a unique identifier which is required to leverage CJDS APIs payloads. Note that project IDs in Control Hub are referred to as workspace IDs in APIs.

  1. Sign in to Control Hub and go to Customer Journey Data > Journey projects.
  2. Click Create a journey project.
  3. Enter a name and a description for the journey project.
Activate Webex Contact Center Connector

After you create a journey project, you must activate the Webex Contact Center connector. This connector allows the journey project to capture all customer events and send it to CJDS from Contact Center. Once the connector is activated in one project, it cannot be activated in another. At any point in time, it can be enabled for only one project.

  1. Sign in to Control Hub and go to Customer Journey Data > Journey projects.
  2. Select a journey project.
  3. Toggle the Activate connector in the Webex Contact Center section to on.

Add Customer Identities to a Journey Project:

There are two ways to add your identity today.

1. CSV Upload

Adding customer identities to JDS will help you connect multiple customer identifiers (phone number, email address, Customer ID) to a single customer identity. You can upload a CSV file with multiple user identities. The requirements for the CSV file are the following:

  • Required headers:
    • Id
    • First Name
    • Last Name
    • Email Addresses
    • Phone Numbers
    • Customers Ids
  • Each customer identity can have up to five email addresses, phone numbers, and customer IDs, separated by a | (pipe) symbol.
  • Each customer identity must have at least an email address, phone number, or customer ID or else the CSV file will return an error.
  • For the Id column, make sure to leave each row empty. When you upload the CSV file, this field will auto-generate.

Once you create a CSV file, you can upload that file to a journey project that you created.

  1. Sign in to Control Hub and go to Customer Journey Data > Journey projects.
  2. Select a journey project that you want to create user identities for.
  3. Select Identities.
  4. Click Create an identity.
  5. Upload a CSV file that you created for customer identities, and then click Next.
  6. If the CSV file is valid, a window appears to show you if the import was successful. Once you're done, select Close. You should see a list of all the uploaded customer identities.

2. Real-Time Identity Creation via Flow

Use the Create Person API in Flow Designer to sync real-time identity data

Example:

  • A caller enters the IVR

  • You fetch customer details from CRM

  • Use HTTP Node (for contact center flow) or dedicated Journey Node (Connect flow) to call CJDS API and create/update identity profile on the fly

This keeps CJDS aligned with your system of record.

Enable the Customer Journey Widget

The Journey Widget provides agents with a unified view of a customer’s real-time and historical interactions across all integrated systems.

To activate - Follow this guide to embed it into the Webex Agent Desktop layout.

In This Article
  • CJDS Overview
  • Key Capabilities Breakdown
  • Key Onboarding Collateral
  • Provisioning CJDS for Your Organization
  • Technical Details
  • Day 0 Operations

Connect

Support

Developer Community

Developer Events

Contact Sales

Handy Links

Webex Ambassadors

Webex App Hub

Resources

Open Source Bot Starter Kits

Download Webex

DevNet Learning Labs

Terms of Service

Privacy Policy

Cookie Policy

Trademarks

© 2025 Cisco and/or its affiliates. All rights reserved.