Adobe Journey Optimizer

Introducing Onboarding in Journey Optimizer: Built-in capabilities that accelerate your time to value. The customer engagement market keeps moving. Platforms change hands, roadmaps shift, and contracts come up for renewal. When that happens, many teams take a fresh look at their stack and ask the same practical question: How much work is it to switch?Any platform transition involves real work. That is true of every modern platform and every team that has made the move. The better question is how much of that work you should have to do by hand.Onboarding in Adobe Journey Optimizer is built to answer those questions. It is a guided experience inside the product, not a separate tool or services engagement. It works alongside your team, your partner, or Adobe Consulting. Why platform moves feel heavy.Teams moving to a new platform consistently run into the same four things:Time. Converting assets, rebuilding workflows and business logic, and validating everything before going live takes su

Hello ​@all Hope you’re doing wellMy name is Manideep D, working as AJO Developer for one of the financial organization.So here I have a conflict with one of the use case.NOTE: I’ve configured a journey entry capping rule,i.e, only one entry per day which has the highest priority. Use Case:When a profileA is qualified to both the read audiences(A,B) of journey_1,2. It should enter only Journey_1 because it has the highest priority for that day and avoids Journey_2 as per the capping frequency(one entry per day) and receives Email_1 and wait for the following 14days(initial wait). Until this initial wait period (14 days) profileA is not supposed to enter any other journeys, even if it’s qualified to other audience/journeys_1,2,.After completing the initial wait(14 days) and receiving the Email_2, it’ll enter into final wait (90 days). From that day profileA can eligible to qualify and enter into another journey which has the top priority for that particular day.During this final wait in

Enable a client into a journey. A journey in this case could be serious of steps a client has to taken to complete an action. Taking an action is supported in multiple channels like web, mobile in app, email and push notifications. How would one should think of creating an omni channel journey that helps us visualize end to end client move through the journey? Question: How can Adobe Journey Optimizer support an omnichannel client journey today and in the future?I’m looking for guidance on how to model and orchestrate an end-to-end, omnichannel client journey using Adobe Journey Optimizer (AJO).In this context, a journey represents a series of steps or actions that a client needs to take to accomplish a specific goal. These interactions may happen across multiple channels, such as:Web Mobile/in-app Email Push notificationsFor example, a client may start an action on the web, receive an email as the next step, continue the process in the mobile app, and then receive a push notification

Hi users, due to new rules of GDPR here in Italy, the privacy act ask us to set a major control on tracking pixels; by far we know that we can set the otion at action level, with the specific chck-box, but, for us, having over 500 email templates active in 100 jouirneys it’s impossible to create a copy for every action w or w/o tracking. So the qustion: is it possible to block the tracking pixel at profile level, setting a boolean field that automatically blocks/uncheck the pixels while sending the email? Hpe it’s clear, thank you for support  

At first glance, Journeys and Orchestrated Campaigns in AJO can look very similar. Both can work with audiences, contain multiple steps, include waits and conditions, and orchestrate communication across channels. Initially it also looks like Orchestrated Campaigns are for batch workflows whereas Journeys are for trigger/event-based workflows. However, a Journey can also behave like a batch-oriented workflow when Read Audience is used as the entry criteria.So, the question is: if Read Audience can be used as the entry point in Journey and process an entire audience, why do we need Orchestrated Campaigns?The difference is not simply trigger/event vs batch. The answer is that Journeys are profile-centric and Orchestrated Campaigns are campaign-centric. Journeys: Think about the customer’s progressionA Journey is designed around the experience of an individual profile.For example, consider a cart abandonment scenario:Cart Event ↓Wait 2 hours ↓Did the customer purchase? /

When adding targeting rules in an action (email), I want to try these rules in the simulation content and it does not work. When I tried it at first it was working fine, but now shows the same template for every audience and they have to be different because i configured them to be different in each tier.

Hi there,I was wondering if there’s an expression I can referent to count the number of profiles coming in from previous node and if it’s more say 1000, go to Others path? In short, any alternate to Profile Capping which we have been testing.Thanks!

Hi Adobe Community,I'm looking for current or upcoming opportunities to earn an Adobe Experience Platform (AEP), Real-Time CDP, or Adobe Journey Optimizer (AJO) certification exam voucher.Are there any active certification voucher promotions, community initiatives, learning challenges, or upcoming events through which community members can earn a free exam attempt?I'd appreciate any official links or guidance. Thank you!

Do you know what is the max number:Max number of surfaces per code base channel configurations?  Max number of actions in code base campaign? 

Why I am not able to save Custom Event Type when I try to set up the capping?  

Hi Team,I'm relatively new to Orchestrated Campaigns and am trying to develop a deeper understanding of a few concepts that seem closely related but are not fully explained in the documentation:Grain Target Dimension Reconciliation Enrichment Change DimensionI've reviewed the available documentation, but most examples are fairly basic. I'm hoping to get a more conceptual explanation, ideally with sample data and before/after results.My Current UnderstandingGrainMy interpretation is that grain refers to the level of detail of the dataset, or simply:"What does a single row represent?"Examples:Customer table → 1 row = 1 Customer Order table → 1 row = 1 Order Claim table → 1 row = 1 ClaimTarget DimensionMy understanding is that the Target Dimension represents the schema/entity that the workflow population currently belongs to.Examples:Customer Order ClaimExample ScenarioCustomerCustomerID C1 C2 OrdersOrderID CustomerID O1 C1 O2 C1 O3 C1 O4 C2 This is a standard Customer →

I’m building a journey where the decision criteria are based on whether users clicked or did not click on communications, both for email and push notifications. I tried using the Reaction Event, but it doesn’t behave the way I expected. What would be the best approach to implement these decision points in the journey? Should I create an audience for users who clicked and another one for those who didn’t? Could you please help me understand the best way to set this up? Im using the AJO. 

Why its not included?Create a Decision Item | Adobe Journey Optimizer 

Why no offers are returned if you can side on the right side of the screen that some are exisitng on that sandbox? :)  

I want to send a Custom Action POST request to CRM during a journey workflow:  jo_status_code for this sendout shows 400 without any further details. I asked support for help  Additionally test authentication shows that the test is successful. Did you come across that this feature might be bugged?   So the error might be with my request structure. How would you futher debug? :( 

Hi all, I want to clarify the total time a customer profile can be in a AJOB2B person journey. As per the AJOB2C documentation, it clrearly mentions the timeout duration to be 91 days i.e. the global timeout stops the progress of individuals in the journey 91 days after they enter. This means that an individual’s journey cannot last longer than 91 days.I’m looking for similar information for AJOB2B person journey, the closest setting I can find here is that the AJOB2B journey end date can be 3 years from start date, does that mean the individuals can progress through the AJOB2B person journeys for 3 years?Any thoughts and information on this would be helpful.Note: I don’t see AJOB2B in the category picklist hence selected AJO.Thanks,Shashank

That type of capping counts when actually offer was chosen in ODE Decisioning? 

I'm trying to trigger a Journey entry using a unitary event condition based on an unsubscribe event coming from a landing page.Entry condition used:(isNotEmpty(@event{All_Consent_Update_Event._experience.customerJourneyManagement.messageInteraction.subscription.subscriptionListID})) and (in(@event{All_Consent_Update_Event._experience.customerJourneyManagement.messageInteraction.subscription.subscriptionChoice}, ["no"]))Context:When a profile unsubscribes via a landing page, the event is correctly generated and visible on the profile. Under messageInteraction.subscription, both subscriptionListID and subscriptionChoice are populated with the expected values (subscriptionChoice = "no"). However, when this same event/condition is used as the entry trigger for a Live Journey, the profile does not enter the journey.What I've already verified:The event is present on the profile timeline with the correct field values. The XDM path used in the condition matches the schema field path on the eve

Hi everyone,I'm implementing Web Push in Adobe Journey Optimizer with the Web SDK, and I'm trying to pass custom metadata to the service worker using the Custom data section of the push content editor. The key-value pairs don't appear in the payload the service worker receives, and I couldn't find official documentation describing how Custom data is handled for the Web platform. SETUP- Web SDK (alloy.js) 2.35.0 with pushNotifications configured (vapidPublicKey, appId, trackingDatasetId)- Official alloyServiceWorker.js served from the site root- Push channel configuration with the Web platform selected- Event-triggered journey with a Push action; Custom data added to the content and the journey republished WHAT I TESTEDTo inspect the raw payload before the Adobe service worker processes it, I added a push listener at the top of the service worker file:self.addEventListener("push", function (event) {  console.log("[DEBUG]", JSON.stringify(event.data.json(), null, 2));});The notification

Quick lesson from a recent Marketo-AJO project: Marketo is program/campaign-centric whereas AJO is event/journey-centric. This sounds obvious, but it changes the schema design, segmentation, and journey logic. This is not a mere lift-and-shift setup.  The two main things aren’t the journeys themselves. These are schema design and identity resolution. Both are harder than they look. XDM Schema DesignIn Marketo, the data model is flat and permissive - custom fields can be added without touching anything else. In AEP, the schema is formal and more structured that every journey, segment, and destination downstream depends on.Few things that matter in practice:Schema classes come first: AEP has 2 main core classes - XDM Individual Profile (attributes like name, email, title, etc.) and XDM Experience Event (timestamped events like website visits, form fill outs, etc.). Every Marketo field needs to be sorted into one of these buckets before building anything else. Some Marketo fields have no

I use a Contentful as a CMS for web. CMS requests Edge Decisioning API and then render the offer. I need to debug what identities are sent in the request do you know if that request land is some specific dataset? 

Have you used that API?My Prod and Dev are not 1:1 so I am expecting problem. I assume as a first step do the POC: Prod Offer Decisioning → Dev Decisioning for one specific Decision ScopeDo you recommend creating all the profile attributes, audiences etc on Dev and then map prod → dev?Any advices?