@gautham_madala The Web SDK automatically tracks clicks on <a> and <area> elements inside open Shadow DOMs. However, clicks inside closed Shadow DOMs are not tracked, as their internal structure is hidden from JavaScript code operating outside the component. You may want to implement custom solution...

@VivekVe1 In short yes, using the same launch property on the subdomain is first step. You will then need to ensure subdomain and domain using same visitor id (ECID) to identify users else your subdomain user visit will inflate visitor count and thus visits. @KumarRishii  suggested few steps on usin...

@SantoshRa5  Short Answer -  Yes, calculated fields are super handy but using calculated fields in your dataflow mappings mainly when you're working with large files, can impact ingestion performance depending on how complex the logic is.  However, AEP is designed to handle such workloads. A few bes...

@KevLa1 It is possible the rule did not have enough time to fire before the new page loads. Try checking the box within the rule identifier indicating ‘Delay link activation’. A delay keeps the activated link from loading until the rule has fired. Note: This setting is only effective on actual link,...

@BrandonFa6  I see you are using OR condition, in that case, the Audience Evaluation on Audience B (in your example: Brandon Graeme Test Audience #4.4 TWC25E_250601 NEW SEEDS) will only return its count as Audience A (EMID NEW All Seed Profiles) has not yet been evaluated. In other words, OR conditi...

@Michael_Soprano Yes, you can definitely connect external tools to Adobe’s Observability API. Can use tools like Datadog, Azure Monitor, Workbook, logic app Splunk, Grafana etc. by pulling metrics via scheduled jobs, serverless functions.

@Tejasvi_mudumala  Try to temporarily create a new dataflow to the same Azure container and use different dataset (for test), now upload a new file with a unique name. This will helps you isolate whether the issue is with the file recognition logic, or a stuck state in the existing dataflow.   

@ChanuteJo  Even with Kafka, AEP's internal processing pipeline is not fully real-time in the way many of us will expect from other event-streaming systems. Adobe is not an event processing engine, but a profile-stitched platform and as of today stitching takes time. For true real-time use cases, co...

@SaurabhPa5  In AEP, Data Distiller and Query Service are closely related but distinct capabilities for working with data stored in the AEP Data Lake. This FAQ document answers your questions about Query Service and Data Distiller. It also includes commonly seen error codes while using the “Queries”...

@Rafael_Sahagun  Yes, keeping a SKU or product ID is still important mainly as a stable key for retroactive classification, data joins, and product-level analysis in both Analytics and Experience Platform. I'd recommend following - Keep SKU or product ID as a stable key Minimize real-time attribute ...