Hey @isaakskinner For the Authentication Endpoint, it depends on which type of Authentication is configured in the Developer Console Project (here you will have ClientID and Client Secret based on the type of Authentication).For Analytics, there are two: User Authentication and ServerToServerAuthent...

Hey @DanielWo8 In the example that you have shared, 3. Visit with ECID=abc (without visitorID) =>Visitor A (the same Visitor); the issue is if the visitor ID (set by s.visitor ID) is not present, then Adobe doesn't know if this is the same visitor reason being the ECID is based on the cookie and s.v...

Hey @SanyaTh1 To ensure visitors are stitched across subdomains, you need to implement cross-domain tracking using Adobe Analytics' built-in features. Here's the link for the same: https://experienceleague.adobe.com/en/docs/id-service/using/id-service-api/methods/appendvisitorid 

Offline tracking is supported by default when sending XDM Experience events since these events have a required timestamp, and there is no separate setting for this as it used to be in the Adobe Analytics extension. The events are backed up in the persistence layer and then sent to the Edge Network i...

Hey @Kayzee08 I was checking this as well, as far as I know,  IPv6 is yet to be fully supported in the Analytics. You might see values in some places, like the data feed for IPv6, but they are not available in the workspace or DW. So, not sure if it will work in the exclusion rules as well

Hey @AravindasamyR, I can think of two reasons, which are a large amount of Report Data or could also be due to the old Report Builder Add-In; please do check if you're on the latest (you can download the latest from Tools->Report Builder).

Hey @Vigin_George, Yeah, I agree, even I'm not able to download any of my older certificates. I reached out to support via the same portal, and as per them, it seems all you have is the share option now but no PDF download.

Hey @arpan-garg, Yes, even my understanding is that CJA does not directly pull data from the Profile Store.CJA retrieves data from the Data Lake in AEP. This means CJA is independent of profile TTL rules, as long as the data exists in the Data Lake.  I was checking this internally as well and found ...

Hey @arpan-garg AFAIK, If data is deleted from an AEP dataset (e.g., due to a TTL rule or manual deletion), it is also removed from the Data Lake. Consequently, this deleted data will no longer be available for CJA, as CJA depends on the Data Lake for its data. Connection is based on the dataset, so...

Agree with @Jennifer_Dungan , also this could be a bug. The new report builder in built on API 2.0, maybe there could be some differences. I would suggest to log a support ticket via Admin Console such that the product team can take a further look and address this.