This is more of a methodology or best-practice question.

What I have:
Users data extension
Online stores data extension
They are connected by the Subscriber_Key

A [User] can have multiple instances of an [Online Store]. The [Online Store] changes status based on whether it is open

I want to enter a user into a journey and have all the Online Stores associated with a user on a list in each email. When a store's status changes they would go into a different portion of the journey.

The questions I have are:
1) would an SQL query allow for a one-to-many relationship that updates the DE on a nightly basis?
2) would using ampscript and filters be a better option than a query

  • Have you tried using decision splits during your journeys? – Samuel Dare Oct 3 '17 at 17:23
  • Yes - that's what I would prefer to do, the question is: can I have a queried data extension that can do an UPDATE when there's a one-to-many relationship between Stores and Users – Tom Callahan Oct 3 '17 at 17:30
  • How many records are we talking about in the Users and Online_Stores data extensions? – Jackson Chen Apr 3 '19 at 23:43
  • I don’t even remember. This is from 18 months ago. – Tom Callahan Apr 4 '19 at 14:14

Your Answer

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

Browse other questions tagged or ask your own question.