Product Communities

Hello there,   I'm reaching out with an important update regarding the Marketo Engage Career Connect job board. After careful consideration, we've made the difficult decision to discontinue this service, effective Tuesday, March 20th. We understand that this news may impact many of you who have relied on this resource for career opportunities.   First and foremost, I want to express our deepest gratitude to everyone who has used Career Connect to advance their Marketo-driven careers. Your engagement and trust in this platform have been invaluable, and we're truly appreciative that it has been an important career resource for many of you. As we move forward with this transition:   We will be contacting all users with Career Connect accounts, including both candidates and employer profiles. Following the shutdown, all associated Career Connect domains will redirect to the Marketo Community.   If you have any questions about the shutdown process or need assistan

Hello, San Antonio Marketo enthusiasts!   We have some exciting news to share with you! After a break, we are thrilled to announce the official restart of the San Antonio Marketo User Group. And not only are we restarting, but you’ll also get to meet two of the current Marketo Champions at the event!   Join Us for a Night of Networking and Knowledge!   We’re inviting all San Antonio Marketo users to come together for an evening of meet and greet, networking, and Q&A. Whether you’re a seasoned pro or just starting out, this event is for you. Bring all your questions, challenges, and ideas, and let’s tackle them together.   Event Details: Date: March 12, Wednesday Time: 6pm-8pm (CST) Location: Buffalo Wild Wings, 5860 De Zavala Rd, San Antonio, TX 78249 Enjoy Some Delicious Wings!   To make the evening even more enjoyable, we’ll be serving up some delicious wings and refreshments. It’s the perfect setting to relax, connect with fellow Marketo user

“We’re seeing duplicate GTM Data Layer updates for a single Marketo form fill,” read the trouble ticket. “Sometimes even 3 or 4 updates.”   My mind went to adding multiple onSuccess listeners. Sure enough, they had a setup like this: function gtmAfterSubmit(submittedValues){ dataLayer.push({ event: "marketoFormSubmit", form: submittedValues.formid }); }); MktoForms2.whenRendered(function(mktoForm){ mktoForm.onSuccess(gtmAfterSubmit); });   Spot the problem?   It’s the use of whenRendered, which fires every time form elements are injected by Visibility Rules. They had some VRs in place (Country ⮕ State dependency, business vs. personal fieldsets) so the form rendered more than once. Each render meant another gtmAfterSubmit() pushed onto the onSuccess stack. Once the form submitted successfully, they all ran.   The fix is to use whenReady. To be clear, whenRendered is key to a lot of custom form behaviors — we more often see people use whenReady whe

Dear AEP Community, Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with Adobe Experience Platform.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for February 2025, designed to help you resolve common challenges swiftly and effectively. Our Top KCS Articles are your shortcut to: Quickly identifying and resolving recurring issues.Accessing expert insights and best practices for AEP.Streamlining your troubleshooting process for maximum productivity.Empowering yourself with the knowledge to tackle any AEP-related problem head-on. Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – creating highly personalized digital experiences with AEP. Start supercharging your problem-solving skills today by exploring our&

Dear AEM Community, Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with AEM.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for February 2025, designed to help you resolve common challenges swiftly and effectively. Our Top KCS Articles are your shortcut to: Quickly identifying and resolving recurring issues.Accessing expert insights and best practices for AEM.Streamlining your troubleshooting process for maximum productivity.Empowering yourself with the knowledge to tackle any AEM-related problem head-on. Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – empowering you to provide a truly personalized experience to your customers with AEM. Start supercharging your problem-solving skills today by exploring

Dear Adobe Campaign Community, Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with Adobe Campaign.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for February 2025, designed to help you resolve common challenges swiftly and effectively. Our Top KCS Articles are your shortcut to: Quickly identifying and resolving recurring issues.Accessing expert insights and best practices for Adobe Campaign.Streamlining your troubleshooting process for maximum productivity.Empowering yourself with the knowledge to tackle any campaign-related problem head-on. Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – creating exceptional campaigns with Adobe Campaign. Start supercharging your problem-solving skills today by explo

Hi Team, We have requirement to remove all the allowedComponent list from the page sling exporter, there are more than 50+ custom SPA components due to that model.json size is larger. In 6.5 version, is there any way to ignore allowedComponents ? Thanks for the help in advance!!

Curated by @zoe_forman & @ilona_buteneers    Introduction The Marketo platform is migrating to the Adobe Experience League platform, and with this comes an important change: the move to Adobe's Identity Management System (IMS). This migration will soon be coming to your Marketo instance. This move aims to streamline your experience and integrate Marketo more seamlessly with other Adobe products. This post will walk you through the key benefits, offer tips for a smooth transition, and explain the migration process.   Why Migrate to IMS? The migration to IMS offers several key benefits: Unified User Management: Manage your Marketo Engage subscriptions and users within the Adobe Admin Console, alongside your other Adobe products. Easy Switching Between Organisations: Seamlessly switch between different organisations. Single Adobe Identity: Sign in with one Adobe ID across all Adobe products and the Marketo community. Centralised Support: Access support,

Managing multiple email addresses within Marketo can be tricky, but it's a common challenge in many marketing automation strategies. Often, prospects or customers have alternate email addresses for different purposes (e.g., work and personal emails), and managing them accurately is essential to creating meaningful and personalized marketing experiences.   However, challenges arise when replacing the Primary Email Address with alternate emails, leading to record invalidation and unreliable reporting. To address these issues, we should develop a scalable solution to track, validate, and manage invalid email records efficiently. Common Challenges Invalid Lead Records: Marketo marks the entire lead record as invalid if any email hard bounces, making it difficult to pinpoint the exact cause. Lack of Email Tracking: No visibility into which specific email field caused the invalidation. Compromised Email Campaigns: Marketo’s standard email field is used when executing targeted camp

In the following HTL code, where I'm using a method that returns a JSON string, I am concerned that it might cause XSS vulnerabilities when the data is rendered in the HTML:<sly data-sly-use.obj="com.components.models.class">${ obj.method @ context= 'unsafe'}</sly>Also, in my JavaScript code, I am accessing the DOM and parsing the JSON data, which I then manipulate and render back into the DOM. I’m worried that this could lead to XSS vulnerabilities as well:const Script = document.querySelector(' script');const data = JSON.parse(Script.innerHTML.trim());  Script.innerHTML = JSON.stringify(data, null, 2).replace(/},\s*{/g, '},\n{').replace(/\[\s*{/g, '[\n{').replace(/}\s*\]/g, '}\n]');How can I fix both of these to prevent XSS vulnerabilities?

Hi,      We have started seeing this recently where when we create a content fragment under a specific path it starts index update with below pattern and keeps on looping and does not stop. At the end of each loop it is showing following error: [sling-oak-1-org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate-async] org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler Failed to create checkpoint 869e77b7-7028-42b4-ade5-87fbb168a204 in 10 secondsIndex update log that is looping: It is looping till 70000 and starting again from 10000GET /editor.html/content/dam/digital/test/fragments/dir1/en-us/places/hotel-florida HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.IndexUpdate /oak:index/uuid => Indexed 10000 nodes in 3.219 s .. In the above hotel-florida is the content fragment. We were unable to identify the root cause or solution to fix this issue. We need to kill the java process to restart the application. Once the application is up ever

By @amandadeasy  and @chrismdavis  Migrating Adobe Analytics and Target implementations to Edge Data Collection simultaneously is key to streamlining your setup and ensuring consistency across your Experience Cloud solutions. In previous blogs, we discussed the value of using the data object when implementing Edge Data Collection for Experience Cloud solutions, including Adobe Analytics. In this post, we’ll dive into using the data object to migrate mbox parameters for Adobe Target. For a complete step-by-step guide, check out this Web SDK migration tutorial for Target.  Recall that the data object allows you to implement Web SDK without using an XDM schema. For Target, this approach also provides a flexible way to configure and pass mbox parameters without additional mapping, making implementation and validation even easier!  Creating the Data Object  Before you begin, ensure that your datastream is enabled for Target. If you haven’t already set

Hi Team, Recently I have faced a issue regarding cross domain tracking when user click on login which is added as button without anchor tag href.  I have implemented appendVisitorIDsTo method and it will works fine when you link is having href but when user click on button which will not have anchor tag and href in this case Implement a robust cross-domain tracking solution using Adobe Analytics (AppMeasurement.js) where tracking parameters are appended to button URLs through the backend system.This ensures consistent visitor identification across multiple domains. I have worked with back-end developer and added the AppMeasurement.js and VisitorAPI.js script on head section so that when user click on button it will appendVisitorID and set it on next redirection URL so that when user lands on page it will add the visitors id in landing page and visitor it will not get changed.With this solution visitor identity is maintained seamlessly across domains, improving attri

Hi Team 1. are there any additional steps for implementation of vanity url for SPA driven setups.2. also the routing of controls from vanity urls to the actual urls of the page should be automatically taken care of. Right ?3. Ours is a SPA application and we are facing issue in getting the URL fetched the original url as well as the model.json RegardsBishnu

Hi Team, I am seeing the wired behavior on the production environment . One of the component on the page not showing option to delete or other options but if i drag and drop the same component i can able to do any of the operations on it and along with that i am seeing component name along with [Root].Example Component name is Text , it is showing as Text[Root] (already existed on the page ) if i drag the component it is showing correct name as Text.Only showing the option Configure, Convert to Experience fragment variation , layout Thank you,

I'm new to Designer and have no coding experience so bear with me.  I'm using Designer 6.5 to create a form that has several check boxes. I need a warning message to appear if a user selects every check box. The message will state: "Please refine your choices".  How should I go about doing this - with the script editor? If so, how? Or is there a simpler way? Thanks!

Hi all - We are seeing an issue with versioning of clientlib after every deploy. We do not see clientlib cache getting clear which results in previous version# being returned even for an updated js/css file after deploy. We have to manually go and "touch" js.txt/css.txt file to see updated version. If we reduce md5 cache size to 0, we see updated version# after each deploy, this leads me to believe that ACS Commons is not able to update cache after each deploy. Can anyone help?

Hi, In the AEM React SPA application when the author environment page loads the user is not able to see any of the components in the content tree and not able to configure the components. However when user clicks on Preview option and then on Edit then content tree loads up correctly and the components dragged on the page could be selected. This issue is on all the environments LOCAL, DEV, UAT and PROD. Thank you for your time, consideration, and experience! Regards,Varinderjit

Sending birthday emails right at 12:00 AM in the recipient's local time is an excellent way to enhance personalization and customer engagement. For example, a customer in Paris should receive the email at 12:00 AM Paris time, while a US-based customer will receive theirs at 12:00 AM in their respective time zone. This approach ensures your message arrives at the perfect time, making the customer feel special. Here’s a guide on how to set up and schedule such birthday emails effectively using Adobe Journey optimizer tool.   Key Prerequisites Ensure the time zone field is available in the customer's profile. This can be sourced from the Preference Details field group.     Timezone attribute would hold a string value. Make sure to add the correct timezone value to the profiles.   Audience creation Use filters to identify profiles whose birthdays fall within a one-day timeframe. This ensures the journey targets the correct audience each day.    

IntroductionData Distiller is a powerful Adobe Experience Platform offering that enables post-ingestion data exploration, processing, and transformation. The Overview Homepage is designed to provide users with quick access to essential resources and insights.  Key Features of the Overview Homepage1. Quick-Access Product ShortcutsThe homepage offers effortless navigation with prominently displayed shortcuts for:Creating SQL queriesExploring use casesAccessing key functionalitiesLearning more about Data Distiller2. Comprehensive Details On Use Case CategoriesUsers can discover primary use cases, including:Data ExplorationDerived Datasets for Platform based appsAI/ML PipelinesSQL InsightsEach category is linked to detailed documentation for comprehensive understanding.3. Distiller AcceleratorsPre-built Templates for following:Advanced Audience OverlapAudience ComparisonAudience TrendsAudience Identity OverlapsCurate your own data templates4. Key Usage MetricsMonitor your platfor

We are establishing relationship from Lookup to Individual Profile schema, using  cross device as well as non-people Identifier as namespace, we are not able to fetch lookup attaributes in the Audience though Full Schema view is enabled, however when we do the relationship from Individual Profile to Look Up it was working as ecpected. notes: 1) Both the schemas are profile enabled2) Dataset are also enabled and have some dummy data as well

Upgrading from Java 11 to Java 21: A Guide for AEM Developersby @daniel-strmecki OverviewAs an AEM developer, staying current with Java versions ensures we can leverage the latest features, security patches, and performance improvements. With Java 21 being the latest Long-Term Support (LTS) release, it's a critical upgrade for enterprises and developers working on Adobe Experience Manager (AEM) projects. Java LTS versions are supported for a longer period than non-LTS releases, making them ideal for production environments where stability and security are paramount. For example, Java 21 was released in September 2023 and will receive Premier Support until September 2028 and Extended Support until September 2031.In the latest release of Cloud Manager 2025.1.0, Adobe announced that they now support Java 21 in AEMaaCS. Java 21 will be enabled for all customers in February 2025, along with the rollout of a new SonarQube version. This article focuses on API features and enhancemen

Hi All,We have registration functionality on our website where an AEM sling servlet collects the data from form and inserts that record into a database table. AEM Sling servlet is invoked from Ajax call from client side. We suspect that there are fraudulent attempts by invoking the sling servlet directly from API client like Postman. AEM Sling servlet is registered with resource type. Is it possible to invoke sling servlet from API client like Postman? If yes, how can we block the attempts to the servlet. Please help here.

AEM Dispatcher: Using RewriteMap to define Redirects by Neeraj ChaudharyIn the world of web development, redirects play a crucial role in maintaining the integrity of URLs, especially during site migrations, content restructuring, or SEO optimisations. For AEM, the Dispatcher is the go-to solution for managing these redirects. One particularly powerful but sometimes overlooked feature of the Dispatcher is the RewriteMap.What is RewriteMap?RewriteMap is an Apache HTTP Server feature that allows you to define a mapping of URLs or patterns to their corresponding target URLs. Unlike simple rewrite rules that are inline and singular, RewriteMap lets you centralize and manage a large number of redirects from a single location.Key Benefits of Using RewriteMap:Efficiency: It processes large numbers of redirects faster by avoiding repetitive conditional checks.Maintainability: Centralized redirection logic makes updates and management easier.Scalability: You can add, re

Welcome back to Expert Insights!  I’m Cynthia Boon, your “On-Demand” Workfront CSM, and in this episode, we are joined by Danielle Johnston (@danielle_john)!  She shares her ideas on how to get started, ways to use Workfront to support your Governance and Center of Excellence efforts and encourages us to be the positive change we want to see in Workfront!      Resources and examples mentioned during the interview:  Ideas:  Start small. Communication is the key to change!  Have your “Why are we using Workfront – elevator speech” ready! Your Execs and your users will ask, so having clear talking points will prepare you for those surprise conversations.  Use Workfront to support and track your Governance and Center of Excellence efforts.  Webinar Links  Webinar | System Admin Essentials: Leveraging the Group Admin (May 11, 2022)  Webinar | System Admin Essentials: What IS Workfront Governance? (Mar 30, 2022)  W