@pradnya_balvir we are even using CNAME which should solve this cross-site tracking prevention but I understand ITP 2.3 is detecting the CNAME and it is blocking Adobe Target, correct? https://experienceleague.adobe.com/en/docs/target-dev/developer/implementation/implement-cname-support-in-target#is...

Hi, We are testing adobe target (at.js 2.11.4) in all browsers and we have realized that in Safari(Version 17.5 ) if we enable: use advanced tracking and fingerprinting protection.(Advanced setting). Adobe Target will not work/load Is there any workaround? is Adobe Target team aware of this? Thanks,...

After more research we found the following: - Does Adobe Target guarantee stickiness forever?By default, it guarantees up to 14 days and it could be increased up to 90 days if the visitor profile is inactive for that period. Ref: https://experienceleague.adobe.com/docs/target/using/audiences/visitor...

Hi @remiller  Could you extend the lifetime up to 365 days? Thanks,Ricardo

Hi  @Rajneesh_Gautam_ We have raised the question (downsides on sending same value for both tntId and thirdPartyId to get stickiness) with support team and they are going to review it with Engineering team. In parallel, do you know if just using the the thirdPartyId along with the same sessionId gua...

Hi @Rajneesh_Gautam_ If we use sessionId + thirdPartyId during the first 30 min, everything is working as expected (we receive same experience). We know this is the recommended way(best practice) to go. However, doing some tests we found (hack/bug/corner_case) that if we just use the same value for ...

Hi everyone, We are using the Adobe Target server-side SDK to fetch experiences and we want to deliver a consistent experience across all devices/platforms for each client using thirdPartyId (if experience A was delivered, the next time it should deliver experience A) The delivery api [https://devel...