Hi @techkodainya  This type of issue usually points to the timing of when variables are being set in relation to when the tracking call is fired, rather than a true SDK race condition. If the pageName or eVar is not defined before the beacon is sent, the hit will go out without those values. Later i...

Hi @Jon_Maguire Even with permissions, the filter will only display if someone has actually shared segments with that user. Can you confirm if the users have shared any segments with each other?

Hi @jane_12 Adobe Analytics Data Warehouse doesn’t support sending reports directly to Azure Blob. The usual workaround is to either schedule delivery via SFTP into an Azure Blob container (by enabling SFTP on your Azure Storage account) or use the Analytics API with an automated job to fetch and up...

Hi @DebanjanaBh1    Page views on the checkout page and the scCheckout event aren’t quite the same thing. Page views will count every time someone lands on that page, even if it’s a refresh or they jump back in. scCheckout is designed to mark the actual start of a checkout attempt, so it’s usually c...

Hi @SwatiTi  The difference comes down to scope -   Hits (server calls) - every individual request sent to Adobe Analytics (page views, link clicks, events, media pings, etc.). Visits - a grouping of hits into a session, based on rules (30 minutes of inactivity, 12 hours max duration, 2,500 hits, ...

Hi @brentrad  CJA doesn’t have an out-of-the-box “Average Page Depth” like AA, so you’ll need to build it with available fields. The closest approach is - Use Event Depth (or a session counter passed via Web SDK) to capture depth per hit. Build a calculated metric: Sum of Event Depths (pageviews o...

Hi @JaniceAk  A derived field scoped at the Person level still respects the date range you set in Workspace. The scope just controls how events are rolled up (all events for that person), while the date range defines which events are included in that rollup. So in your example, if you look at Jan 1 ...

Hi @SeongHyunPa  Adobe Analytics will capture tracking codes based on the query parameter you’ve set up (e.g csref). If that parameter appears more than once in a URL, the platform takes the last occurrence, so in your example, only dsp:DEF is stored. If your use case requires both values, you’d nee...

Hi @AbhishekDhami I agree with @Jennifer_Dungan  There’s currently no direct replacement in the 2.0 API for extracting Processing Rules, that functionality only exists in 1.4, which is why your current approach works. For now, options are - Manual export & documentation which is not ideal for large...

Hi @AbhishekDhami Similar to what @yuhuisg mentioned. These values are mainly used to indicate the nature of the stream for reporting and analytics consistency: LIVE - Real-time broadcasts with no ability to pause/rewind beyond the live point (e.g., sports event livestream). LINEAR - Scheduled, fi...