Product Communities

We are currently migrating from Adobe Analytics to Customer Journey Analytics (CJA) and would like to request support in enabling identity stitching for our setup. Our Setup: We operate a B2B lead-generation website. AEP Web SDK is implemented, and ECID is generated for all page views. Email is captured only at the time of lead form submission. We will soon be integrating Marketo and Salesforce data into Adobe Experience Platform using the RTCDP B2B schema, which will also feed into CJA.  Our Objective: Stitch anonymous ECID-based behavior with the email identity once it becomes available via lead form submission. Enable reporting in CJA that shows a complete view of the customer journey — from anonymous engagement to form submission. Avoid increasing profile counts in RTCDP based solely on ECID-based anonymous traffic (we do not want ECID-only visitors to create full profiles). Ensure that profile qualification only happens when a

Adobe Experience Manager (AEM) and Adobe Journey Optimizer (AJO) together provide a powerful ecosystem for delivering personalized customer experiences at scale. While AEM manages content and digital assets, AJO orchestrates customer journeys using real-time data from Adobe Experience Platform (AEP)..

Hello Community! Has anyone successfully used the “Create Record” automation available within Planning and been able to get linked fields to transfer between record types? The only options for creating record between record types is Name, Start Date, and End Date (we use a taxonomy workspace and link picklist there).

It seems that a bug was introduce in version 2.34.2 of the AEP Data Collection Tags AEP Web SDK extension, whereby the extension’s version number is no longer included in the xdm.implementationDetails.version value. Now the value is “__VERSION__+2.34.2”. In previous versions the value was like this “2.31.1+2.34.1”.This data has been helpful in attributing the root cause of observed issues in collected data back to a specific version of the AEP Web SDK extension. How do we go about getting this bug fixed?

We are looking for some help as we currently blocked in our tracking implementation of this Adobe target server side implementation. We can successfully retrieve a4tpayload/tnta from the backend and sending in the first analytics call through global page rules, but it never appears on the first Analytics b/ss call also nothing appears in the Analytics report either

I posted something about this a while ago. However, the problem just keeps getting worse. I’ll trigger a scenario I’m working on by performing an action. The automation will run. And regardless of it runs successfully, it errors out, or returns a warning, I’m waiting for minutes before I can see what’s actually happening. I’m not the only person on my instance who is experiencing this. My colleague in a different business unit has to deal with the same latencies.Yeah, I know that if you trigger individual modules when building, you get an almost instantaneous turnaround with execution data. Yeah, I know I manually start an automation, I’ll get execution data almost instantaneously. However, I’m in the midst of building a complicated automation which requires it get triggered from inside of Workfront. Every time I run it, I have to wait between three to five minutes before I get any data back. And even when I get a failure pop up on my screen, I’ll go to the scenario where I’m still wai

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

Hi everyone,I’m working on a schema configuration and have run into a question regarding field group inheritance and Profile enablement.The Setup: I have a Custom Field Group containing Field A and Field B. Field A was marked as "Required" at the Global Field Group level (it appears as mandatory in every schema it is added to). In my specific schema, I have designated Field B as the Primary Identity. In most other schemas across our organization, Field A is usually the Primary Identity. The Question: If I enable this schema for Profile and begin ingesting data, will my local configuration (marking Field B as Primary) have any "upstream" impact on the Field Group definition? Specifically, will Field B suddenly become a required field for other schemas using this same Field Group?Also, since Field A is "Required" at the group level but is NOT my primary identity in this specific use case, is there a recommended way to handle this during ingestion if Field A values aren't the focus

We have several product fields (multi-select dropdown) on custom forms used by different groups. One group would like to adjust the fields by adding new choices on them that won’t apply to the other groups. No deletion or renaming of existing choices is needed. These fields have been used on thousands of requests and projects by the group, and I’d like to keep that data intact for them. I know that changing the fields will change them on all the other groups’ forms. I’ve tried making copies of the fields in Preview to see if the copy carries over the original field’s selection, but it didn’t work. Is there a way to copy the existing fields for this group’s forms (requests and projects) so that the copies retain all of the previous entered data while also allowing me to add the new choices they requested?

I am trying to create configuraion to purge workflows which are older than 100 days for AEM as clouds service.Documentation -https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/maintenance Above link says to create a node under /conf where as the link below asks you to create node under /apps for maintenance window.Sample configuration - https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-25921#environment  I'm trying to determine the correct way to create a maintenance window. I used the sample configuration and it worked, but after reviewing the documentation for second time, I realized that the maintenance window is supposed to be created under /conf. So what is correct place to keep this configuration?

Assume that I have two dasets and both have the field with same path:xyz.path.FirstNameI know that in AEP that field would be taken into profile depending on the merge policy. However how that field would be treated in CJA. That would be two columns?How would I know the source of the particular field (if it comes from dataset 1 or dataset 2)? 

Hi All,Quick question - can we get the report as attached as the end result from the data pull in Marketo power BI analytics?  Please share your thoughts!Thanks!

Hello Everyone,I'm new to Adobe Analytics and have created a rule for page load using a specific custom event called 'page load', triggered via Adobe Client Data Layer - Data Pushed. This rule works perfectly in all lower environments. However, in the Prod env (including the author environment), the rule triggers only once—when the page is loaded for the first time. On subsequent page loads, the rule does not fire.Additionally, I noticed that the prod launch script includes headers likecache-control : max-age=3600etag :"1e97f6ab69caa332353cdff72029d3f5:1752060858.688733"server: AkamaiNetStorage What could be the reason ?? I am not able to reproduce in lower env.  

I ingested data to dataset (I am AEP architect so its really there :). At least 100k records. Then sent it to CJA - I mark the backfill. How can I futher debug? Its already 8h so it should be there  

Hi Community,I'm looking for guidance on handling datetime values in Adobe Experience Platform where the source data is in local datetime but AEP's datetime datatype only stores values in UTC.The scenario:We ingest event data that includes timestamps originally in local datetime. Since AEP schemas require the datetime datatype to be in UTC format, the local time context is lost upon ingestion.However, when we use this data downstream for example, in personalization templates or email rendering we need to display the datetime back in the original local datetime format for the end user.My questions: Dual storage approach — Is it a recommended practice to store both a string field (preserving the original local datetime as-is) and a datetime field (in UTC) in the schema? This way, the string field can be used for display purposes and the datetime field for any time-based logic or segmentation.  Conversion functions — Are there any built-in helper functions that can convert a UTC datetim

Hi all,We’re using AEM as a Cloud Service CDN configuration where requests are routed to Azure Blob Storage using a one-to-one mapping between CDN YAML path patterns and blob container folder structure.kind: "CDN"version: "1"data: originSelectors: rules: - name: "page-origin" when: reqProperty: "path" matches: "^/(page)(/.*)?$" action: selectOrigin: "blob-storage-origin"Problem: When a path maps to blob storage but the file does not exist (origin returns 404), we want to display a custom 404 experience and it must support both locales:English 404 for non-/fr pathsFrench 404 for /fr/* pathsQuestion: Is there any supported way in AEMaaCS CDN YAML to:map/override origin 404 to a custom page/route (rewrite or redirect), anddo this per locale (EN vs FR)?We looked at errorPages but schema validation indicates only errorPages.spa is supported (no custom “rules” / mapping).If CDN config cannot do this, what is the recommended approach in AEMaaC

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.

Body:Hello everyone,I’m encountering an issue with a Page Rule in Adobe Analytics. The rule is configured with:Event: OneTrustGroupsUpdated Action: Send BeaconHowever, I consistently receive the following error: Failed to execute "Send Beacon" for "Adobe : Page Rule" rule. A timeout occurred because the action took longer than 5 seconds to complete. Error: A timeout occurred because the action took longer than 5 seconds to complete. Since the rule only has the event and the beacon action, I’m unsure why it’s timing out.Has anyone else faced this issue, or do you know what could cause the beacon to exceed the 5-second limit? Any guidance on troubleshooting or optimizing this setup would be greatly appreciated.Thanks in advance!