Skip to main content
Jio Commerce Platform

JCP UCP

Give customer journeys a shared foundation.

Connect customer identity and profiles across storefronts with identity resolution, consent management and context for personalization.

Part of the JCP portfolioPlan
Illustrative customer journey

One foundation, several experiences

  1. Relate customer records
  2. Resolve the identity
  3. Apply consent boundaries
  4. Provide permitted context
The next stepA coherent customer experience foundation
Illustrative workflow
For the teams behind the work
  • Customer platform teams
  • Retail CRM and marketing leaders
  • Digital experience teams

Unified customer platform

Different storefronts should not require different understandings of the customer.

Retail groups often operate multiple customer experiences, each with its own account and interaction context. JCP UCP provides an identity and profile foundation across those experiences. Identity resolution, a cross-business profile graph and consent management support a more coherent view of the customer. The same foundation can inform supported sign-in and personalization workflows. The goal is to connect relevant context while preserving the boundaries that determine which information a business or experience is allowed to use.

Inside JCP UCP

What you can do.

01 / Capability

Unified customer identity

Establish a shared identity foundation for connected customer experiences. Identity resolution helps relate customer records, giving downstream workflows a more coherent reference than independent identifiers maintained separately by every storefront or business.

Explore your use case

A connected profile graph

Bring relevant customer context into a profile graph across participating businesses. This provides a foundation for understanding relationships between customer records and experiences, with the scope of connected information defined for the retail operation.

Consent and privacy management

Keep consent and privacy controls within the customer-data workflow. Customer context should be made available according to the permissions and purposes that apply, rather than assuming that a shared profile makes every use appropriate.

Sign-in and personalization context

Support connected sign-in experiences and provide customer context to personalization workflows. The product scope includes login across storefronts and a personalization feed; the experiences available depend on the participating storefronts and their configured connections.

The product in practice

How it works.

Follow the decisions and handoffs that bring JCP UCP into your operation.

  1. 01

    Relate the customer records

    Identify the customer sources and identity references used by participating experiences. Apply identity resolution within the agreed boundaries so the connected profile has a clear basis for relating records.

  2. 02

    Apply the permissions

    Carry consent and privacy requirements into how customer context is used. Define which business or experience can access the relevant profile information and for what purpose.

  3. 03

    Use the context in the journey

    Provide the permitted identity and profile context to supported sign-in, personalization or marketing workflows. Review the customer experience together with the data responsibilities behind it.

In your working day

Where it fits.

Start with the situation your team needs to address. Then map the capabilities and connections around it.

Connected storefront sign-in

Use a shared identity foundation when designing sign-in across participating storefronts. Keep the experience consistent with account relationships and the permissions governing the connected businesses.

Customer-aware personalization

Provide permitted profile context to personalization workflows so a connected experience can draw on relevant customer understanding instead of starting from an isolated storefront record.

Consent-aware campaign audiences

Connect customer profiles with campaign planning while preserving activation permissions. Give CRM and marketing teams a foundation for audience work that includes the rules governing its use.

A little more detail

Your questions, answered.

Explore what JCP UCP could mean for your team.

Ask our team
What is the difference between an identity and a profile?

Identity establishes how customer records relate to the same person or account. A profile organizes the relevant context associated with that identity. UCP brings both into the foundation used by connected customer experiences.

Does a unified profile mean unrestricted sharing between brands?

No. Consent, privacy requirements and business permissions still govern access and use. The connected profile should support the permitted customer journey without treating every piece of context as available to every participating experience.

How does UCP relate to the AI Marketing Platform?

UCP supplies the customer identity and profile foundation. The AI Marketing Platform covers segmentation, campaigns, creative and orchestration. Their relationship should be defined through the customer context and activation permissions included in the implementation.

Your next step

Bring your workflow.
Let’s build from there.

Talk through JCP UCP, your existing systems and the scope that fits your business.

Talk to our team