I am trying to inject contacts via journey rest api from cloud page.
It seems to work fine if it is unique record, but if the contact already exists in a journey, the cloud page does not throw an error but no record is added to the DE and subsequently, no entry in the journey.
I've tried 2 different scenarios:
- Subkey and Date : composite keys
- No primary key (Subkey and email address is not nullable)
Journey setting is to allow re-entry anytime.
Is rest api journey entry admitting only one unique entry (per subscriber) expected behavior?
If so, is there a workaround to allow multiple entries per subscriber?
Thanks in advance 🙂
Best Answer
Perhaps you could try to add some more logic to your code, in which you first get a contact's exit status from a journey, if needed remove a contact from a journey, and then try to add him once again..
I wrote a quick sample:
Please be aware that I haven't included in the logic of how to obtain access token. But since you already were able to fire the journey builder API from a cloud page, I assume that you already managed to deal with this.
I haven't tested this code, but it should give you a direction to look for.