4

What i am trying to achieve is an unsubscribe decision split that checks if a customer is unsubscribed directly against the global subscriber status.

Since i only can link dataextensions to the data designer, i feel kind of limited to get the "subscriber status" from the global subscriber status. For example the status of _Subscribers Dataview.

What i do not want is: Creating SQL queries and dataextensions of system data views which i periodically update.

Is there any out of the box implementation for unsubscribe decision splits?

Improve this question

1 Answer 1

Reset to default
5

You really need SQL Queries to get the data from the _subscribers Data View and link it to the entry Data Extension of the journey so you can check who of them unsubscribed or not.

Depending on the aim of the journey, you can also use measures to filter by unsubscribes from the main entry audience (no journey needed in this case).

Improve this answer
8
  • Thanks for the advice but to be honest this does not solve it. As per definition of the question i do not want to have SQL automations running to achieve this. That's why i am not going to accept the answer. The main reason behind is that this question still stays unanswered because it is not answered.
    – Johannes Schapdick
    Feb 12, 2020 at 11:21
  • I get your point but based on my reply, I just want to confirm that it is not possible to achieve that without using SQL queries or maybe via API
    – fromero
    Feb 12, 2020 at 11:24
  • You are talking about filters, these filters only apply while injecting contacts into a journey. I talk about decision splits that have to happen on a particular time. I do have to set these prior to sending emails to achieve follow up update-contact activities to inform other departments. These departments would then know which information a customer has gotten and which not. The longer the journey is the worse is the filter at the beginning and not inside activities inside the journey.
    – Johannes Schapdick
    Feb 12, 2020 at 12:08
  • I totally got your point at the beginning. I proposed the filter option as you didn't detail the aim of the journey and why you needed it. Now it is clear. Unfortunately, my suggestion is the same. I don't see any other approach rather than using SQL Queries. I hope someone from the community could suggest another approach.
    – fromero
    Feb 12, 2020 at 14:49
  • 4
    @JohannesSchapdick one thing I can think of is a custom activity as decision split. This would be able to perform an api call against the subscriber status and route contacts accordingly. This is obviously development intensive and might need an external service to host the custom split activity.
    – Stephan de Paly
    Feb 12, 2020 at 18:01

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.