Product ideas | Community
Skip to main content

10000 Ideas

Michael_au
Michael_auNew Participant

Rolling Daily/Monthly/Yearly Active User Metrics + User stickiness metrics (i.e. MAU/YAU)New

Description - We wish to be able to create a table and line chart that contains a break-down by day which includes metrics to look back at the unique visitors for the past 30 days and 365 days, as well as including a user stickiness metric which will be defined as MAU/YAU. For example: Why is this feature important to you - Active users indicate that people are interacting with our app/website. Determining the number of active users over time helps us with assessing the effectiveness of our marketing campaigns and the customer experience.How would you like the feature to work - Out of the box Active User metrics (DAU, MAU [rolling 30 days], YAU [rolling 365 days]); Out of the box user stickiness metrics (DAU/MAU; DAU/WAU, WAU/MAU, MAU/YAU); Out of the box Workspace template that has the key active user and stickiness metrics trended over time; Ability to create custom active user metrics based on custom time frames - including rolling amounts and custom user stickiness metrics with the ability to trend per day based on the rolling amount. Current Behaviour - While we can use the Unique Visitor metric broken down by one of the out of the box date date breakdowns, it seems that it isn't possible to calculate the active users for a rolling date range, for example rolling 30 days up to and including the date that the UVs is broken up by. Trying to achieve this via the Cumulative Average Function doesn't dedupe Visitors that revisit the website within the same period.

kshamitha1New Participant

Get the references of product detail and recipe detail pages in adobe SaaS implementationInvestigating

Request for Feature Enhancement (RFE) Summary:   In the Adobe SaaS platform, product detail and recipe detail pages are implemented using the CIF framework, meaning there are no physical pages for recipes and products. The current issue is the inability to identify internal references to specific recipe detail and product detail pages. Use-case: When we try to unpublish SaaS says there are Referenced pages but does not give the list of referenced pages, this is a serious limitation. This feature existed on the previous D2 platform. In Unilever platform some brands have over 800 pages and webmasters keep adding and removing pages on a very regular basis. There are many pages where Product URLS are also referred. Whenever a page or product is deleted or removed we do add 301 redirects. If there is an internal link if we don’t update those links then when user clicks on the link it redirects a new page url, This is being flagged by SEO error. Before unpublish a page the System is showing error but it is not showing which pages have reference and we have no way of knowing and it results in SEO ranking. In D2 the PDP Pages were published as pages and we used to unpublish before deleting. In SaaS there is no PDP page unpublish as we don't have any physical pages for recipe and products , hence when a PDP is deleted or renamed we have no way of knowing. Current/Experienced Behavior: Currently we get notification that there is a reference for a page but the list of references are not provided Improved/Expected Behavior: Need a way to identify the internal references for a product and recipe detail page. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release :2024.6.16971.20240628T122619Z Customer-name/Organization name: Unilever Screenshot (if applicable):   Code package (if applicable):  

kshamitha1New Participant

OOTB RSS feed exposure to outside AEMInvestigating

Request for Feature Enhancement (RFE) Summary: Currently we do not have any end point from where we can get all details of the article data .A few brands use the search api endpoints to fetch article data for a brand-locale but that only gives limited data ( title , body text , url ) .Currently we have systems like AIBA which use article data to train their models to generate dynamic recommendations . To do so we need some end point from article which when hit , directly provides all data in the body content of the article Use-case: A structured data feed with a periodic synchronization enables AiBA recommendation engine and AiBA LLM engine capability to have latest content and avoid any incorrect recommendations and also avoid a manual process for feeding the latest updates in article content.Other initiatives currently being discussed for LLM and AI engine revamp may also benefit from this implementation. Current/Experienced Behavior: Currently there is no provision in the product for exposure of content feed outside AEM. The engineering team should review and implement this based on the priority for future releases. Improved/Expected Behavior: We need some end point from article which when hit , directly provides all data in the body content of the article Environment Details (AEM version/service pack, any other specifics if applicable): AEM release 2024.6.16971.20240628T122619Z Customer-name/Organization name: Unilever Screenshot (if applicable):   Code package (if applicable):  

ASSET-LINK - enable opening the asset shown/used/worked on in PS, IA, ID etc. directly in AEMInvestigating

Request for Feature Enhancement (RFE) Summary: When using asset-link, I can search for and use assets out of AEM directly in Creative Cloud Applications. But when I found an asset, I might want to check it's metadata, or check the folder it's in for other assets, and such. The asset-link UI is not good for such activities, and cannot do them.As such, it would be great to be able to directly open the asset directly in AEM - using the information asset-link already has to open the asset in the browser in AEM-ASSETS.Searching though cloudmanager for the right environment, then searching for the right asset inside of AEM is cumbersum and error-prone. Use-case: check/edit metadata of files used in asset-link review the folder the asset used in asset-link is in preview the edited  asset in AEM with renditions etc.  preview the edited asset in the experience the asset is for (website, etc.)  Current/Experienced Behavior: The asset cannot be opened in AEM using asset-link Improved/Expected Behavior: Being able to open the asset in AEM ASSETS in the browser directly from asset link. Environment Details (AEM version/service pack, any other specifics if applicable): all AEM versions, but especially Cloud Services. Customer-name/Organization name: Adobe Screenshot (if applicable):   Code package (if applicable):  

content_publisherNew Participant

enhance reporting features for Expired AEM AssetsInvestigating

Request for Feature Enhancement (RFE) Summary: enhance feature set for AEM Asset Reporting  Use-case: We propose the implementation of a new features in Adobe Experience Manager (AEM) that allows users to create custom report templates for asset management. These templates can be saved and scheduled to run at user-defined intervals, such as monthly. The primary purpose of this feature is to facilitate the generation of reports that scan for assets scheduled to expire within a specified timeframe and defined meta data parameters. Key Features: Custom Report Template Creation: Users can create and save custom report templates and use again. Templates can include custom metadata fields configured by the user. Scheduling: Users can define a schedule for the report to run automatically, such as daily, weekly, or monthly. Email Delivery: Users can register one or more email addresses to receive the generated report. The report can be sent as a PDF attachment or as a link to a dashboard in AEM. Interactive Reports: The report includes thumbnails of the assets. Users can interact with the report by clicking on links that direct them to the respective assets in AEM. This can be implemented as an interactive dashboard within AEM or as clickable links in a PDF report. Use Case Example: A marketing team schedules a monthly report that identifies assets due to expire within the next specific parameters. The report includes thumbnails and key metadata fields such as asset name, expiration date, and usage rights. The report is sent via email to the team, and they can quickly review the assets and click on links to access them directly in AEM for further action.   Current/Experienced Behavior: Not able to save templated reports and can only schedule once or execute now. Report need to be reconfigured each time used. Report not interactive. If exported from system thumbnails of images are lost. Improved/Expected Behavior: Create recurring report that has thumbnails of images and has live links to the assets in AEM. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

AG7New Participant

Cloud Managed Deployment Pipeline Feature Request : Allow pipeline to continue after publisher failureInvestigating

Request for Feature Enhancement (RFE) Summary: When a server fails to successfully deploy the pipeline aborts leaving servers in various states of deployment. Instead when a publisher fails, the failed publisher/dispatcher pair should be left out of rotation and the deployment should continue to the next server. A notification/incident is sent/created to CSE and customer. In an environment where there are 10 publisher/dispatcher pairs one server or even multiple servers failing can be left out of rotation and still serve proper traffic. The aborted pipelines in this case cause 8-9 hours of delays, sometimes days to resolve. This costs all parties a significant monetary and time loses. Please create a JIRA ticket and request for this. Keep me posted on when that is created and share regular updates on the progress of the request Use-case: In large infrastructures deploys can take 9-10 hours to completed.  One failure can cost hundreds of thousands of dollars in delays that can take anywhere from 12 to days of additional deployment hours, leaving part of the infrastructure in varying states of deployment.  Rolling back or manually deploying to the remaining servers is not an option as content over 9-10 hours already has a delta, and manually deploying 30 packages across 21 servers takes even longer.  This feature would reduce hours, and cost significantly as well as reduce the  production server downtime caused by deployment failures due to infrastructure reasons. Current/Experienced Behavior: There are 10 publish/dispatcher pairs.  The deployment fails on publisher 3 because publisher 3 is experiencing an issue or high load, when this happens the entire deployment is aborted.  This leaves publisher/dispatcher pair 4 thru 10 un-deployed, so now we have author, pub1 and pub 2 serving traffic using new code and the rest of the stack serving traffic on old code.  To redeploy the pipeline again using the re-execute feature can take another 10 hours.   Improved/Expected Behavior: When a non author server fails to complete deployment, keep that publish/dispatcher pair out of rotation and continue the deployment to the rest of the infrastructure.  Alert custom and CSE that a publisher/dispatcher is out of rotation due to a deploy failure.   Add a feature into the CM pipeline that allows the ability to deploy to a single dispatcher publisher pair, or any server in your infrastructure.   Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.21 : 21 server infrastructure, 1 author, 10 publishers, 10 dispatchers.   Customer-name/Organization name: Undisclosed Screenshot (if applicable): N/A Code package (if applicable): N/A