Hi  In Adobe Journey Optimizer, an event journey requires a consistent namespace for all events, it's needed to ensure correct profile identification and flow throughout the journey life cycle. There is a feature of supplemental identifier which can also help and worth checking.

Hi @Sukrity_Wadhwa ,- For Authoring API Triggered Campaigns : we need campaign manage permissions .- To execute the API triggered Campaign : we need to have a developer permissions and should have developer project on Adobe IO console : https://developer.adobe.com/journey-optimizer-apis/references/m...

On Best practices : - Contextual Support : The contextual attributes passed into the request cannot exceed 50kb and are always consider of type string.- The context.system syntax is restricted to Adobe internal usage only, and should not be used to pass contextual attributes.some are mentioned here ...

Yes we do support Experimentation in API Triggered Campaigns.so one can create an experiment in the Campaign Authoring and the same will be honored from API .We don't support any experimentation options ( treatments ) from the API Payload.https://experienceleague.adobe.com/docs/journey-optimizer/usi...

Hi @Anuhya-Y ,Guardrails for throughput in API triggered campaigns are captured at : https://helpx.adobe.com/legal/product-descriptions/adobe-journey-optimizer.html today we support 500 requests per second for all outbound channels (email , push and sms ) 

Hu @Sukrity_Wadhwa Yes, This document has good API Triggered Samples for different channels (email , push and SMS) and for different scenarios : https://developer.adobe.com/journey-optimizer-apis/references/messaging-samples/