Adobe Analytics

Currently, Adobe Analytics custom bot rules only support filtering based on User-Agent, IP Address, or IP Range. However, when modern browsers (like Chrome or Edge) send requests without Client Hints, Adobe replaces the un-vetted minor version with a .999 placeholder in the reporting backend (e.g., Chrome 148.999), which is surfaced via the standard Browser dimension.Because this fallback logic happens downstream from the initial User-Agent ingestion, we cannot reliably capture or block these specific spikes using standard User-Agent string matching in our Bot Rules.Why this is needed: A sudden spike in .999 browser versions is a strong indicator of low-quality or bot traffic. However, our data quality is currently suffering because we have no native way to translate this specific reporting dimension back into a bot filter rule. Relying on complex VISTA data engineering or shifting IP ranges is inefficient for dealing with browser-specific anomalies.Proposed Solution: Expand standard A

Adobe recently announced Sub-Hit analysis for Adobe Analytics. However, this feature will be limited to the Products variable, according to the documentation.Since many customers are using List Vars and List Props, support for Sub-Hit analysis for these dimension types is needed. Please extend this feature to those dimension types.

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

Currently, Workspace allows us to export reports in PDF and CSV formats. We would like to know if it would be possible to also add Excel (.xlsx) as an export option, as we are experiencing several issues when working with CSV files:- We work with program and video titles that contain commas. When exporting the report as a CSV and opening it to process the data, these titles are split into multiple columns, making the data difficult to work with.- For time-based metrics, the CSV export converts the values into seconds, causing us to lose the time format (hh) and preventing us from working with the data correctly.We would also like this enhancement to apply not only to report exports, but also to the scheduled delivery of reports in Excel format through both Workspace and Data Warehouse.Thank you in advance.

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.

At this time, there doesn’t seem to be any good options for copying Report Builder requests from one file to another. There is a Copy / Paste request option built into the Add-On which is amazing, but this only works within the same file. You cannot copy a request from one file into another. I tested this by opening and logging into two Excel Reports, copying a simple request from Report A, then going into Report B and selecting a cell… there was no Paste option available. I can understand that this might be an Add-On scope issue, but what about adding an Export / Import function that can export out an XML or JSON formatted file that can then be imported into another Excel instance… and hopefully this would support bulk rules and not just one at a time, as this would make merging reports into one large report so much easier (than the current “rebuild all requests from scratch”). This feature would be a huge time saver to:make copies of common requests to other files merging reports tog

Hi Everyone,I wanted to share a new Chrome extension I’ve been using called TagScanner that has significantly streamlined my Adobe Tags (Launch) auditing workflow.As implementation scale increases, keeping track of library bloat and rule dependencies can get tricky. TagScanner helps by loading all details about any Adobe Tags property directly from the page.Key Features:Direct Page Reading: It reads the Tags library directly from the browser—no remote code or extra permissions required. Comprehensive Visibility: Quickly view all active Rules, Data Elements, and Extensions in a single interface. Performance Insights: It displays exact file sizes and usage details, making it much easier to identify "heavy" rules or unused code that might be slowing down your site. Effortless Documentation: Perfect for cleaning up legacy properties or creating implementation documentation for stakeholders.It’s been a great addition to my toolkit for quick audits without having to dig through the Data Coll

We need the ability when we set up automated scheduling of reports to have an expiration date of “NEVER”. Its very inconvenient to have reports from either analytics or the new adobe report builder to aways hit an expiration date that has to be kept up with. 

Currently I can pull bot name as a dimension and bot pageviews as a metric in Analysis Workspace.  And I can pull IP address or user agent in Data Warehouse.  But I can't pull bot name or bot pageviews in Data Warehouse and I can't pull IP address or user agent in Analysis Workspace (at least out of the box) and breakdown bot name by IP. I would love the ability in either Workspace or Warehouse, (but ideally both), to be able to breakdown bot name by IP address/user agent, but right now there's not a great way to do that.Customer care confirmed this was the case.Here's a brief summary of our discussion for future references:You were looking to pull out bot reports in Data Warehouse. I informed you that its not possible as bots are excluded from the reporting. The Bot reports are only available in the Workspace and that too, separate from rest of the report suite data. Further, you wanted to enquire if its possible to pull out Bot Reports with IP Address or User Agent. Un

Teams who collaborate on Workspaces have a lot of potential issues to lose / overwrite work from others in their team. There is no “lock” feature to prevent multiple users from accessing and updating the same report at the same time, which can lead to lost efforts by the last person saving their version, and “wiping out” the other person’s work. There are lots of potential options to help mitigate this, and it may end up being a roll out of features, since there are definitely complications for designs. Options:At least show visually how many people (and maybe who) are actively on a Workspace at a given time… or at least showing how many people with Edit rights have access. This way there is some warning that you might be impacting someone else’s work when you are there. For multiple active users, if I make a change and try to save, there could be a warning that my changes aren’t the most recent… and maybe provide a way to merge the other recent save with my own? Implement a “Lock” tha

Currently the list of classifications on the the Classification Set page (in the new Classification sets interface) does not have an option to show if a classification is active or not. The old interface did.  Including that flag is useful to easily see which classifications, in a potentially long list, are currently active. To see that in the new interface requires two clicks to see the status and a third click to get back to the list. If one is working on a number of conversions you might want to see which you have not made live. Currently you have to click into each item in the list and keep a separate note (or have a really good memory) to keep track.

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 Adobe Analytics API 1.4 is scheduled for decommissioning this summer, yet critical endpoints from this legacy API have not been integrated into API 2.0. This creates a significant gap in functionality that will impact many organizations relying on programmatic management of Adobe Analytics configurations.Missing Critical Functionality:The most important missing feature is the ability to programmatically:Create new Adobe Analytics variables (props, eVars, events) Modify existing variable configurations Delete variables when no longer neededCurrently, API 2.0 forces users to manually manage these variables through the Adobe Analytics interface, which is:Time-consuming for bulk operations Error-prone for complex configurations Incompatible with automated deployment workflows Difficult to integrate with CI/CD pipelinesBusiness Impact:Without this functionality in API 2.0, organizations will lose the ability to:Automate variable management across multiple report suites Maintain consiste

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

!!NOT the same as being able to apply segment to calc. metrics!!Goal:Segment Visitors based on calculated metrics (such as  AOV)Problem:Calculated metrics is NOT available in Segmentation console.

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.