Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
This post is for informational purposes only. It is not legal advice and does not warrant your compliance. The Adobe Marketo Engage product capabilities described in this help article, configured and operated appropriately, support a compliant implementation. Each user is responsible for determining and complying with its obligations under applicable law.OverviewOn April 14, 2026, France’s data protection authority (CNIL) published a recommendation on the use of open tracking pixels in emails. The guidance clarifies when consent is required and highlights the importance of proper consent practices for email pixel tracking. This policy impacts any entity sending emails to subscribers based in France.CNIL provided a three-month period from the date of the recommendation for companies to inform their email recipients of the presence of the tracking pixels, their purpose, and the recipients’ right to opt-out. During this transition period, Marketo Engage users are expected to notify their
Welcome to the September edition of the Workfront Wire! This is your monthly roundup built just for Workfront customers. Think of this as your one-stop-shop for the latest news, updates, events, and everything happening across the Workfront world. Each month, we’ll bring you what’s new, what’s next, and what you should know to get the most out of Workfront, without having to dig for it. Let’s get into it, and we’ll see you again In October for the next edition of the Wire. Workfront Skill Exchange On-Demand The Workfront Skill Exchange sessions are now available to watch on demand! As you work through the recordings, you may find you have questions for our speakers, and we encourage you to ask them. Discussion posts have been created on the Experience League Community for each session. Please leave your questions in the appropriate thread to chat with our presenters directly. Don't be shy! These folks have been in your shoes and are here to share their experience, so you don't have
The Adobe Experience Manager Skill Exchange sessions are now available to watch on demand here! The Skill Exchange is a global series of virtual customer learning events, focusing on diving deeper into Adobe Experience Cloud solutions. From Skill Exchange sessions you will learn about innovations and gather best practices and tips for next steps from peer and Adobe product experts.We hope you take time to watch one of interest to you and get inspired to take these ideas, best practices and key takeaways back to your teams. Content Authoring Evolution and Best Practices with AEM Champion @venkatkrishnat Understand the evolution of content authoring, structured content models, and why this shift is critical for scalability Learn how authors can influence AEM design by driving requirements for components, templates, and content models that improve usability and reuse Adopt future- ready best practices that balance flexibility, governance, and emerging AI-assisted workflows to create eff
Opens and clicks have long been considered the gold standard for measuring email performance, thanks to their simplicity and broad accessibility. But in recent years, the gap between these metrics and real human behavior has grown rapidly. Today, relying on basic metrics like opens and clicks can be misleading. Why? Because they track technical signals, not real human behavior. Why Email Metrics Often Don’t Reflect Real Human Behavior Here’s the reality: Opens are recorded when a tracking pixel loads, and clicks register when a link is requested. Neither proves that someone actually read your email, paid attention, or intended to engage. Factor in modern email bots, security scanners, and privacy tools, and what looks like an “engaged” audience can be a mix of real humans and automated systems. As marketers, it’s crucial to grasp not just how this skews standard email engagement metrics, but also the ripple effects it can have on revenue and the sales funnel: Compromised A/B Test Resu
An upcoming deprecation may impact your integration with Marketo Engage and may require action. The Marketo Engage SOAP API will be fully deprecated on August 31, 2026 (the REST API Access Token has already been deprecated). Please review this post if you are still using the SOAP API in one or more of your Marketo subscriptions. To avoid disruptions of service, you will need to retire or migrate any services using the SOAP API to the Marketo Engage REST API by August 31, 2026. Consult the Migration Guide for further information. Marketo Engage Support is only able to provide the IP address of requests made to the SOAP API. On August 31, 2026, the Marketo Engage REST API will no longer accept access tokens for authentication and authorization via the ‘access_token’ query parameter. Please check if one or more of your integrations uses this parameter to authenticate. To avoid disruptions of service, any services using this parameter to authenticate will need to migrate to using head
This article makes the case for setting up a lightweight Workfront release management process, and shows how it's easier to implement than most people assume.Key points:The problem: Untested changes going live in Workfront can catch teams off guard and erode trust. The fix doesn't need to be heavy: Release management just means having a repeatable way to plan, test, approve, and communicate changes — not a bureaucratic approval chain. Two sandboxes, two jobs: SB02 (Sandbox 2) is where technical building and testing happens; SB01 (Sandbox 1) is where real users validate changes before go-live. Keep sandboxes fresh: Regular refreshes (SB02 more often, SB01 before major testing cycles) keep testing environments realistic — stale sandboxes give false confidence. Environment Promotion moves things along: Workfront's built-in packaging tool lets you move configuration changes (forms, fields, templates) between environments reliably, instead of manually rebuilding them each time — build → com
I'm looking for guidance and best practices from anyone who has implemented bilingual SMS compliance keywords in Adobe Journey Optimizer (AJO), particularly in a Canadian context.ScenarioWe're using:Adobe Journey Optimizer (AJO) Sinch as our SMS provider A single shared short code for both English and French audiencesAs part of Canadian SMS compliance requirements, we need to support mandatory opt-in/opt-out keywords in both languages, including:EnglishSTOP HELPFrenchARRET AIDEChallengeThe integration documentation between AJO and Sinch appears to rely on a single inbound webhook endpoint for processing SMS replies. Based on the documentation I've reviewed, I haven't found a clear approach for configuring language-specific automatic responses.For example:If a user texts STOP, they should receive an English confirmation message. If a user texts ARRET, they should receive a French confirmation message.However, with a single shortcode and what appears to be a single inbound processing pat
Hi, I have a Dispatcher filter rule to allow for DELETE method for a specific url path. It works fine on my local AEM instance Dispatcher. The same errors out “406 Not Acceptable”Can you please suggest a fix for the AEMaaCS environment?The following is how the rule looks in the sites_filters.any file./0123 { /type "allow" /method "DELETE" /url "/service/xyz.json”
Our team has a need to make the filter selection in the My Approvals widget sticky. We have multiple team members that submit work to others for approval and receive work from others for approval. Having to reset the filter each time to show only “My Approvals” instead of “All” wastes a few clicks of time and makes it more difficult for us to work through time-sensitive approvals.
When updating the panel date ranges, the Comparison Dates stay the same. This means we as users have to delete the old comp dates and percentage change metrics, then create new ones. On bigger “recycled” dashboards, this takes FOREVER! This one improvement would save me hours and hours and hours every year.Thanks! RR
We are looking to manage OSGi configurations in the AMS environment instead of storing sensitive values in the codebase. In Adobe Cloud Manager, there is an option to manage environment-specific secrets and configurations. Is there a similar approach available in AMS, and if so, how can we manage these configurations securely?
Hi All, I ran the dispatcher utility in local and it auto-runs as part of web-tier in build stage too.Ideally one would expect same inconsistencies but there was a difference in my case. Local Validator - PS C:\Users\admin\Downloads\aem-sdk-dispatcher-tools-2.0.274-windows\bin> .\validate.cmd 'C:\projA\dispatcher\src'opt-in USE_SOURCES_DIRECTLY marker file detectedPhase 1: Dispatcher validatorCloud manager validator 2.0.892026/09/07 19:41:48 The following warnings were found: Did not find ServerAlias '*.adobeaemcloud.net' in any vhost file Did not find ServerAlias '*.adobeaemcloud.com' in any vhost file2026/09/07 19:41:48 The following suggestions are proposed: C:\projA\dispatcher\src\conf.d\enabled_vhosts\aem_publish.vhost: file is not a symlink, all files inside "enabled_vhosts" and "enabled_farms" should be symlinks2026/09/08 19:41:48 The following errors were found in the httpd config: C:\projA\dispatcher\src\conf.d\enabled_vhosts\aem_publish.vhost: link points to invalid lo
Hi everyone,I’ve been trying to build this project without much success. Here’s the command I used last:```mvn -B archetype:generate ^ -D archetypeGroupId=com.adobe.aem ^ -D archetypeArtifactId=aem-project-archetype ^ -D archetypeVersion=23 ^ -D aemVersion=6.5.0 ^ -D appTitle="My Site" ^ -D appId="mysite" ^ -D groupId="com.mysite" ^ -D frontendModule=general ^ -D includeExamples=y```I am on windows and I do use cmd with administrator privileges. I’ve tried numerous versions of the command above and I haven’t managed to get it running. Sometimes the build command fails, other times the `mvn clean install` or `mvn clean install -PautoInstallPackage` or `mvn clean install -PautoInstallSinglePackage` fails. And the times that both work and I can see the project in AEM it is still not functioning properly. For example I get an error when trying to create a page. My question is more general as I’m trying to understand how this all works. I have the AEM 6.5.0 version.From aem-project-archetyp
Hi all,I'm trying to understand a specific aspect of AJO's decisioning capability. Does AJO's decisioning engine have the ability to generate/select offers purely on its own — using only internal AJO/AEP configuration (like offer eligibility rules, priorities, and constraints) — without needing to pull any profile or event data from an external/3rd party source into AEP?
Hi All,I'm trying to understand a discrepancy in visitor counts between Adobe Analytics and an Adobe Target activity using A4T reporting.I created a new Adobe Target activity that targets all visitors landing on a specific URL, and the activity is configured to use Analytics for Target (A4T) reporting.However, I noticed the following:Adobe Analytics reports approximately 500 unique visitors for this URL. The new Target activity shows only 250 unique visitors. I also have another existing Target activity running on the same URL, which includes an additional mobile segment as part of the audience criteria. That activity is showing approximately 390 unique visitors in Analytics.Since the new activity is targeted to all visitors on the URL, I would expect all visitors landing on that page to qualify for the activity.Could anyone help me understand what might be causing this discrepancy between the Analytics unique visitor count and the Target activity unique visitor count?Thanks,
Adobe Target appears to interpret ${} as Target variable/token syntax, which conflicts with JavaScript ES6 template literals.For example:let x = 'Testing var';console.log(`Value: ${x}`); Instead of printing:Value: Testing varthe content inside ${} gets removed or replaced during Target processing, resulting in unexpected behavior.As a workaround, developers must use string concatenation:console.log('Value: ' + x); It would be helpful if Adobe Target could either:Support JavaScript template literals without preprocessing ${} expressions. Provide an escape mechanism for JavaScript template literals. Document this limitation and the recommended workaround in the official documentation.This would prevent conflicts between Adobe Target token replacement and standard JavaScript syntax, making custom code easier to write and debug.
Event Forwarding governance and optimization are becoming increasingly difficult as implementations scale and additional rules are introduced. While the current monitoring experience provides an aggregate compute-time view, it lacks the visibility needed to understand which individual rules are responsible for overall resource consumption. This creates a significant operational challenge because teams can identify that compute-time usage has increased, but they cannot determine what is driving the increase, which rules are contributing the most, or where optimization efforts should be focused. As a result, troubleshooting becomes highly manual, requiring teams to review rules individually, make assumptions about potential bottlenecks, and perform extensive testing without any data-driven insights.To address this gap, the Event Forwarding monitoring UI should provide rule-level compute-time attribution that allows users to understand exactly how much compute time each rule consumes duri
I’m currently trying to create a fusion scenario to map the Workfront Core project status to a Planning record’s status field so there is more parity between the two objects. I’m running into this very odd issue where for some Planning Workspaces I am able to successfully map the status but in other workspaces I can’t. I’m an Admin and the owner of all workspaces so I don’t think it’s an issue with permissions but given how complicated Planning sharing is I haven’t fully ruled that out.The fusion scenario throws no obvious errors and appears to execute successfully, however in the output bundle I get is below, and I know the record ID it’s saying doesn’t match does exist: { "body": { "data": { "status": "failed", "total": 1, "succeeded": 0, "failed": 1, "requestId": "[Request ID redacted for privacy]", "results": [ { "requestIndex": 0,
While initially excited about the NEW Email Designer, I’ve found it to be incredibly frustrating to work with. I would appreciate any support with the spacing issue I’m having. I’ve included images of how my email looks in Marketo and how it looks once sent via Gmail. You can see the spaces between sections at the top and bottom of the email. I can confirm that there is no extra padding in any of the components/fragments of my template. While I can see the HTML, in the design studio, it’s locked so I can’t make any changes. I have watched every tutorial and asked as many users I can find and can get no solution. Additionally, there’s no way to bring in plain rich text without losing our brand fonts, weights etc. UGH. Not having the ability to upload our brand fonts/colors in the new designer and having it hold while working on an email is crazy. To have to add a custom color for every usage is very frustrating.
There should be a setting in the new launch to be able to track s.products without going to the custom code to build the product string.Kind of like how the old GTM had a checkbox to enable e-commerce tracking and it would just read the dataLayer Enhanced Ecommerce (UA) Developer Guide | Google Tag Manager for Web Tracking | Google Developers
Hi everyone,I’m trying to identify duplicate records in our Marketo database using a Smart List with the “Email Address is duplicate” filter.The Smart List is showing 6 records, but when I go to the People tab and search for the email addresses of those records, I’m unable to find another person record with the same email address.Has anyone experienced this before?I’m trying to understand:- Why would the “Email Address is duplicate” filter return records when I cannot find the corresponding duplicate records in the People tab?- Could this be related to deleted/merged records, workspaces/person partitions, indexing, or Smart List data refresh?- Is there a reliable way to identify the actual duplicate records that Marketo is detecting before we proceed with a database cleanup?Any guidance on how to troubleshoot this would be greatly appreciated.Thanks!
I’m facing Adobe Analytics Error “Error code: 500-001: Page loading fail”.I’m not sure why this error happens. Full error message is below:The page could not be loaded correctly. Please verify your login and try again. If this message continues to appear, please contact customer support with the following reference information: EIM Instance ID 230e11a2-ab1a-11f1-8dfe-2f547bb1e87c.
Hi Team,I’m working on a use case where I need to trigger a Workfront Fusion flow when a Smart Campaign is run/activated in Marketo.The requirement is:When a Smart Campaign is activated/run in Marketo, the Fusion flow should be triggered. The flow should check whether the Communication Limit option is unchecked for that campaign. If the Communication Limit is unchecked, the Fusion flow should proceed and send the email. If the Communication Limit is checked, the flow should not send the email.Is there any way to trigger a Workfront Fusion flow when a Marketo Smart Campaign is activated/run? Also, is there a Marketo REST API that can return the Communication Limit setting for a Smart Campaign?Any guidance or recommended approach would be greatly appreciated.Thanks!
Please build API where you can store the user activity from 12 months to var node and so that based on that we can able to identify the how many active users are there from past 12 months.
We are investigating an issue related to Unspecified values and are trying to determine whether we're encountering a configuration issue, a data collection issue, or a platform limitation.In the example below, some conversions are successfully attributed to the menu-details dimension using Link Position, while 68 other conversions appear as Unspecified and cannot be tied back to a dimension.Why would some conversions be attributable to a dimension such as Link Position or Link Name, while others remain Unspecified? Is it reasonable to expect that most click-tracking conversions should be definable and reportable against a link dimension, or are there scenarios where Unspecified is the expected behavior?More specifically, can Target users define click-tracking conversion metrics using link-level dimensions such as Link Position and/or Link Name, and are there any known limitations that would prevent these dimensions from being available for certain conversions?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
