Adobe Analytics

Description - (I am sure this has been asked many times, so I just wanted to revive the idea) We need an automatic "Previous Period" date range component that automatically creates a dynamic lookback window relative to the selected date range on the panel.   Why is this feature important to you It is basically not practicable to have fixed previous date range components in place that only work until one changes the panel date range. Example Freeform table using the last 7 full days (Panel date range) vs the previous 7 days (custom date range in the workspace project). Now, someone decides to change the date range on the panel to "last 30 full days" Result the custom date range still displays only 7 days, the rest is 0 the comparability between panel date range and freeform table is completely useless this becomes even more obvious / erroneous if you are applying a summary change visualization on the two columns, not taking the same number of data points into consideration Ho

We should have the option to disable / remove the opt-out link in scheduled projects. We’re sending scheduled projects to distribution lists with 200+ recipients. But we can’t manually add 200+ recipients in the Adobe scheduler efficiently. Therefore we only have a single email address in the scheduler (an internal distribution list).Here’s the issue: everyone receives the same scheduled project containing the same opt-out link. If only one person of the 200 recipients clicks on the opt-out link the whole distribution list is removed from the scheduler which this is stopping the scheduled report for the whole list on almost a daily basis.

DescriptionThe executionMetadata helper function in AJO is extremely valuable for dynamically capturing and storing custom key-value pairs in the message execution context.In our organization, the primary use case is tracking user exposure to specific fragments and enabling downstream personalization logic without the need to create additional journey branches or duplicated nodes.However, currently the execution metadata is only populated in the Feedback dataset (Sent, Delivered, Bounce, Error, Exclusion). It is not populated in the Tracking dataset for interactionType events (Opens, Clicks, Spam, and Unsubscribe). Why is this feature important to youThis limitation significantly reduces the analytical value of execution metadata.Today, if organizations want complete reporting across both delivery and engagement metrics, the only viable option is to create separate journey nodes for each variation or fragment exposure scenario. This increases journey complexity, maintenance effort, and

Several reports, particularly the correlations, subrelations and complex filters take a good amount of time to fetch. The user ends up navigating to some other work / different site to use the waiting time instead of seeing the waiting icon, sometimes leading to a session expiry. It would be much more useful if the user could be educated and entertained that time in that time by showing up some DidYouKnow stuff about Omniture, some Omniture/SiteCatalyst IQ Puzzles, or simple small games like TextTwister, Tiles etc which could be paused and kept to side as soon as the report arrives. (Omniture - You could even use it to upsell Discover, T&T etc.) The Exit rates from Omniture would go down significantly if that is done.

First Touch Campaign: What It Is and How It Benefits Your Business A First Touch Campaign is a marketing strategy designed to create the initial interaction between a brand and a potential customer. In analytics terms, it represents the first marketing touchpoint that introduces users to a brand, product, or service.These campaigns are commonly executed through channels such as Google Ads, paid social, display ads, or organic discovery, and they play a critical role in first‑touch attribution analysis within platforms like Adobe Analytics and Customer Journey Analytics (CJA).The primary objectives of a First Touch Campaign are to:Build brand awareness Reach new or unknown users Create a positive first impression Initiate long‑term customer relationshipsBelow are examples of how First Touch Campaigns differ by industry.📈 eCommerce Industry – First Touch CampaignIn the eCommerce industry, urgency is often a key factor in the success of First Touch Campaigns. Consumers typically make fas

In the old Report Builder, it was possible to set a "reference date" when refreshing a report. For example, you could configure the report to show "last month" and then decide at refresh time whether "last month" should be calculated from today or from an earlier date. In the new Report Builder, this feature seems to be missing or only possible through multiple formulas.It would be very helpful if we could reference a "reference date" from a cell, so that the report calculations (e.g., "last month") are based on the date specified in that cell. This would make it much easier to analyze data from different time perspectives without having to adjust multiple formulas.

DescriptionCurrently, Adobe Analytics 1.4 API provides several powerful endpoints that allow administrators to manage report suite configurations programmatically. These include the ability to:Fetch and update eVars, props, events, and classifications.Retrieve configured processing rules for a given report suite.Adobe has announced that the 1.4 API will be deprecated in favor of the 2.0 API next year. However, these configuration-level features are not yet available in the 2.0 API. Once 1.4 is removed, these critical capabilities will be lost.For many enterprise-scale implementations, this functionality is not just convenient — it is essential. Proposed ideaExtend Adobe Analytics 2.0 API to include endpoints for:Variable Management: Create, update, and fetch eVars, props, events, and classifications at the report suite level.Processing Rules: Fetch and (if possible) update processing rules for a given report suite.Cross-Suite Comparison: Provide efficient ways to compare variable

 🧾 Description We are currently migrating from Adobe Analytics API 1.4 to 2.0 and have identified critical gaps that prevent us from fully deprecating API 1.4. API 2.0 does not provide feature parity with 1.4 in terms of report suite configuration and variable metadata, which creates a blocker for automation, governance, and documentation use cases.  🚨 Key Gaps  1. Missing eVar Metadata The API 2.0 /dimensions endpoint does not return essential configuration fields such as:  expiration_type expiration_custom_days merchandising_syntax allocation_type  These fields were available in API 1.4 and are critical for:  Automated documentation Data governance Attribution validation Migration verification   2. Missing Admin / Configuration Endpoints API 2.0 does not support:  Creating or updating eVars, props, events Managing Marketing Channel rules Accessing or modifying Processing Rules  Equivalent functionality existed in API 1.4 via ReportSuite.* endpoints.  🎯 Impact This

The Concept: In sourcing, identifying cost pattern shifts or rogue spend requires heavy week-on-week spend analysis and deflation tracking. Adobe Analytics has built-in AI for this exact type of monitoring.The Adobe Connection:Intelligent Alerts & Anomaly Detection: Instead of using these features just for spikes in website traffic, they can be configured on internal B2B platforms to flag sudden spikes in unclassified spend or deviations from contracted pricing structures.The Conversation Starter: "Adobe's Anomaly Detection isn't just for spotting a sudden surge in website visitors. Imagine applying that same AI-driven alert system to internal B2B portals to instantly catch 'tail-spend' leakage or week-on-week deflation shifts without manual Excel tracking."

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. 

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".