Adobe Analytics

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.   

Description - CJA/Derived Fields: Internal URL Filter for Marketing Channels, new feature requestWhy is this feature important to you - I'm setting up our Marketing Channels on CJA using Derived Fields, as part of our migration from Adobe Analytics to CJA. While in the process, I noticed that there is no option to set up Internal URL Filter in the derived fields. We have many internal sites in the company, and we need to be able to categorize them as "internal traffic" in our marketing channels, so that it doesn't mess up our marketing channels reporting.How would you like the feature to work - exactly as it is currently working in Adobe Analytics: the possibility to add internal URLs, and to later use them in the marketing channels processing rule builder (screenshots attached). Current Behaviour - there is currently no behavior on the derived fields. 

Description -We would like some groups to have the ability to see Data Views and their configuration without having the ability to modify. Current Behaviour - users without edit/modify permissions cannot see data views.

Description - Implementing the Analytics CNAME involves creating a subdomain for our website, which is then utilized to place cookies in a first-party context. However, during SEO crawling, these subdomains are scanned as well. To prevent Google from crawling these subdomains, we need to make adjustments to the robots.txt file located within it. Yet, as end users, we lack the capability to perform this task on our own and require assistance from Analytics Engineering to handle it on our behalf Why is this feature important to you -Search engines like Google allocate a crawl quota to domains, determining the time and resources dedicated to indexing a website. If these crawlers expend their resources on redundant URLs, like CNAME subdomains, there's a potential for vital content on our site to go unnoticed during indexing. This poses a risk of missing out on organic traffic if the crawlers neglect new or updated content while focusing on less crucial areas. How would you like t

Description - CJA Derived Field Lookup() funcion support on schema array field Why is this feature important to you - Lookup for array field is a powerful feature for many use cases How would you like the feature to work - The Lookup() function should be able to take an schema level array field as input, and output an array with lookup names Current Behaviour - Currently it's not supported. But Lookup() function seems somehow have this functionality as it can take the array field outpt from the Split() function.

Description - As a user, we would like Adobe to provide us access to the robots.txt file of our analytics subdomain so we can prevent search engines from crawlingWhy is this feature important to you - Googlebot is crawling resources on our adobe hosted analytics subdomain millions of times a week. This is hurting our crawl budget, resulting in less traffic and revenue to our eCommerce sitesHow would you like the feature to work - We would like the robots.txt set to Disallow allUser-agent: * Disallow: * Current Behaviour -  The robots.txt file is set to Allow AllUser-agent: * Disallow:

Description -This feature would introduce a new settings panel within the CJA interface for stitched(FBS/GBS) datasets. This panel would provide clear visibility into the configuration and schedule of the stitching process, including the lookback window, replay settings, and the timing of data processing runs. Why is this feature important to you -Data accuracy and trust are fundamental to our analytics practice. Without knowing when the CJA dataset was last stitched or what lookback window was used, our stakeholders cannot be confident about which day of the week contains the most complete and accurate data. This ambiguity undermines our ability to make timely, data-driven decisions. It also creates an unnecessary dependency on the Adobe support team for basic information about our own data configuration. How would you like the feature to work -Within the CJA Data View settings, there should be a new tab or section dedicated to "Stitching Configuration". This

Description - When building a freeform table with a subset of a dimension (either using a filter, using display only selected rows, or dropping individual dimension items), if you try to make a line/area visualization that is trended over time from the summary row it uses the entire dimension and not just the items that you've dragged in. This is a problem because it isn't accurately trending the dimension items that you have selected, it is including information that is not in the table and leads to an inaccurate representation. You can see here, with the header/summary row selected, it's trending the entire dimension, because the total for some of the single days in the line graph is greater than the total for the two weeks in the table.    Why is this feature important to you - This feature is important because when building out trended visualizations, we rely on having accurate information displayed. There are times that we need to trend the sum of a couple items from a

Hi Adobe Team, It would be great to have the ability to manually set the cookieDomain in WebSDK (noting that there was previous functionality in Adobe Analytics that allowed for this). We have noticed that in our implementation in some environments the AMCV and kndctr cookies are being placed on the incorrect domain. Adobe Engineering Support has explained that it is because the Web SDK does a guess and check approach that finds the shortest set of subdomains that will accept cookies (based on the publicsuffix list). If a domain is on the list, you cannot write cookies for any of it's sub-domains as the cookies will be incorrectly placed on the main domain, rather than the sub-domain. This is problematic if you require separate cookies to be placed on each separate sub-domain.  Currently there appears to be no way to manually set the cookieDomain, as mentioned in the following documentation:"The Web SDK can determine the correct cookie storage domain witho

The older version of the API, 1.4, allowed us to download a JSON of the processing rules in a suite.  Since these are instrumental in transforming data into eVars, Props, and Events, they are an essential part of maintaining the data quality of a suite.  The newest version of the API, 2.0, does not currently support accessing the processing rules, and it's been stated on Github that, as of this idea submission, processing rules access is not even on the roadmap.  Unless Adobe is going to eliminate these rules (and the eVars and Props that are driven by them), a mature multi-site installation of Adobe Analytics, esp. across mobile and web, relies on a constant overview of processing rules for maintenance, QA, and to aid site and mobile app developers.Please make sure that processing rules are accessible via the APIs, not just in version 2.0, but in all future versions.  Leaving 1.4 up is not a complete solution, as Adobe may deprecate it at any point.

DescriptionWhen using the Adobe Analytics API 2.0 to pull the details of our evars, we also need to know the expiration type and merchandising evar status. Why is this feature important to youWe're currently migrating our projects that use Adobe Analytics API 1.4 to API 2.0, but this latest version doesn't return whether an evar is set as merchandising and what its expiration type is. This feature used to exist in API 1.4, and we still need it as we use the API to keep our documentation up to date. How would you like the feature to workInclude the following key/value pairs in the response:"expiration_type": "page_view","expiration_custom_days": "1","merchandising_syntax": "product","allocation_type": "merchandising_last" For example, evar25 should return this:  { "id": "variables/evar25", "title": "Internal Campaign Name (Product Syntax) (v25)", "name": "Internal Campaign Name (Product Syntax) (v25)", "type": "string", "category": "Conversion",

Description - Today, when the Experience Platform Debugger is used by a logged-in user, the component name is pulled right into the debug output, which is great: However, this could be enhanced by a lot by pulling in more details. Some things I would love to see there: The component description Expiration/Persistence settings for eVars List settings for eVars and Props Event settings Existing Classifications This would help to make the debugging experience much easier for less-technical business users. Maybe others have some more ideas? 😊

Description - When working in a Workspace Table, rows are sometimes custom segments or specific values from another dimension. They stay in order as long as you don't edit any of the metrics. However, when you start adding/removing metrics, the order of your table is lost and you have to rebuild it. It would be better to have a feature to lock your selections in place so they remain sorted in the desired order while you actively work in the table. Without this feature I am constantly having to manually re-add the dimension values or segments and it's a waste of time. It would be ideal if the "lock order" feature was available in the right click menu with the other options to copy/download/delete/create segment from selection, etc.

Description:Allow users to upload flat files (e.g., CSV or Excel) directly into Adobe Analytics for temporary, ad hoc correlation with existing data in Analysis Workspace.Why is this feature important to you:Often, analysts receive supplemental data from external sources — like media plans, call center reports, or offline survey results — that need to be compared with web or app behavior. Currently, there’s no easy way to integrate this data quickly for exploratory analysis. This feature would enable faster insights without relying on engineering or data ingestion processes.How would you like the feature to work:Users can drag and drop or upload a flat file directly into Workspace. They can map the file’s columns to existing Adobe dimensions (e.g., campaign ID, date, region), then use those fields like any other dimension or metric in visualizations. The join would be temporary and only available within that session or project, without affecting underlying data.Current Behaviour:Today,

Here is a list of uses cases where I would have loved a product-scoped container in the segment builder:https://analyticsdemystified.com/adobe-analytics/product-segmentation-gotchas/Here is a description of how it might work:https://analyticsdemystified.com/adobe-analytics/a-product-container-for-christmas/Here are other related ideas:https://forums.adobe.com/ideas/8709https://forums.adobe.com/ideas/10245

Description - When adding permissions for user you can currently give them Analytics Workspace access and the ability to create Segments and/or Metrics, however this same permission allows them to share reports, segment and metrics with anyone else. The suggestion is to split off the share permission as a separate permission(s). Why is this feature important to you - We're more than happy for users to create their own reports, and to create segments and metrics in order to complete whatever reporting or analysis they need. However these may not be documented properly or defined correctly so we want to impose governance and check reports/segments/metrics are defined correctly and are not copies of existing company wide segments/metrics, etc before anything is shared. Adding this feature allows us to reduce confusion around which reports/segments/metrics to use, guarantee they are correct, and give end-users greater faith then the data they see is correct. How would you like th

Description - A "week of year" dimension, that functions similarly to the "month of year" dimension item. "Month of year" allows for year-over-year comparisons at a monthly level and can produce a view where the user can see the raw numbers for current year and previous year along with the percent change between the two time frames.Why is this feature important to you - I would like to be able to do year-over-year comparisons at the week level where I can also see the percent change. How would you like the feature to work - In the same manner as the "month of year" dimension. The values could be 1-52 (sometimes 53) or even better, the month of year and week of the month, for example, "April week 1".Current Behaviour -In current state, I can only add a time period column, which allows me to see the raw metrics for each time frame but does not allow me to see the percent change.

Description - Unable to associate lookup dataset with multiple datasets within the same connection. Why is this feature important to you - It's such an important piece that is missing; if this is not given, I cannot make meaningful reports or spend more time creating my mapping in CJA.  How would you like the feature to work - Give the flexibility to associate lookup with multiple datasets.  Current Behaviour - While setting up connections, I am ingesting multiple event datasets, a profile dataset, and a lookup dataset in CJA. However, I can associate lookup with only one dataset. 

I recently created an SDR within the AA workspace project.  The thinking is that users should be encouraged to use the AA workspace tool as much as possible, as compared to generating an excel based SDR that has to be stored externally.   Some examples of what I built 1) a picture of the different sections of the SDR -    2) a picture of the different panels, one for each variable (props illustrated) indicated its number, its name and whether or not the variable is enabled   3) an overview of a specific variable details.   I get that there are some items in this example that might not be easy to automate, like the BRD reference number with a hyperlink,    but I think it would be great to have a tool in the AA admin areas that would generate an SDR template within Workspace grabbing all the information it can from the AA admin area report suite traffic and conversion variable screens.  UX:  The admin would click a button, the script wo