API Event Entry Source Use Case

A marketer at Northern Trails Outfitters (NTO) works with a developer to set up an API that admits customers into a Marketing Cloud Engagement journey every day. In this example, the marketer and developer work to set up the API Event and API request, and then test sending a single contact into a journey. The API is intended to send a single contact at a time. It admits contacts when they’re ready to enter the journey rather than queuing or batching them.

1. Create a journey from scratch.
2. Add the API Event onto the journey canvas as the journey's entry source.
3. Click to open the entry source.
4. Copy the Event Definition Key and provide it to the developer.
5. Configure the journey activities. Then save and activate the journey.
6. With the Event Definition Key in hand, the developer uses the instructions here to create the API request to fire the entry event.
7. The developer gets a sample ContactKey that is linked to All Contacts in Contact Builder to put into the API request. This key corresponds to the contact that enters the journey when the request is fired. The developer then uses an API client to send the test request.