Product Communities

If your bounce rate is showing near-zero percentages after migrating to the Web SDK, this post explains why it happens and how to build a reliable alternative metric.Why Native Bounce Rate BreaksAdobe Analytics bounce rate = visits with exactly 1 hit / total visits. When success events fire on page load as separate beacons (component presence tracking, feature flags, etc.), every page visit immediately has 2+ hits so almost nothing qualifies as a bounce, even when users leave immediately.The Solution: Page View-Based Calculated MetricBuild a segment and calculated metric using page views instead of hits:Segment: Include > Visits > Page View (event1) equals 1 Calculated Metric: [Segment] × Visits ÷ Visits = Page View Based Bounce RateThis is immune to your success event inflation because page views don’t increment on non-page-view beacons.Watch Out: Event Multi-FireIf your custom page view event itself fires multiple times per visit (common with SPA frameworks or overlapping Adobe

I’ve been exploring different Adobe advertising and marketing tools lately, and one thing I keep noticing is how much modern campaigns now rely on personalization and user behavior data rather than just traditional ad placement.With platforms like Adobe Experience Cloud focusing heavily on customer journeys, analytics, and audience segmentation, it feels like advertising is becoming much more experience-driven instead of simply pushing ads to large audiences. Adobe communities also emphasize learning, collaboration, and improving customer experiences through smarter workflows and integrations. ()I’m curious how others here approach balancing personalization with simplicity. Do you think highly targeted campaigns genuinely improve engagement, or are users starting to feel overwhelmed by “too personalized” advertising experiences?Would love to hear how different teams are using Adobe tools for campaign optimization and customer engagement.

Hi, Looking for some ideas and support here -  I am the admin for a financial services company, we have lots of regulations. We received a request that we now need to have our approvers “certify” that they checked the asset in the proof for x, y, z. My initial thought is to add a custom form to the document but this would be brand new behavior for our approvers to fill out and don’t love this. We also had someone bring up adding a comment, I also don’t love this because it is manual and think that we will be chasing down approvers to add this (also will mess up my automated workflows). Has anyone ever experienced this or has any idea? TYIA

Buried in the extremely large feature release last month, were a number of layout template enhancements which I wanted to call out for those of you who might have missed it. The LT enhancements are applicable to all contracts as far as I can tell. https://video.tv.adobe.com/v/3483245/Please watch the recording if you’re interested in the new LT functionality below.-- Determine the options that appear in the More menu (proj, task, issue, portfolio, program)-- Determine toolbar options (e.g. you can hide everything except Create Project from Template)-- Customize header fields to include custom fields. (the 5 field limit remains unchanged)-- Customize left nav bars for groups, teams, users, templates Tagging in ​@user01245 for the 4th bullet point -- this might fix your issue more efficiently if you lock your casual requesters out of this section on their details page.

Hello,we are trying to add seo schema to our page, Adobe's documentation suggests to use json-ld to author seo schema, but I am clueless on how to add it as a property to page.json. Whenever I tried to add it as a property to page.json, the content which I author in that page is being rendered as a meta tag with name property which I have defined in page.json. It is not rendering as script tag as it was mentioned in documention. Could anyone help me with this.  Thank You.

Join us for a panel discussion focused on building and advancing your career as a Workfront Admin. Hear from experienced professionals as they share what has fueled their growth, how they have expanded their skills, and the moments that helped shape their career paths.This session will focus on real world insights, from what makes the role fulfilling to how Workfront expertise, Adobe connections, and emerging tools like AI can open new opportunities. Whether you are looking to grow in your current role or take the next step, you will gain practical advice and perspective from those who have been in your shoes.What you will learn: What makes a career as a Workfront Admin rewarding and sustainable How building Workfront expertise can impact your long term career growth Tips for leveling up your skills and positioning yourself for new opportunities How to start incorporating AI into your day to day work Career advice panelists wish they knew earlier This is a session you will not

With Claude or Cursor, is anyone using any MCPs that are helping either with code, workflow or analytics within work being done in Adobe Target?

If you've built a report, view, dashboard, or workflow in Workfront that makes your life as a project manager easier, we want to turn it into a recipe. The PM Cookbook is a community-driven collection of real Workfront setups — by project managers, for project managers. Think of it as your favorite recipe card, but instead of ingredients and steps, it's filters, fields, and the logic behind why it works. What makes a great “recipe”?Share something you actually rely on:A report you run every week A dashboard that stopped the constant “Can you send me a status?” pings A view that finally gave your team one source of truth A workflow that removed manual steps or confusionIf it solved a real problem for you or your team, it belongs in the cookbook. What you’ll submitTo submit your recipe, you’ll need:Recipe name Prep time, yield, and who it serves (e.g., “10 minutes to build, used by PMO leads weekly”) Report / view / dashboard / workflow type Step-by-step instructions with screenshots A s

Currently, External Lookup fields support JSON-based data sources, but only a single property can effectively be used/returned. This becomes limiting in real-world integrations where systems require a stored value that differs from the user-facing label.Example:[ { "label": "Not Applicable", "value": "not_applicable" }, { "label": "Brand New", "value": "brand_new" }]Today, we can only expose either the label or the value. In practice, this forces us to expose technical/internal values to end users so downstream systems can properly consume the data.A common example is AEM Tags:label → human-readable value shown to users value → internal identifier/path required by AEM for storage and integrationsWith the current limitation, users see implementation-specific values instead of clean UI labels because the native connector must send the correct stored value to AEM.Suggested improvement:Allow External Lookup fields to:display one property in the UI (e.g. label) store/send another property

I was recently configuring maintenance tasks in AEMaaCS and ran into several gaps in the official documentation.Documentation explains the concepts, but some practical aspects are not very clear, especially around:• YAML-based configuration of maintenance jobs• How these jobs relate to the maintenance window• How to test them locally, since YAML configs are not supported in the SDK• How (or if) it’s possible to verify execution by yourself via logs in AEMaaCSI had to raise an Adobe support ticket to fully understand the behavior.After going through the full setup, I documented everything end-to-end - including configuration and testing approach.Sharing it here in case it helps someone else working with AEMaaCS maintenance: https://medium.com/@nikitamitroshin/maintenance-in-aemaacs-a-complete-setup-guide-7580dd67b770Comments and feedback are welcome!

 Ever see this in a Smart List filter?The 2 options look the same to the naked eye. And whichever one you choose, you get the same results on the People tab. Yet records with the first value will prevent the person from syncing to SFDC because it’s not in the corresponding picklist! See, due to a malformed CSV import, there’s an extra U+2060 WORD JOINER before the G in the first option. That character is by definition invisible, so it makes sense that they look the same in the UI. (Though note several visible whitespace characters have the same behavior.) They also look the same in the person detail:I call this Schrödinger’s whitespace (or whitespäce to be more metal): it’s either absent or present depending on how you look for it.in Smart Lists, Marketo trims whitespace when creating the underlying database query, which is why the People results are the same but the character is still there in the database, so when you sync to SFDC — and this is absolutely, 100% appropriate! — the att

Are you passionate about AEM and eager to share your expertise with the community? The Adobe Champion Program recognizes our most knowledgeable and passionate practitioners—those who help drive product adoption by:   Sharing technical expertise, best practices, and strategies with the broader customer community.  Collaborating with Adobe teams through product feedback, beta testing, and roadmap discussions  Each year, 40 AEM Champions are selected through a rigorous application and review process. Will you be amongst the 2026-2027 class? Join our live webinar to learn more about the program, benefits, selection process, and how to make our application stand out. Whether you're a seasoned expert practitioner or an aspiring leader in the AEM space, this is your opportunity to unlock the Adobe Champion advantage.   Date: Thursday, May 14, 2026    Time:  9am PT | 12pm ET | 6pm CET  Register here:  https://engage.adobe.com/adobe-dx-unlock-champion-advantage.html?trackingid=4SC98SFY&m

  In my recent project I extensively worked with Permission Sensitive Caching and Closed User Groups, aka. CUGs. It turned out to be a little more complex than I anticipated. So I started a 6-part article series to document and share my learnings: Part 1 — Using Closed User Groups to Control Access Part 2 — Setting up the Dispatcher and CDN for Permission Sensitive Caching  Stay tuned for more to come. 

Just published a long-form article sharing lessons from 10+ years of AEM implementations,including AEM Cloud migration patterns, service user pitfalls, performance at scale in regulated environments, and where AI is taking AEM next.Would love to hear from others in the communitywho have gone through similar migrations especially in regulated industries.https://medium.com/@merupulaakhilgoud/from-aem-5-6-to-aem-cloud-what-10-years-of-enterprise-cms-taught-me-about-building-for-scale-1c6040b09e1e 

Hi Marketo Community 👋I’m a Marketing Automation Manager looking to either adopt or evolve a better translation and localization process for email, and I’d really love to learn how others are handling this—especially at scale.Our current stateWe start with an English source and translate + localize into seven languages Translation and localization are handled in-house via cross-charge, with localization (rightfully) costing more After translation, my team then builds separate emails in Marketo for each language Most of this work supports nurture programs, so each project can involve many translated email buildsWhere things get difficultNative-language review is non‑negotiable. We strongly believe content must be reviewed by someone fluent in the target language to ensure accuracy, tone, cultural nuance, and brand alignment. That said, finding native speakers is a challenge in itself: It adds cost Reviewers are often outside marketing or Marketo If we rely on internal native speakers

Currently, setting the default filters and groups in a Layout Template > “Home” > “Widget Settings”, changes the default filter for all areas of Workfront. IE if a user is on a layout template where the default grouping for the “My Tasks” widget is set to “Project”, all areas of Workfront where the user views tasks will be grouped by project. This is simply a poor UI choice - these settings should either only affect the home widgets, or they should be moved to a section of the UI that indicates they affect the entire system.

As the Workfront Second Quarter Release is scheduled for next week (April 16 - Quarterly Release, April 15 - Monthly/Fast Release), this webinar highlighted a handful of enhancements coming to Advanced Enterprise Operations, Unified Approvals (the future of proofing in Workfront), Reporting, Fusion, and Workfront Planning. There are several demos in the on-demand recording, so it’s a bit longer than usual - plan for 75 minutes unless you watch on 2x speed.  If you weren't able to attend - no worries! The links to the slide deck, recording, and Q&A are listed below. Be sure to review the release notes on Experience League, as not all feature enhancements were covered in the webinar today!  Webinar Recording  Slide Deck PDF - note that the videos cannot be replayed in the slide deck PDF, so I’ve included links to those below  All videos from the section, Advanced Enterprise Operations Enhancements, can be found here - Financial Management (slide 18), Enhanced Layout Templates (sl

Adobe is repositioning Marketo from a campaign execution and lead management platform to a more AI-native, agent-driven platform. Below are the key summit updates and what they mean in practice. 1. Marketo + MCP ServerMarketo is introducing a native MCP (Model Context Protocol) Server that enables you to securely connect your instance to enterprise AI platforms such as Claude, Copilot, and other MCP-compatible AI systems.This means:You can build custom AI agents on top of your own Marketo data Your data remains within your environment (no external exposure) Marketo becomes part of your broader enterprise AI ecosystem Cutting down the constant switching between toolsThis essentially opens up Marketo for AI innovation without compromising security or governance. 2. Callable AgentsMarketo is moving toward an agent-first model where AI doesn’t just assist, it executes.These agents can:Run within Smart Campaigns as callable steps Automate repetitive operational tasks Identify data gaps and

Just been going through some of the announcements from Adobe Summit 2026 around AEM as a Cloud Service and wanted to get a real-world pulse from folks actually building on it day to day.A few things I’ve been thinking about after working on enterprise AEM Cloud implementations:The Edge Delivery Services push is getting louder but I’m curious how many teams are actually migrating existing Sites implementations versus greenfield only. In practice the replatforming effort is significant and I haven’t seen a clean story for brownfield migrations yet.Universal Editor is getting a lot of attention but author adoption in enterprise environments has been mixed in my experience. Has anyone actually rolled it out to a large non-technical authoring team and how did that go?On the pipeline and CI/CD side, Cloud Manager has improved but environment promotion still feels like it needs work especially around content variable management across stages.Would love to hear from others are these things you

In AEM, the language dropdown in the tag editor (Settings → Tags → Edit → Language) shows only a small subset of available languages, even when all language nodes are correctly defined under /apps/wcm/core/resources/languages.SolutionThere are three possible root causes:Missing or incomplete languages[] property on /content/cq:tags — the tag UI reads this property directly to populate the dropdown. Add it to /content/_cq_tags/.content.xml in your ui.content module. Use mode="update" in your filter — not mode="merge", which silently skips property updates on already-existing nodes. Language locale not defined in AEM — overlay the missing locale under /apps/wcm/core/resources/languages in your ui.apps module. Permissions — add rep:readProperties allow ACE on /content/cq:tags for the relevant user group via Repo Init.The most common culprit is #1, combined with the merge vs update filter mode confusion. Full write-up with code snippets and filter mode comparison:Why Your AEMaaCS Tag Trans

DescriptionThe ability for a Workspace owner to hide a panel within Workspace. Why is this feature important to youThere are two main reasons:(1) Temporarily stop sharing a specific panelToday, I faced a situation where, due to an issue with data coming from Web SDK ingestion, a panel shared with employees across my organization was displaying inaccurate data.Until the ingestion issue is fixed, the only available solution is to delete the panel entirely, which means I will later need to recreate it from scratch.A “Hide Panel” feature would allow Workspace owners to temporarily disable visibility of a panel without losing the work already done. (2) Facilitate report developmentConsider a project with multiple panels already being actively used.If I need to develop a new panel, this currently has to be done outside the existing project to avoid exposing incomplete work to users. Once development is complete, the panel then needs to be recreated manually inside the production project.A “H

I had the pleasure of speaking at an Experience League Community AMA at Adobe Summit this year, and I wanted to bring the conversation here for those who couldn’t make it. This is the kind of thing I genuinely wish someone had told me before we started.AEP on AWS  - Summit AMA RecapThe ContextWhen we set out to implement Adobe Experience Platform (AEP), the working assumption was that it would behave like any other cloud deployment. It didn’t. AEP’s defaults around networking, identity models, and tooling integration had been built against a specific cloud environment. That wasn’t documented anywhere, it was something you discovered by running into it. In our case, we discovered it during an architecture review, well into the project, not in a test environment.On top of that, Real-Time CDP and Customer Journey Analytics had to go live at the same time. That meant every foundational decision from schema design, identity resolution to data integration had to be right for two production s

Join us for this upcoming session including Q&A time with Vengadesh Shanmugavelu, AEM Champion and certified AEM Architect and Lead Developer.Learn From Your Peers Webinar | Adobe Experience Manager Assets WebinarDeliver Once, Delight Everywhere: Scaling Omnichannel Experiences with Adobe Dynamic Media Are you wondering how to streamline the transformation and optimization of your images and videos in AEM Assets?In this Learn from Your Peers session, Adobe Experience Manager Champion Vengadesh Shanmugavelu will share:How Adobe Experience Manager Dynamic Media enables intelligent media distribution using profile settings, smart renditions, and real-time optimization. How to activate Dynamic Media through AEM Core Components and extend its power across the enterprise using Dynamic Media Open APIs.Whether you’re a marketer, architect, or developer, this webinar will show you how to deliver once and scale everywhere with performance, consistency, and control. Date and Time: Thursday, M

If you just got back from Adobe Summit 2026 (or wished you had), this is the event you don't want to miss. The Workfront WUG – Southern California is hosting a virtual after party on May 12, 2026 — and we're skipping the polished recaps in favor of the real conversation.What announcements will actually change how your team works? What's worth bringing back to your org — and what's just hype? Our expert panelists are ready to give you their unfiltered takes on Workfront, content supply chain innovation, and AI. No fluff. Just clarity, candor, and a little healthy debate.🗓️ May 12, 2026 | VirtualAll chapters, members, and guests welcomeRegister here: https://workfront-augs.adobe.com/events/details/adobe-workfront-wug-southern-california-presents-spill-the-tea-adobe-summit-2026-after-party/Mega-WUGs are special virtual events where all Workfront User Group (WUG) chapters are invited. Not familiar with WUG?  Learn more here.

I’m curious who is using Priorities and whether it’s working well for your team. I’ve been playing around with it for a while and really like the UI and overall functionality, but it still feels a bit too “clicky” for me to comfortably roll out to our teams.For example, our Creative team lives in their assigned tasks and frequently jumps into the project custom form to view requirements/details. In Priorities, it seems like they need to click into the project name and then click “Go to details” from the side panel to get there. Am I missing an easier way to navigate this?Would love to hear how others are using Priorities in similar workflows/scenarios.