Hi @gautham_madala , Using 1 sandbox is easier because you set up schema/dataset once and don’t have to change IDs when publishing.But the downside is test data can mix with prod and access control is harder.Using 2 sandboxes is safer and makes access management easier, but you have to maintain both...

Hi @KumarRishii @Vinay_Chauhan What is drawback of this approach. As far i know below are some1. No Audience Activation for anonymous users.2. Delayed Personalization for AJO Journey anonymous web activity cannot trigger real time journeys untill the user become unknown.3. Delayed identity resolutio...

We are currently migrating from Adobe Analytics to Customer Journey Analytics (CJA) and would like to request support in enabling identity stitching for our setup. Our Setup: We operate a B2B lead-generation website. AEP Web SDK is implemented, and ECID is generated for all page views. Email is capt...

In Adobe Journey Optimizer (AJO), a "timeout" in the context of email channel actions usually refers to a situation where the user neither opened nor interacted with the email within a given time window, not just "did not open".

Hi @saikumar3Here are some actual options you can explore: 1. Adobe Solution Partner Program (SPP) - if your organization is an Adobe partner, you may get access to partner sandboxes via SPP. Link: https://solutionpartners.adobe.com/2. Customer Account Access via Employer - If your current employer ...

Yes you can use that one as well. Also find the below documents for the sandbox licence and setup. https://experienceleague.adobe.com/en/docs/experience-platform/sandbox/home

Hi @Michael_Soprano Development sandboxes are basically "safe playgrounds" where you can:Test stuff without breaking anything importantLearn AEP features without worrying about mistakesTry different approaches before committing to productionLet multiple people experiment simultaneouslyValidate integ...

Hi @Saiteja_1225 Can you please add more details to your question. Although whether or not nested fields in a schema should be mandatory depends on the specific requirements of your data model and how you intend to use the schema. While nested fields can be made required, it's not always necessary, ...

Addition to this you can also look into below options:- 1. Verify the Schema Primary Identity: Confirm that the schema you are using for streaming ingestion has the correct field designated as the primary identity (e.g., ECID field).Identity Map: Ensure that the identityMap is correctly configured a...

Hi @Joseph_Making I think either you can go with the above solution using the visit number as segment or use this 2nd option directly you can use this option which need to be implemented using adobe launch.Option 2: Visit Duration TrackingUse the getVisitDuration data element to track engagement pat...