Background
The winter 24 release notes mentioned a new feature that allows triggering real-time journey entry at scale by entering up to 100 contacts per API request, rather than making individual API requests for each contact.
This feature is useful for using commercial and transactional emails in the same journey, and can help reduce the number of API requests needed to enter multiple contacts into a journey.
Technical Details
The API endpoint for entering contacts into a journey in batches is documented at https://developer.salesforce.com/docs/marketing/marketing-cloud/references/mc_rest_interaction/enterContactsIntoJourneyInBatches.html.
This endpoint allows you to pass an array of up to 100 contact IDs and enter them into a journey in a single API request.
Implementation
To use this feature, you will need to make a POST request to the API endpoint, passing in the journey ID, contact IDs, and any other required parameters.
example.json
{
"journeyId": "YOUR_JOURNEY_ID",
"contactIds": ["CONTACT_ID_1", "CONTACT_ID_2", ...]
}
The root cause of the confusion was the lack of clear documentation and the fact that the feature was not properly announced.
Best Practices
Checklist for Entering Contacts into a Journey in Batches
- Make sure to pass an array of up to 100 contact IDs in the API request
- Use the correct API endpoint and parameters
- Test the API request to ensure it is working correctly
- Use error handling to catch any errors that may occur
- Monitor the API request to ensure it is completing successfully
What is the maximum number of contact IDs that can be passed in a single API request?
The maximum number of contact IDs that can be passed in a single API request is 100.
What is the API endpoint for entering contacts into a journey in batches?
The API endpoint for entering contacts into a journey in batches is https://developer.salesforce.com/docs/marketing/marketing-cloud/references/mc_rest_interaction/enterContactsIntoJourneyInBatches.html.
How do I handle errors that occur when entering contacts into a journey in batches?
You can handle errors by using error handling mechanisms such as try-catch blocks and logging errors.
Can I use this feature to enter contacts into a journey that has already started?
Yes, you can use this feature to enter contacts into a journey that has already started, as long as the journey is still active.
Need help shipping this in production?
Genetrix builds and untangles Salesforce Marketing Cloud and Agentforce setups for teams that want it done right the first time. If anything in this post sounds familiar, talk to us before it ships.