Source record · tier 2 current vendor documentation
Customer Journey Data
- Publisher
- Cisco Webex Connect documentation
- URL
- https://help.webexconnect.io/docs/customer-journey-data
- Published
- unknown
- Updated
- unknown
- Accessed
- 2026-09-30
- HTTP status
- 200
- License
- Cisco proprietary; all rights reserved; no-redistribution; short excerpts and locators only
Source notes citing this source
- The Webex Connect Customer Journey Data node is available only to Flex 3 Webex Contact Center customers. in context
- The Webex Connect Customer Journey Data node offers five methods: Manage Identity, Write to CJDS, Get Identity By Aliases, Read from Progressive Profile and Read from CJDS. in context
- The Webex Connect Customer Journey Data node authorises with the standard OAuth 2.0 authorization code grant flow. in context
- Using the Webex Connect Customer Journey Data node requires a Webex account backed by Cisco Webex Common Identity with the Contact Center Administrator role in Control Hub, a client ID and client secret pair obtained by request, and a valid authorization configured under Assets > Integrations > Pre-built Integrations. in context
- Webex Connect documentation recommends the Customer Journey Data prebuilt node v2.1.2 and says the older v1.0 node will be deprecated in a future release. in context
- Webex Connect documentation presents Read from Progressive Profile as a way to retrieve a customer's journey profile in real time for use in routing decisions. in context
- The Read from Progressive Profile method of the Webex Connect node takes a Workspace/Project, a Template Name and an Alias ID (phone, email, social ID, customer ID or temporary ID) as inputs. in context
- The Read from CJDS method of the Webex Connect node takes a Workspace/Project, an identity and a filter query, with type, queueId and pageSize given as example query parameters. in context
- In the Webex Connect node, a successful Write to CJDS or Manage Identity call is reported with HTTP 202, while successful Get Identity By Aliases, Read from Progressive Profile and Read from CJDS calls are reported with HTTP 200. in context
- The Write to CJDS method of the Webex Connect node accepts the identity types email, phone, customerId, socialId and temporaryId. in context
- The terms 'project' (or 'journey project') and 'workspace' in Cisco's CJDS material appear to refer to the same scoping object within an organisation. inferred in context
Cite this source record
APA
WarmTransfer. (2026, September 30). Customer Journey Data. WarmTransfer. https://warmtransfer.net/knowledge/sources/webexconnect-docs-customer-journey-data
BibTeX
@misc{warmtransfer-webexconnect-docs-customer-journey-data,
title = {Customer Journey Data},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/webexconnect-docs-customer-journey-data},
note = {Cisco Webex Connect documentation, accessed 2026-09-30}
}