Adobe Analytics

Current status: when you build a multiple data blocks in the same Excel file using report builder, it can sometimes be difficult to distinguish between them. It is currently possible to group them based on metrics, dimension, or what sheet they're on. But if you have multiple data blocks with all the same components but just different date ranges, it's very difficult to tell them apart in the list of data blocks.  How the feature should work: when making a data block there should be an option to give it a name. The ability to name data blocks will allow users to more easily distinguish between similar data blocks and make it easier to maintain their reports.  Why this feature is important: the new report builder has been such a huge upgrade from the legacy version, but it can still be improved upon. Having named data blocks will make it easier when trying to maintain reports and share them with others. 

Managing campaign tracking in Adobe Analytics (AA) is often more complex than in Google Analytics. While GA relies on standard UTM parameters, Adobe Analytics utilizes the CID (Campaign ID)—typically captured via the v0 or s.campaign variable—to track the effectiveness of marketing efforts.Here is a guide on how to transition from manual tracking chaos to a streamlined workflow using UTMMind.Part 1: The Dilemma of Adobe Analytics CID ManagementFor many enterprise teams, managing CIDs is a significant operational hurdle. Without a dedicated system, organizations often face the following "Tracking Debt": Inconsistent Naming Conventions: One team might use fb for Facebook, while another uses facebook_ads or FB-Paid. This inconsistency shatters your reports, making it impossible to see a unified view of channel performance. The "Mapping Table" Nightmare: Since CIDs are often cryptic strings (e.g., em_promo_20240501), teams rely on massive Excel or Google Sheets to "map" these IDs to huma

We have one app and several web properties tracked in abobe analytics. We use the LiveStream API to push our app and web data into an external repo. Mobile App ID is, in my opinion, the easiest and quickest way to segment out traffic to/within the app from the web properties.But Mobile App ID is not one of the fields sent in the Livestream API! Please do the engineering work to change that and include mobileappID in the livestream. You may be saying to yourself, now why don’t you just track them in separate report suites.. great question! I didn’t make the decision to combine them in the same suite - that predates my time here. 

Dear Adobe Team,we are currently in transition from AA to CJA and are migration a ton of workspace to from AA to CJA.However the process is currently not really perfect as only CJA Admins can be chosen as Owner of the dashboard and its elements.We are aware of the workaround of first put the ownership on an admin. transfer the workspace and then later use Asset Transfer in CJA to set the real owner of the workspace but this is problematic and error prone as identifying all assets which ownership should also change is a lot of manual work.i guess that is also a problem for other admins that are in the transition and want to make as easy for the previous AA users the transition to CJA in having full access to their workspace as the workload explodes by only having CJA Admins and not CJA User as Owner ins transfer available.KRMarc

I’d like to share feedback regarding the new Feeds UI, as the current default behavior is creating significant usability issues.Right now, the report suite filter defaults to a state where none of the report suites are selected. Because of this, users must manually select every report suite before they can see any feeds. For organizations with a large number of report suites, this becomes extremely time-consuming and makes the interface difficult to use.Ideally, the default behavior should either:- Show feeds for all report suites by default, or- Provide a more practical filtering option, such as filtering by active feeds.The current setup adds unnecessary steps to a workflow that used to be much more efficient and makes managing feeds considerably harder for teams with many report suites.Please consider revisiting the default filtering behavior to improve usability and reduce friction when accessing feeds.

Add the ability to store Internal Link Click information on main domain level.AppMeasurement Activity map uses a cookie(s_sq) set on main domain level to store information about the click from previous page, page name, link, region. The corresponding feature with WebSDK, Internal Link Click, only offers to set this information in either local storage or session storage, both stores data on subdomain level. Result is that Internal Link Click tracking doesn't work across subdomains. If your site holds e.g. www.website.com and secure.website.com Internal Link Click tracking won't work across.Would be ideal to be able to use a cookie for Internal Link Click tracking with WebSDK too. Sending Internal Link Clicks immeadiately and not use a grouping would duplicate the server calls and not an option.

Include thh Adobe consulting plugin Get previous value as part of the default Adobe product and also make it work across subdomains as this now only works isolated per subdomain. Get previous value is setting information in a cookie e.g. Previous Page Name, but does so on a subdomain level which makes the previous page name to not work properly across subdomains e.g. www.website.com and secure.website.com 

Description - Update the dimension operator in Annotations from AND to OR. Why is this feature important to you - Currently, if an annotation includes multiple dimensions, it only appears on a Workspace dashboard when all of those dimensions are present. If the dashboard contains only one of the specified dimensions, the annotation won’t be visible.For example, if I create an annotation using both eVar1 and eVar25, I must include both in the dashboard for the annotation to appear. To work around this, I have to create separate annotations for each dimension. How would you like the feature to work - Change the annotation logic so that it uses the OR operator. This way, the annotation will appear if any of the specified dimensions are present in the dashboard. Current Behaviour - Annotations use the AND operator, requiring all listed dimensions to be present for the annotation to display.

Sometimes, a collaborative dashboard can benefit from the Comments feature, but most of the time this is unnecessary and instead causes annoyance by opening frequently by accident as users try to scroll down through the workspace.While I can turn off comments individually on each dashboard, it would be much more convenient to default this to Off in Preferences and only toggle Comments section on when needed..

Looking to populate city, state, country, geolocation values to Adobe Analytics’ default Cities, Region, Countries dimensions. In this case, I would like to prevent Adobe’s IP lookup from populating these values, and populate the default geo dimensions to use geolocation information derived from my own application. Reasons for taking this approach -1 Adobe does not appear to handle IPv6 addresses correctly. Adobe Support confirmed this is the case.2 Better accuracy of geolocation Request - Add a method to overwrite the default geolocation dimensions in Analytics.

In the Old Report Builder if I shared a report which included a segment that someone does not have access to the UI shows a warning that the report contains segments not currently available to that userPlease add this functionality to the new Report Builder UI. 

Description - Being able to create a table with multiple dimensions side-by-side on a panel.Why is this feature important to you - It's visually more simple to track than comparing the breakdowns of your various primary dimensions across every dimension. You also then have no way to easily sort the top combinations to the top of your view without exporting the data and manipulating in Excel.How would you like the feature to work - Be able to drag multiple dimensions side-by-side, just the same as you can metrics.Current Behavior - You can only have one dimension in a table (unless the other dimensions are breakdowns). I can't create a flat table of multiple dimensions in the Analytics Workspace view.

DescriptionDynamic text visualization would allow the inclusion of dynamic fields (dimensions, metrics, segments, or date ranges) directly within text elements. This enables text to automatically update based on the context of the analysis, making dashboards and reports more interactive and informative. Why is this feature important to youProvides greater flexibility in storytelling with data.Reduces manual effort of updating static text when filters or date ranges change.Enhances clarity by showing contextual information.Improves user experience by making text responsive to analysis changes. How would you like the feature to workText visualization should support placeholders that can be linked to dimensions, metrics, or filters.When a user changes a filter (e.g., date range), the metrics displayed should automatically refresh to reflect the new values.Ideally, users can select fields from a menu or insert them via a formula-like syntax.Example: {{ date.range }} there we

 Why is this feature important to you - It would be very useful to see how many times a dashboard has been opened/used, by whom it was opened/used statisticsHow would you like the feature to work -We request the development of a user-friendly Workspace Usage Report interface within Adobe Analytics that allows admins to easily view and analyze dashboard usage metrics without needing to extract or parse raw logs.Current Behaviour - At present, dashboard usage can only be reviewed by accessing Usage Logs, which is not practical or user-friendly for administrators or business users who need to understand how dashboards are being accessed and utilized.

Description This question has come up multiple times in the last few weeks, and it probably surfacing in other channels as well, but there should be a way to filter the rows in a freeform table based on Metric Count. So only show items below X, or above Y, or between X and Y.   While we can filter rows manually via the "only show these rows" the values can change month to month, being able to only show rows based on a specific criteria seems like a basic function we should have, and yet don't as of yet.     Why is this feature important to you Values change month to month, so having to manually find and filter rows is a lot of effort that we shouldn't need. While, yes, we can use a calculated metric to change rows outside of a range using IF and Greater Than/Less Than logic (using a static 0 for outside our range), the rows, while no longer counting in the total, still show in the table.     How would you like the feature to work Either in the dimension filters

Non-Standard Marketing Attribution does not utilise persistence from eVars and Marketing Channel, utilising only the instance of each of these variables during the lookback window.  As such, there is a large "none" bucket for Marketing Channel, although Marketing Channel without using these non-standard attribution metrics does not contain a none - all channels are account for.  This is because the Marketing Channel Processing Rules sets channels based on what can or cannot overwrite previous channels.   For example - if someone comes via PPC and then via Direct - if the PPC is outside your look back window, but the Direct is not, the non-standard attribution would give credit to "None" because Direct was not set-up to overwrite any other channel.   Since the non-standard marketing attribution events ignores this persistent, it would be good to have an options for the following:1. Follow the Marketing Channel persistence, ensuring the last "paid"

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.