[Postponed] I'm Chakravarthy Kalva, Sr Product Manager at Adobe. AMA about Campaign Orchestration in AJO. | Community
Skip to main content
C
Adobe Employee
ChakravarthyKalvaAdobe Employee
Adobe Employee
March 13, 2026

[Postponed] I'm Chakravarthy Kalva, Sr Product Manager at Adobe. AMA about Campaign Orchestration in AJO.

  • March 13, 2026
  • 4 replies
  • 490 views

Update:
Due to unforeseen constraints, this session is being postponed. We’ll share the new date soon and notify you once the updated AMA thread is live.

In the meantime, ​@ChakravarthyKalva will be addressing the questions that have already been submitted. We won’t be taking additional questions on this thread going forward.

Thank you for your understanding, and stay tuned for the updated session details!

 


Hi, I'm Chakravarthy Kalva. I’m excited to share that on March 27, I’m hosting an Ask Me Anything (AMA) all about Campaign Orchestration in Adobe Journey Optimizer (AJO). I can’t wait to connect with you all. 
 
A little about me: 

  • Job Title: Sr Product Manager
  • Location:  San Jose

  • Fun Fact:  Last year (2025) in Hawaii, I went snorkeling for the first time, even though I can’t swim. It was a big step in overcoming my fear of water, and I was pleasantly surprised to see sea turtles and colorful fishes in Hawaii’s crystal-clear waters, it was totally worth it.

  • What I'm passionate about:  My passion lies at the intersection of innovation and impact — not just what technology can do, but what it should do, and how we harness it to move people, organizations, and industries forward.
  • Ask me about:  Campaign Orchestration in AJO, building multi-step marketing workflows, audience segmentation strategies, omnichannel campaign design, the future of martech, what it's like to be a Senior PM at Adobe and yes, snorkeling with sea turtles when you can't swim.😊.

How to participate in the AMA: 

  • 📅Wednesday, March 25: The thread opens — start submitting your questions right here! 
  • 🗨Wednesday–Thursday: Drop in any questions you’d like me to cover. 
  • ⭐Friday March 27: I’ll be responding throughout the day to as many questions as possible. 

After Friday, the thread will be closed for new replies but will remain available as a resource. 📚

 
Stay in the Loop:  
Hit Subscribe on this thread, so you don’t miss any updates. 
 
I’m really looking forward to a great discussion. Let’s dive in and learn together! 🙌

    4 replies

    T
    tonytheboldest
    Level 1
    March 13, 2026

    Hi Chakravarthy! Thanks for doing this AMA.

    We are currently utilizing Orchestrated Campaigns and are very interested in the 'bridge' between Standard XDM Profiles and Relational Schemas.

    Could you share your product insights and best practices on the following:

    • Cross-Schema Joins: What is the officially recommended canvas pattern for intersecting a Standard Profile audience (via the Read Audience activity) with a Relational dataset (via the Build Audience activity) using the Combine node?
    • Target Dimension Mapping: Are there any strict rules, hidden caveats, or best practices regarding Target Dimension entity mapping to ensure the SQL engine compiles these hybrid joins successfully?
    • Debugging the Bridge: When joining these two different schema types, debugging can be difficult if the intersection unexpectedly drops to 0. Are there any roadmap plans to allow us to preview interim data between nodes to help validate the data flowing across this bridge?
    • Multi-Step Workflows & Terminal Nodes: We recently saw a demo showing seamless multi-step workflows (e.g., Email -> Wait -> Email). However, our engineering support indicated that channel activities are effectively 'terminal nodes' that drop the downstream schema, forcing us to insert a new Build/Read Audience activity before any subsequent message to avoid 500 errors. Could you clarify this discrepancy? Is seamless message-to-message chaining supported, or are there specific configurations required to replicate the demos?

    Thanks in advance for your insights!

      C
      Adobe Employee
      ChakravarthyKalvaAdobe EmployeeAuthor
      Adobe Employee
      March 31, 2026

      Thanks for the thoughtful questions — this is exactly the right area to focus on for Orchestrated Campaigns.

      1. Cross-schema joins (Profile ↔ Relational)
      The recommended pattern is to normalize both branches to the same target dimension before Combine.

      • Use Read Audience → explicitly reconcile the Profile audience to your campaign target dimension
      • Use Build Audience (or Change Dimension) → ensure the relational branch is in that same dimension
      • Then use Combine (intersection)

      We don’t recommend directly intersecting heterogeneous branches without aligning dimensions first — that’s the most common cause of unexpected drops.

      2. Target Dimension mapping
      This is critical and strict by design:

      • The target dimension must have a clean, direct identity path to Profile
      • The identity used for reconciliation must be consistent across both branches
      • Avoid using transactional entities as target dimensions — stick to sendable/person-level entities

      Once set, target dimension is immutable, so getting this right upfront is key.

      3. Debugging (0-count intersections)
      Today, debugging is primarily through stepwise validation and logs.
      Best practice:

      • Validate each branch independently in the same target dimension then intersect

      We understand the need for intermediate data preview on canvas — that’s an area we’re actively looking to improve, but nothing GA to share yet.

      4. Multi-step workflows / channel nodes
      Multi-step orchestration (Email → Wait → Email) is fully supported.

      However, in current behavior, channel activities don’t guarantee preservation of the full working schema downstream.
      So if your next step depends on relational context, best practice is to re-establish the audience (Read/Build) before the next message.

      In short:
      Think of the “bridge” as target-dimension alignment + explicit reconciliation, not implicit joins. That mental model will keep your workflows stable and predictable.

      A
      AmitKu38
      Level 1
      March 13, 2026

      Hi, 

      We have started leveraging Orchestrated Campaigns, could you help us in bringing something in notice about how dataset deletion works, will deleting Dataset tied to Relational Schema also deletes data from relational store? And how does Orchestrated Audience Profiles contributed in the AJO Licensing. 

      Pradeep-Jaiswal
      Pradeep-Jaiswal
      Level 5
      March 16, 2026

      Campaign is designed to run over a span of several days along with wait activity.

      Audience is built using XDM attributes to excluded all customer having opt-in consent as denied, along with some other criteria.

      Campaign starts with the read audience created in above steps.

      I have learned that when campaign is triggered, it has snapshot of all attribute values from xdm & relational tables.

      After several touch point, before sending an email, how can we check if the consent value is still granted, so that we don’t send email campaign to customer having opt-on consent as denied ?

      C
      Adobe Employee
      ChakravarthyKalvaAdobe EmployeeAuthor
      Adobe Employee
      April 1, 2026

      In long-running campaigns, we recommend re-evaluating consent right before each send using Profile attributes, rather than relying on the initial audience snapshot.

      Pradeep-Jaiswal
      Pradeep-Jaiswal
      Level 5
      March 16, 2026

      How to port the OCM segments, campaign canvas etc from one sandbox to another sandbox env in the same ims ? Is it same sandbox package tooling or any other method ?

      C
      Adobe Employee
      ChakravarthyKalvaAdobe EmployeeAuthor
      Adobe Employee
      April 1, 2026

      For sandbox-to-sandbox move within the same IMS, the recommended path is Sandbox Tooling using Packages. OCM segments can be managed this way. But the actual workflows can’t be migrated using this package (tedious but you can copy and paste the workflow from one sandbox to another). The support for this is expected to come in very soon. 

      Terms & ConditionsAccessibility statement

      Loading footer...