@HardikJa4  , Try the below format {"requestId":"3126743632163793","campaignId":"10e2583b-4d1d-4b57-bd6e-fdc79405d67d","recipients":[{"type":"aep","namespace":"email","userId":"test@gmail.com","channelData":{"emailAddress":"test123@gmail.com"},"context":{"personal":{"name":"XYZ","town":"Paris","coun...

@RakeshK1  Select (Ctrl+A) and copy(Ctrl+C)  all the nodes in the journey and paste(Ctrl+V)  them into a Notepad file. This will provide the complete journey in JSON format. Update the required information directly in the JSON. Then, copy and paste the modified JSON into a new journey. This will aut...

@Pradeep-Jaiswal If the requirement is to insert new event records  instead of updating existing ones, in order to maintain immutability, the XDM ExperienceEvent standard schema should be used. A time series based relational dataset is mutable. In general, relational datasets allow updates and delet...

1) Reporting (CJA) Orchestrated campaigns write message feedback, tracking, and journey-step events as XDM Experience Event datasets into AEP. CJA can create connections on top of these AJO datasets and expose them via a data view for reporting. However, datasets created using relational schema type...

@trojanHorse12  The user enters a lower-priority journey, but suppressed and will not receive email communication from lower-priority journey. Can verify this under reports -> journey exclusions section of a lower-priority journey. Check out  https://experienceleague.adobe.com/en/docs/journey-optimi...

@DN1191  I suspect that the incoming incremental data is not landing as a streaming ingestion type. This can be cross-verified by checking the audience evaluation latency for the incremental records/profiles. If you believe the above points are working as expected, then please follow up with Adobe S...

How quickly are these new records getting evaluated for the streaming audience? If the records are flowing via streaming ingestion, these profiles will get evaluated for the audience within 60 sec.

@DN1191  Yes, only incremental records are ingested through streaming using the Marketo source connection.Are the incoming events incremental that you are validating against the Unitary Event journey?

@DN1191 Unitary journeys listen for streaming events into AEP, batch data ingested from Marketo will not trigger a unitary event journey by default.   https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configure-journeys/events-journeys/about-events   

@AlbertoGa8  check the API details to create tag https://experienceleague.adobe.com/en/docs/experience-platform/administrative-tags/api/tags#create-tag