Adobe Analytics

Description -We recently customised our calendar so that week now starts on a Monday and ends on a Sunday.However, the descriptions in the data dictionary haven't updated and include the sentence: "By default, this refers to the time period that starts on Sunday and ends on Saturday prior to the current week.".We cannot edit these descriptions in the UI as they are "Adobe provided components".We feel that the existing definitions are likely to mislead users. Why is this feature important to you -The current behaviour is misleading. How would you like the feature to work - Either: a) The descriptions of Adobe provided components such as "Last Week" can be edited by users, orb) If users customise their calendar to change the start date of a week then the definitions for these date ranges are updated automatically. Current Behaviour -The descriptions cannot be edited as they are "Adobe provided components".    

The existing time dimensions (day, hour, minute) in the DWH are not fine-granular enough for a few clients' use case.Therefore, they are collecting the user-timestamp in milliseconds in a custom prop as a workaround for this issue. But this workaround has some disadvantages:a) User timestamp collected in the frontend is local and sometimes incorrect (days or years in the future/past)b) For some server calls, the prop is not collected / missingc) This workaround depends on the data collection (server-side timestamp would be independent of front-end data collection).Can this be considered a possible enhancement, making the server-side hit timestamp available as a dimension in the data warehouse?With my basic understanding, since DWH is the post-processed data. Any data on the DWH is the outcome of the raw data.Hence, this particular enhancement should first be in the data feed because the current data feed shows second-level information.

Description - The derived fields UI to grab and persist a URL query parameter, for instance UTM parameters like "utm_source", "utm_medium", etc. seems rather counterintuitive, at least I have not managed to set it up successfully to assign a utm_source grabbed on pageA to pageB.  Which functions to use is a little unclear, and setting the persistence does not seem to work as expected. From what I have read, you will somehow need to check if the query param is set on pageB and if not, return the previous value?   It would be amazing if a working approach could somehow be baked into CJA derived fields function templates and call it something like "Get and persist query parameter" or whatever.   Why is this feature important to you - The UI should be as simple as possible and self explanatory. If there are multiple steps needed to come to a result, it would help to provide guidance or a template to avoid making "beginner" mistakes.   How would you like the feature to

For most normal dimensions you can only generate dynamic columns for the top 5 items.  5 is a very small number (I needed 8 the other day and was stuck!) - is there any chance of increasing this? If there are performance worries, even a small increase to 10 or 20 would be very useful! The feature can be seen here: Dynamic Columns In Analysis Workspace Freeform Tables | Adobe Analytics - YouTube

Description Love the Company Folder and the ability to share a group of projects across your organization, but want to potentially share only relevant projects for users and / or want to hide non-relevant templates and folders?  Current state, the Company Folder is an all-or-nothing holding ground for placing reports and enforcing automatic sharing privileges.  However, there are situations where you want only a certain team or group of individuals (maybe even product profile) to access a certain folder or even see that folder.     I'm proposing the idea of allowing users to create a "Shared Folder" that will let you set-up your own sharing permission that allows you to create a project and move to the folder and all members of the group will be able to access, but will not have to give carte blanche access to all members of your company.     Why is this feature important to you I often have a team of core people I work with for certain projects

Description - Apply attribution models to Data Warehouse exportsWhy is this feature important to you - So that we have an ability to automatically export approved data to vendors with the appropriate attribution in view.How would you like the feature to work - Be able to do attribution on metrics in Data Warehouse.Current Behaviour - You can only use Last Touch Channel as a dimension (with no ability to manipulate attribution window per report) and no metrics can be attributed.

Since the prehistory... In Adobe Analytics the possibility of sorting by dimension is something impossible.Now we have workspace and I really dream to have it.In freeform table we can sort by value we have in columns but not by value we have in rows. Please let's make it !! There are tons of reason why we need it. Try to think about a report where I'd like to have data sorted by Category of products, Zip codes, Order Id, Attributes of product...

Description - Ability to create segment based on calculated metrics Why is this feature important to you -  Sometimes a calculated metrics need to be used to get a more accurate segment How would you like the feature to work - In my case, I created a metrics of revenue with tax, which added 2 existing metrics of revenue and tax.  I then would like to create a segment of visits that meet a threshold of the calculated metrics. Current Behaviour - Calculated metrics cannot be used in segment creation.

Description - Ability to create segment based on calculated metrics Why is this feature important to you -  Sometimes a calculated metrics need to be used to get a more accurate segment How would you like the feature to work - In my case, I created a metrics of revenue with tax, which added 2 existing metrics of revenue and tax.  I then would like to create a segment of visits that meet a threshold of the calculated metrics. Current Behaviour - Calculated metrics cannot be used in segment creation.

1) Dimension Value Highlight Visualization DescriptionIt would be great to have a new visualization in Adobe Analytics / Customer Journey Analytics that highlights dimension values. For example, showing which product has the highest conversion rate or which page is the most viewed. The visualization would be similar to a Summary Number or Summary Change, but focused on what rather than how much. Why is this feature important?Currently, summary visualizations are excellent for showcasing key metrics, but they don’t emphasize the specific dimension value driving those results. Having a way to visually highlight the top-performing dimension item would make dashboards more insightful and storytelling more effective. How would you like the feature to work?Users could select a metric and a dimension, and the visualization would automatically display the top (or bottom) dimension value according to the chosen metric. Ideally, it would also support conditional formatting (e.g.,

It would be great to be able to have multiple dimension columns rather than having the information stacked. Currently whenever you breakdown dimensions it stacks this on a line by line basis which makes it harder to analyse and also looks messy for the end user.Example below

Description - For Adobe Analytics Data Warehouse exporting, I would like to suggest for an export option to a Microsoft Fabric Lakehouse as this is Microsoft's newest data platform. Our business use case involves analyzing the Adobe Analytics data alongside our existing 1st party data in Microsoft Fabric, and then using some outputs in our reporting.Why is this feature important to you - Microsoft Fabric gives us the most processing power for analyzing 1st party data. By being able to export Adobe Analytics data to a Fabric lakehouse, we can utilize that processing power to combine web behavior data with 1st part data for reporting and ad hoc analysis.How would you like the feature to work - Export option to Microsoft Fabric LakehouseCurrent Behaviour - Right now we can export to an Azure source then setup a data process that can take it from Azure and upload to Microsoft Fabric. Those are extra steps that slow down our ability to further ETL and analyze this data in a timely manner.

Description -Why is this feature important to you -i want to hide the shared components to some users which work in different bunsiness unitsHow would you like the feature to work -Current Behaviour -can share to all - but everyone will see all of the segments/calculated metrics that admin shares.  putting in user group will give users the ability to share to all users.  

Hi there, I'd like to raise a feature request on AA/CJA segments & components. DescriptionI’d like to suggest a few improvements related to traceability and governance of key components in AA and CJA, specifically for segments, derived fields, and Data Views. Why is this feature important to youThese features would greatly enhance collaboration across teams, improve auditability, and enable safer and more transparent management of assets within Analytics. In environments with multiple users and frequent changes, it's essential to track who made what changes and when, and to be able to recover previous versions if needed. How would you like the feature to workSegment change history: Ability to view a log of changes for each segment, with the option to restore previous versions. Ideally, this could be enabled selectively for specific segments to avoid unnecessary data load.Author and last modifier for derived fields: Each derived field should display who created i

Description:Introduce an option in Adobe Analytics Workspace filters (e.g., dropdown segments, panel filters) to enforce single selection only so users cannot apply more than one filter value at the same time. Why is this feature important to you:When users multi‑select from a dropdown filter or segment, some reports produce incorrect or misleading values. As an example, we use segments to isolate our Web and App experiences. However if a user selects both of these from a dropdown, they will get inaccurate values in the data set. Similarly, during gradual rollouts, mixing two experiences into one selection can lead the stakeholder to make decisions based on inaccurate values. A single‑selection restriction would ensure data integrity, especially in decision‑critical scenarios such as product rollouts. How would you like the feature to workAdd a setting to the filter/dropdown component in Workspace (e.g., a checkbox “Limit selection to one value”). When enabled, the filter beh

Hi, we are using data warehouse exports.The Files that we are receiving a quite big -> in avg. 1GB on hourly basis. Our db don't support ZIP format (the same like Athena, Redshift, Snowflake etc.), so we need to convert the files first in GZIP. Since unzip large files consumes a lot of time & ressources,  we would like to submit an idea:- add the gzip compression format to the exports- split large files automatically (like in Data Feeds) into smaller chunks of gzip files. It's actually the same way Data Feeds currently exports the data. Cheers,Piotr  

DescriptionIn a scatter plot we usually have two metrics and one is usually the independent one and the other dependant. In a line chart we have the ability to add various trend lines. It would be great to have the ability to fit a linear regression line to the scatter plotWhy is this feature important to youThis would provide the ability to spot relationships and trends between two metrics and highlight value that are outliers, either way above or below the line. This data can greatly help drive business decisions. How would you like the feature to workAdd option under the viz configuration "cog" to turn linear regression line on or off

Description - Have the date range comparisons update to align with selected dates for current time period regardless of date granularity and without need to go into the settings and adjustment comparison time periods Why is this feature important to you - allows for fewer and more flexible reports to be built for the teamHow would you like the feature to work - the custom time period is based on both the first and last date in the selection and updates automatically as the date range is updatedCurrent Behaviour - locked to the start date and requires going into the time range settings and adjusting the rolling time periods (much too complex for basic business user)

DescriptionThe Site Data Reference (SDR) is constantly evolving as new analytics needs come up. Right now, every change is handled manually — reviewing requests, mapping fields, and updating the schema one by one. It works, but it’s slow and makes it hard to keep different divisions aligned.Why is this feature important to youI’m responsible for tagging governance across multiple teams. The challenge is balancing speed with consistency. When requests pile up, there’s pressure to implement one-offs, which leads to fragmentation and extra rework later. Having a smarter way to spot repeat needs and streamline approvals would save a lot of time and prevent drift.How would you like the feature to workIdeally, the system could scan incoming requests, flag patterns that show up across teams, and propose new standardized fields for the SDR. From there, it should feed into an approval workflow so governance owners can decide what gets added. That way, divisions move faster but we still keep a s

Description - Currently if you are looking at a bar chart you need to hover your cursor over a bar to see details about that bar's total.  It would be easier to show bar totals/values at the tops of each bar. Why is this feature important to you - Ease of stakeholder consumption of data.   How would you like the feature to work -Allow bar totals to be toggled on and off.  Allow for a more simple Max/Min toggle for cases where there are too many bars.  Current Behavior - There are no displayed totals for bar displays without hovering over them.  

Description -Why is this feature important to you - instead of have 1 annotation for each of my 100 report / VRS, having this feature will allow 1 annotation. A specific annotation may be applicable to 100 out of my 200 RSID/VRSHow would you like the feature to work - Ability to select which report suites to be added to.Current Behaviour - Currently allowed to add to 1 or ALL

It would be great if you could customize a calendar on the Vi !rtual Report Suite level rather than only on the parent report suite.Example: Creating a virtual Report suite which has the week starting on Mondays instead of Sunday.

We're currently undergoing an exercise to fully automate our reporting. We have a number of scheduled reports (report builder) and projects (analysis workspace) that need to go external to our company, and as per company policy, I need to be password protect them before they can be sent.Would it be possible to introduce as system that would allow us to apply password protection to files as part of the scheduling tools?

Description Sorting for bucketed dimensions in CJA should default to logical sorting by the dimension's numerical value, rather than it's label. Buckets should be displayed more clearly (Less than 30, 30 to 59, 60 to 119, 120 or more) Why is this feature important to you Bucketed dimensions are intuitively understood when sorted in logical order by the value of the dimension. For example, shortest to longest time. It's confusing when two buckets are ambiguously defined and contain the same value (example: 30 to 60, 60 to 120). How would you like the feature to work Bucketed dimensions should default to logical sorting by the dimensions numerical value. At a minimum, users should have the option to sort by logical order. Example: If I have a bucketed dimension for time in seconds (Less than 30, 30-60, 60-120, 120 or more), I'd like the option to sort them logically as either:     Less than 30, 30 to 60, 60 to 120, 120 or more, or    &nb

If you delete a project it is permanent. Adobe should implement a 30 day recycle bin where you can restore your deleted projects.