An executive guide to Adobe CJA: How to build a strategy that scales in five steps

Collecting every button-click is not a strategy. While Adobe Customer Journey Analytics (CJA) promises a unified view of the customer, many organizations end up with a mountain of data but no clear business value. At TELUS Digital, we know that true CX transformation requires moving beyond the “track everything” mindset to a scalable strategy that connects customer data across channels to business outcomes.

In this five-step guide, we’ll demonstrate how to build a foundation for improved reporting and fueling personalization, decision-making and customer experience at scale.

Step one: Discover KPIs and define success

Each department in an organization influences which data matters. A marketer may want to track how many users complete a booking funnel after clicking on a promotion, while operations might care more about identifying peak product demand to plan inventory.

The critical question to uncover the most strategic KPI is: If we can get more users to do this one thing, will it increase sales or improve product success? That one thing becomes the North Star metric.

Supporting measures — page views, engagement rates or seasonality trends — are ancillary metrics that provide context but don’t drive the strategy on their own.

There are two effective ways to surface the North Star metric:

• Workshops: Facilitate collaborative discussions that help distill priorities by asking questions like:
  • Why are we building this website or app?
  • What do users want from their experience?
  • What are our overall business objectives?
• Stakeholder surveys: Collect input via structured questionnaires, then synthesize the responses to uncover themes and align on the most strategic KPIs.

Once KPIs are agreed upon, document them alongside ancillary metrics. This distillation becomes the skeleton of your analytics strategy, ensuring clarity before moving into technical execution.

Step two: Visualize the data flow

With a defined North Star, the next step is creating a blueprint of touchpoints, events and attributes. Unlike Google Analytics 4 (GA4), which comes pre-packaged with events like “page views” and “user count,” CJA requires intentional design.

Consider three levels of attributes:

1. Global properties: Context metrics collected on every event (e.g., page name, URL, previous page).
2. Event actions: User interactions such as button clicks, form submissions or video plays.
3. Page-specific attributes: Custom fields requested by stakeholders to answer specific business questions.

By mapping these attributes into a visual journey, stakeholders gain a clear view of what will be collected and why. This avoids ambiguity and ensures non-technical audiences stay engaged before schemas and Adobe Experience Platform (AEP) configurations enter the conversation.

Step 3: Design the XDM schema

Once the visual blueprint is in place, it’s time to translate it into a structured Experience Data Model (XDM) schema within AEP. This schema becomes the backbone of your implementation.

Best practices include:

• Standardized naming conventions for events and attributes (e.g., buttonClick, pageView).
• Consistent event design, ensuring data looks and behaves uniformly across the schema.
• Event-based architecture to maintain flexibility and extensibility.
• Scalability, so data can be reused across Adobe tools such as CJA, Adobe Journey Optimizer (AJO) and Adobe Target.

A well-structured schema supports analytics today and future-proofs your customer journey strategy for tomorrow.

Step 4: Execute implementation with documentation

The schema becomes actionable only when paired with clear technical documentation, such as technical specifications or Solutions Design Reference (SDR), which should include:

• Event collection rules
• Field mappings to XDM attributes
• Governance guidelines for data quality and consistency

Detailed documentation ensures stakeholders understand how data is captured, enables developers to implement with confidence and provides a reference point for ongoing maintenance.

Step 5: Take an aggregate approach for broader impact

Finally, the true power of CJA comes from treating analytics as a shared foundation, not a siloed tool. One of its greatest strengths is the ability to bring in data from multiple sources and make it usable across Adobe’s ecosystem.

Using an aggregate approach — for example, naming all buttons buttonClick and attaching attributes like buttonText or buttonLink — simplifies implementation and improves scalability. Teams using AJO and Adobe Target no longer need to hunt for specific names, reducing friction and speeding up execution. New features can also be supported with less dev work by reusing general naming conventions.

Because XDM schemas cannot be changed once in production, designing them with reuse in mind is critical. This foresight ensures that teams across the enterprise can leverage the same data for personalization, testing and journey orchestration.

This aggregate approach reduces duplication, accelerates personalization and ensures a unified view of the customer journey across teams.

From reporting to activation and beyond

While Adobe CJA is often marketed as an insights tool, it also powers activation, personalization and customer experience at scale. However, success depends on strategy. By shifting from siloed reporting to an aggregate approach, CJA becomes a primary growth driver rather than just technical overhead.

To truly steer your organization in the right direction, consider a partner who can translate complex data flows into seamless customer experiences. Let’s move beyond the dashboard and start building journeys that matter — reach out to one of our experts today. You can also find us at Adobe Summit 2026, where we’ll be presenting live demos with the latest Adobe solutions and AI tooling.