Hi we designed a journey trigger based and the same version but segment based.
We noticed the following issues that need a full rethink from your product team:
Overall the journey / segment/ trigger behave as expected BUT
our current data is built as such as that a contact can be associated or shared across multiple accounts.
Our journeys are emailing these contacts about compliance things they need to do for each business/ account they own.
As such if a contact is shared across 3 accounts we would like this contact to receive 3 emails (1 for each account).
In the case of a shared contact between an account 1 that should enter the journey and one (account 2) that shouldn't, the system bugs completely.
As part of our unfortunate testing:
- A shared contact can only enter once a segment based journey. A duplicate contact - same. Email hard bounces.
- In the triggered journey, the contact enters but the first email of the journey has dynamic data mapped to Account 1 and then in the same journey email 2 dynamic data is mapped randomly to account 2.
This is the worst customer experience ever where our customers receive incorrect information and that could have legal repercussions.
If you have another way to suggest on how to build these journeys please let me know but to date I have not found any solution.