We are having hard time figuring out to solve this issue regarding journey builder and using wait by attribute with multiple primary keys. What we would like to achieve:

  1. A sendble DE has 2 primary keys.
  2. This DE also has a Date field which is null when a contact enters the journey.
  3. This fields populates in the middle of the journey just before contact reaches wait by attribute activity which is based on the value of this field.
  4. We try to use contact data for setting up the wait by attribute activity but this seems to retrieve the date value only based on the one of the primary keys in the DE and ignoring the other one completely (thus random values are retrieved each time that correspond only to the one of the primary key).

Do you have any suggestions how to achieve the above?



You must log in to answer this question.

Browse other questions tagged .