0

I have 2 journeys. One is the welcome journey, and one is the post-purchase journey. We automatically opt-in all users who checkout. Unfortunately right now new all users who checkout with us are getting BOTH the welcome and post-purchase journeys. both journeys have different data extensions. We would like to have it so that if a user is a new user, they ONLY get the Welcome Journey and do not get the Post Purchase Journey.

6
  • What are the entry sources for these two journeys? May 19 at 15:29
  • How do you feed data to the data extensions?
    – zuzannamj
    May 19 at 17:33
  • Data come through the server to the server API call May 19 at 18:59
  • What type of entry source are you using for the two Journeys? Data Extension or API Event?
    – Macca
    May 19 at 23:03
  • You're most likely using the same entry source for two different journeys and that might be the problem May 19 at 23:57
0

As it has been considered already in the comments, you are probably using the same Entry Source for both Journeys and/or do not have any entering rules for the Journeys.

To start segmenting people when they enter, you can create an additional field in the Entry Source Data Extension, which would symbolise whether a contact is a new user, e.g. Field NewUser = "True" and then add a filter for the Entry Source for one of the two Journeys, which would filter out people who (do not) have Field NewUser = "True".

0

I suggest you use a single journey with a Decision split to handle the first-timers and the returning customers separately, how about?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.