Welcome to the Adobe Analytics Community! Connect with peers to ask questions, share best practices, explore release updates, and contribute ideas that shape the future of Adobe Analytics.
Attivo di recente
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
I am an admin for Adobe Analytics and CJA for my company account. However, when I use Adobe Debugger, the below message has started to show when trying to validate our data on the website. I have tried checking my permissions, logging in and out of Experience Cloud & Debugger, I have also reset the debugger, as well as clear my cache and cookies for good measure. Does anyone know why this might be happening?
It would be useful to be able to use Regex when creating segments in Adobe Analytics to help segment based on patterns/sequences rather than on specific values. It would also prevent the need for building complex, “stacked” segments with multiple criteria/containers.
I’d like CJA lookup table dimensions to natively differentiate between "Unclassified" and "No Value".Using a Campaign ID (CID) lookup as an example: "Unclassified" (ideally customizable in the UI): The event has a CID, but that specific CID is missing from the lookup table (or the CID is missing the specific attribute) "No Value": The event does not have a CID present at all. Currently, CJA groups both scenarios under "No Value". While the Data View UI allows you to rename "No Value Options," it applies blanket-style to both types of events, so you lose visibility into unmatched lookup entries versus traffic completely missing the key.While this can be solved today using a derived field, native support in CJA lookup dimensions would eliminate the need for derived field workarounds, save contract derived field slots, and provide immediate clarity into missing lookup data right out of the box.
Setup: one Org, five Launch properties serving five subdomains under one registrable domain (www, oem, my, … .example.com). First-party collection via CNAME smetrics.example.com. ECID v5.5.0, AppMeasurement 2.27.Goal: each subdomain should start with no Adobe identity cookie before its own consent is given, and ideally identity should not be shared across the subdomains.What I've confirmed:The server (CNAME) sets both AMCV and s_ecid with Domain=example.com (registrable domain). These bleed to every subdomain. The ECID cookieDomain config scopes only the client-side AMCV to the subdomain; it has no effect on the server-set cookies. Setting it to the literal subdomain, the Set-Cookie response still returns Domain=example.com. (Adobe docs also list cookieDomain/cookieDomainPeriods as retired.)My open question:If I provision a per-subdomain CNAME (e.g. smetrics.oem.example.com as trackingServerSecure on the OEM property), will the collection server set the cookies on .oem.example.com, or
Hi,I am seeing a data discrepancy in CJA when building a 12-month YoY chart inside a panel locked to "This Month" (September 2026).Identical months (e.g., July, August, Sep) show completely different numbers for the People metric depending on the table setup:Setup A: Generic Month of Year dimension in rows + custom Jan 1, 2026 - Dec 31, 2026 column override. (shows 9.9K people for Aug)Setup B: Rolling date ranges in rows (This Month, 1 Month Ago, 2 Months Ago) + custom Jan 1, 2026 - Dec 31, 2026 column override. (Shows 6.8K people for Aug)Why does the time-parting dimension (Setup A) data mismatch with that of the relative date components (Setup B)?
With the new segment release on 23rd April 2014, it's become impossible to add multiple countries to a segment at once. We're now forced to add each country as its own rule, and when you're trying to build segments for entire market areas at once, this gets old very quickly. We used to be able to set a "contains one of" rule, that would allow us to space separate a list of countries. Can we please go back to doing that?Or at least find some way that doesn't mean I have to do three clicks for each extra country I'm adding? I'm trying to make segments with 50 to 70 countries in. So as to get a sense for how different areas of the world are behaving on our site, with this new UI that's an incredibly frustrating process.
Do you think excluding visits where:Page Views is less than or equal to 1 AND Time Spent per Visit - granular is less than or equal to 1 (second)makes sense? (The page views aren’t that much important to my question, Time spent is more)In my opinion, it kinda does. Because 1 second or less is extremely fast for normal human traffic. This started because I spotted obvious bot/crawler/uncommon traffic with those conditions on specific countries and domains. Which then left me wondering about the meaning of a 1 second (at most) visit…I believe it could be real people entering and immediately leaving. Either by clicking by mistake or other reason, which none seem ‘meaningful’ to me (at least at the moment).Another reason I can think of, is tracking set up problems, where the dimensions/metrics aren’t correctly populated. But confirming the tracking is properly set, and only thinking of Marketing/Traffic analysis, not on a developer/programmer analysis..Thank you in advance
Hi Adobe Community,We are currently working on optimizing a responsive web platform that serves dynamic HLS video streams alongside personalized media overlays using Adobe Target / AEM dynamic components.While the core dynamic media delivery works as expected, we are looking to fine-tune frontend performance—specifically reducing Layout Instability (CLS) during video player initialization and optimizing hardware-accelerated GL buffer management on mobile viewports.I’d love to gather insights from developers and technical architects here:1. What are the best practices for wrapping custom HTML5 / HLS video player scripts within AEM components without blocking critical-path rendering?2. How do you handle smooth component teardown and memory cleanup when switching dynamic video streams on single-page layouts?3. Any recommended client-side caching or lazy-loading strategies for high-concurrency video portals?Looking forward to hearing how other teams manage media-heavy, high-performance web
I am investigating an Adobe Analytics implementation issue and would appreciate guidance on understanding the root cause.Current SetupWe are using:Adobe Analytics Extension (AppMeasurement) Custom Tracking Server configured in the Adobe Analytics Extension AEM as a Cloud Service Author and Publish environmentsThe Adobe Analytics Extension is configured with: Tracking Server:smetrics.company.comSSL Tracking Server:smetrics.company.comBased on Adobe documentation for trackingServerSecure, my understanding is that Analytics hits generated by this implementation should be sent through the configured tracking server rather than Adobe's default collection domains.Observation #1While testing an AEM Author URL similar to:https://author-pxxxxx-exxxxxx.adobeaemcloud.com/content/site/page.htmlI inspected Network requests and found Analytics calls being sent to:amcglobal.sc.omtrdc.netwith report suite information resembling:amc.global.prodinstead of using the configured tracking server:smetrics.co
Hi everyone,We use the Next or Previous panel to analyse navigation, and we compared it with paths rebuilt from our raw data (page events ordered by timestamp within each visit). The results are very close, which makes this panel really valuable. But I think two options are missing to reflect real user behaviour:Include repeat instances. The panel uses the "Non-repeating instance" model, so consecutive views of the same page (e.g. a search results page reloaded after each date change) disappear. Flow already offers "Include repeat instances". Having the same setting here would make both views consistent. Show visit entries. When the page is the first of the visit, there is no previous page, and these occurrences are excluded. A "No previous page / Entry" row would let the previous pages add up to 100% of the page's occurrences.Today we work around this with a manually edited segment, but it has to be rebuilt for every page and panel, which doesn't scale.Would others find this useful t
Hello, Does anyone know if there will be a challenge for 2026? I know the 2025 was canceled.Thank you
The customer Journey Management > message Execution field group physically exists in both the AJO message feedback schema and the AJO email tracking schema. I can see the field in the tracking schema and build a CJA report against it. But at runtime, the value is never actually populated on tracking events.Since opens are tracking events, and tracking events never carries messageExecution. metadata, any CJA report keyed on that metadata for opens/clicks will be blank.I tried identity stitching for tracking and feedback events datasets in CJA with an Identity Map as EID in both datasets. But still unable to see engagement metrics (email opens and email clicks) when using the metadata LOB value filter for email opens and clicks in Email Journey Reporting in CJA. Is anyone facing a similar issue in CJA?
We noticed our original referrer data starting to get stripped which moved what would have been Natural Search traffic into Direct throughout the summer, but especially in early August. Are there any ideas on if this is related to the Safari 26 browser update tied to an iOS release, and are there any work-arounds to get that traffic back in under Natural Search in Adobe Analytics?
Hi all,I'm currently having trouble integrating traffic data from Adobe into our marketing platform (Datorama) using the 2.0 API.With the legacy 1.4 API, we were able to apply multiple segments within the Extended Properties section to filter the data. For example, excluding business-related visits, upgrade journeys, and other traffic types. However, in the 2.0 API connector, I appear to be limited to a single segment and cannot add additional segment filters.Can anyone confirm whether this is a restriction of the 2.0 API, or if there is an alternative approach to apply multiple filters/segments within a single stream?Any guidance or workarounds would be greatly appreciated.Thanks,H
Hi folks,For some of the pages, I am able to see Visits is greater than pageviews. Ideally this should not be the case, right? as per my understanding. but at overall level pageviews is greater than visitsThis started happening when i changed expiry of evar from visit level to hit(i breakdown page name with day and noticed this)Some of the notes :1. I am visiting website → accepting cookies → pageview fires first → and then engagements as i make so it seems no action is happening before pageview2. I am sending page name and URL with all my engagements (scroll and link clicks) as i want to know what happened on which page. Also can you please let me know if this is correct or do i need to change something in my implementation.
If you've ever opened your browser's network tab while debugging an AdobeAnalytics implementation, you've seen it: a long, ugly request to somethinglike /b/ss/examplecompanyprod/1/H29-abc123 or /ee/v1/interact, packedwith query params or a JSON body nobody memorizes on purpose. Tools likeOmnibug or Adobe's ownExperience Platform Debugger will decode that for you -- nicely, even --so you can eyeball it and go "yep, that looks right."That's the thing, though: eyeballing it is the whole workflow. There's nostep where a machine checks the hit and fails a build if it's wrong. Youship a change, the tag either still works or it doesn't, and you find outwhen an analyst asks why last week's numbers look weird.This post is about what's actually inside these two hit shapes, and why Iended up writing a parser (and then a few more tools) instead of justliving with the debugger-and-eyeball loop.Two generationsAdobe Analytics tracking comes in two flavors depending on what'simplemented:AppMeasuremen
We are investigating an issue related to Unspecified values and are trying to determine whether we're encountering a configuration issue, a data collection issue, or a platform limitation.In the example below, some conversions are successfully attributed to the menu-details dimension using Link Position, while 68 other conversions appear as Unspecified and cannot be tied back to a dimension.Why would some conversions be attributable to a dimension such as Link Position or Link Name, while others remain Unspecified? Is it reasonable to expect that most click-tracking conversions should be definable and reportable against a link dimension, or are there scenarios where Unspecified is the expected behavior?More specifically, can Target users define click-tracking conversion metrics using link-level dimensions such as Link Position and/or Link Name, and are there any known limitations that would prevent these dimensions from being available for certain conversions?
I’m currently reviewing the Adobe documentation about AI traffic in Analytics.Using this: Analyze traffic from AI chatbots | Adobe AnalyticsAccording to the documentation, hits are generated during AI Pretraining when our websites are scraped for training purposes. The documentation sates - You can use bot detection in Analysis Workspace to analyze AI traffic that comes from pretraining.However, there are no detailed instructions how to do it. Please advise, what are the steps?
Many content-rich websites with extensive knowledge bases are experiencing a significant increase in traffic from AI scrapers, crawlers, and data harvesting bots. In our case, this has been an ongoing challenge for several months. While the impact on reporting accuracy is already substantial, the more immediate concern is the associated increase in Adobe Analytics server call consumption, which can lead to unexpected overages and additional costs.What makes this challenge different from traditional bot traffic is that these are not a small set of well-known bots that can be managed through static signatures or conventional bot rules. The traffic is highly distributed, frequently changes behavior, and often originates from a large number of sources, making it significantly harder for customers to identify and mitigate on their own.Given the broad impact across digital analytics implementations, could Adobe consider a more proactive partnership model with customers? For example:Maintaini
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
What is the core difference? Field based works only in one specific dataset and graph based between datasets??
I am trying to track videos on a webpage. if webpage has 1 video, its getting tracked, but more than 1 video, when i am clicking on 2nd video. Its not getting tracked.Scenario : When i click on 1st video, its tracked, but 2nd video is not tracked. when i refresh and click on 2nd video. Its tracked but now 2st is not tracked. (Whichever video i click first gets tracked) This is the rule for youtube playback enable tracking. I searched on AI tools and it suspecting that problem is in this rule onlyfor 2nd video...you tube start is not happening even though all seems correctNote : The above code is for pageload irc frame in events
Description - When a users share a segment with a group of users or individual, there should be an option to decide edit rights - edit copy or edit original. Why is this feature important to you - Our Analytics community is mixed with foundational to advance users and we are often sharing components based on expertise level. This feature would help us to democratize more of the IP across teams. How would you like the feature to work - The sharing prompt should work much like workspaces. Edit copy - Edit Original- Read Only. Current Behaviour - Today we can only ask the user to clone segments from the components section, if they want any specific universal segments OR work based on trust that the user wont make an update and would be careful.
If you have just gotten access to Adobe CX Enterprise Coworker and want to learn more about how Coworker helps put your analytics data to work in new ways, this session is for you. Coworker brings the power of agentic AI to CX Analytics — so your team can investigate business questions in plain language, automate analytical workflows, and uncover deeper insights, all grounded in the data you already trust.Join our product team on Thursday, September 17, 2026 for a live session on Coworker's analytics capabilities. In this session, you’ll: Discover key use cases for Coworker on CX Analytics Learn best practices and tips & tricks to get started See real world examples of Coworker's analytics capabilities being put to use[Webinar] Unlocking Analytics Use Cases in Adobe CX Enterprise CoworkerThursday, September 17, 20268am PTSave your seat here: https://events.teams.microsoft.com/event/58c38075-bcc5-4c31-8b03-d5ab51ff0bec@fa7b1b5a-7b34-4387-94ae-d2c178decee1?source=copyLinkLegacyShareE
Hai già un account? Accedi
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
